Related
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.
Thanks I'll check there.
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium
New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...
bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2
matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.
Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.
Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2
[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.
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.
If you have 'Device Status: Modified' and don't know how to fix it, you may be interested in my story.
I bought GN2 in November. Rooted, flashed custom firmwares etc. Beyond being just great phone it seemed to have one big problem: it did lock up cold every once in a while regardless of firmware.
I created some other thread on that and based on responses and some of my own research I started getting to conclusion that my device has a hardware problem.
So I figured that I need to do warranty exchange. So I unrooted, triangle away and flashed completely fresh original tar.md5 package via odin with all blows and whistles. Did factory reset, of course.
I still see 'Device Status: Modified' after some time. Usually after reboot. Bummer!
So I did some research and someone here on xda mentions that using jig from old days helped with it. I had a jig, so I tried it. Rest assured - device status became 'Normal'. Awesome! I am happy and I didn't have to wipe data.
Some time passes. The darn thing is 'Modified' again!. I use jig again - story repeats. So I figured that I use jig to reset status right before I go to AT&T. So I did.
I came to AT&T center and they say 'Hmm - it must be software locking up your device. Lets just flash and clean it all'. Fine - lets do it. So I walk out of the store with wiped clean device having UCALK7 version of firmware.
Obviously, it didn't solve the problem. Device still locking up and it's still modified'.
Now we get to the interesting part.
I use 64Gb Sandisk microsd card. It has may be 40Gb of music and other stuff. I always had .nomedia file in a music folder so album art would not appear in gallery.
I decided to remove .nomedia for some other reasons and so I did.
The phone didn't find my music for couple of days but eventually music did get scanned. And at this point (I think at this point), my jig stopped working and device just remained in 'modified' status. That was bad - I needed to replace device.
So I did more research and some people mentioned some correlation between external sd card and 'modified' status. Something, in effect, that formatting external sd card fixed it for them. I simply took out sd card and rebooted. AND.... status become 'normal'.
Now we get to part III.
I am happy that my status is 'normal', I am not putting sd card back and I use it for a day and than go AT&T. Right before that, while watching YouTube during lunch, my device locks up. I am block away from AT&T center so I just walk to them and show locked up phone.
They say ok and give me a new phone. Awesome! I plugin my sd card and walk out.
I didn't even sign in to Google yet, just walking away from store and I look at my brand new phone and, guess what? 'Device Status: Modified'
So I took out sd card: 'Device Status: Normal'. Card in - modified.
Tonight I will explore my sd card on PC to see what possibly can be on it to cause it. And may be reformat it.
So the moral: external SD seems to cause somehow this device modified status.
And may be this story will help someone.
It definitely appears that Samsung is searching external sd card for artifacts related to rooting. Once I deleted all twrp an titanium backup as well as all flashable stuff like roms etc the status changed to normal. After a while it became modified again so I formatted card and copied back my media.
Now it stays.
So big brother is watching - you can't own any illegal artifacts...
Sent from my SAMSUNG-SGH-I317 using xda premium
Ok. I give up. After a day it became 'modified' again. New phone without any change + formatted sd card.
So just remove the darn card from the phone and reboot before taking it to AT&T or Samsung for warranty. That's provided that this 'modified' status even matters.
Maybe it's the size of the card? Isn't 32 gig the largest officially supported?
Just a thought...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Its not the size of the card...I had a 4gig in mine and had that modified status also...time will tell.
Sent from my SAMSUNG-SGH-I317 using xda premium
LOL
I am NEVER going to understand wtf posses people to play mcgeyver when doing warranty exchage.
:banghead:
First off NOTHING is easier than using sammys firmware tool and it garauntees
A complete stock phone.
If you can get into dl mode youre golden.
Its a one step process and fail/noob proof.
You will need kies, and the most recent usb drivers.
I cannot believe you jigged your n2
All that time wasted unrooting, fladhing "stock rom" checking md5 sum
Waste of time!!
Go to samsung.com and dl kies.
Flash em firmware recovery:done
Like new no modified flag.
I cant tell you how many times I have done this. Bootlooped, bricked, corrupted recovery... if you can get into dl mode and have 20 min to spare...shell be just like new. GL ! :thumbup:
freakboy13 said:
LOL
Go to samsung.com and dl kies.
Flash em firmware recovery:done
Like new no modified flag.
I cant tell you how many times I have done this. Bootlooped, bricked, corrupted recovery... if you can get into dl mode and have 20 min to spare...shell be just like new. GL ! :thumbup:
Click to expand...
Click to collapse
I kind of agree that the easiest is to just flash kies firmware. But the point of this thread is to highlight that SD card may cause it even to brand new unmodified phone.
The real question is...havebyou tried it yet?
I have had the same 32gb samsung sd card in my gs3 and just swaped right into
My n2. And according to your title the thread is about the "modified" flag on your phone.
The em firmware tool garauntees that not to be there. I wasnt trying to hijack your thread or anything. There are tons of fake sd cards that say samsung or kingston.
Do you have any tools to verify the sd cards integrity/ true storage?
Honestly give the em tool a try.
Then (this may be your prob)
Reformat your sd with your phone.
I know pia but it fixes a lot of probs.
When I first got my 32gb I was having issues. Missing/ corrupt files, etc.
Reformated the card with the phone...bingo! Never had an issue since.
Hope it works out for ya!
:beer:
freakboy13 said:
LOL
I am NEVER going to understand wtf posses people to play mcgeyver when doing warranty exchage.
:banghead:
First off NOTHING is easier than using sammys firmware tool and it garauntees
A complete stock phone.
If you can get into dl mode youre golden.
Its a one step process and fail/noob proof.
You will need kies, and the most recent usb drivers.
I cannot believe you jigged your n2
All that time wasted unrooting, fladhing "stock rom" checking md5 sum
Waste of time!!
Go to samsung.com and dl kies.
Flash em firmware recovery:done
Like new no modified flag.
I cant tell you how many times I have done this. Bootlooped, bricked, corrupted recovery... if you can get into dl mode and have 20 min to spare...shell be just like new. GL ! :thumbup:
Click to expand...
Click to collapse
I agree completely!!! Why go through all that when you're just trying to go back to stock for a repair? (plus it's a good "last ditch" troubleshooting tool when a ROM is just giving you too much trouble and re-flashing doesn't seem to help.
ReggieSmith said:
I agree completely!!! Why go through all that when you're just trying to go back to stock for a repair? (plus it's a good "last ditch" troubleshooting tool when a ROM is just giving you too much trouble and re-flashing doesn't seem to help.
Click to expand...
Click to collapse
I'm attempting to restore my phone to complete stock and am having issues getting by binary counter from 1 to 0. Status is Normal and firmware is official Samsung, but the counter remains at 1 after using triangle away. I have done a factory reset as well.
I didn't know you could use Keis to restore to stock and I've look around the software, but can't see how to do it. I see the Emergency Firmware Recovery, but it looks like you can only use that if your phone is in emergency mode.Any help?
---------- Post added at 08:54 PM ---------- Previous post was at 08:25 PM ----------
KinAndTonic said:
I'm attempting to restore my phone to complete stock and am having issues getting by binary counter from 1 to 0. Status is Normal and firmware is official Samsung, but the counter remains at 1 after using triangle away. I have done a factory reset as well.
I didn't know you could use Keis to restore to stock and I've look around the software, but can't see how to do it. I see the Emergency Firmware Recovery, but it looks like you can only use that if your phone is in emergency mode.Any help?
Click to expand...
Click to collapse
Nevermind, I figured it out using Firmware Upgrade and Initialize. Although, it didn't clear the Binary Count. Still shows "yes (1 counts)" when I enter download mode. ugh
---------- Post added at 09:43 PM ---------- Previous post was at 08:54 PM ----------
I did it! lol
Used this (http://rootgalaxys3iii.com/how-to-reset-rooted-galaxy-note-2-flash-counter/) to finally get Triangle Away to work on my phone and then did factory reset. Completely stock now.
Hey grats on that. Judt an fyi you can use the EM tool anytime...doesnt have to be an emergency.
Hmmm im gonna have to try the em tool again and check my count.
It set back to 0 eveytime on my gs3.
Glad it worked out for ya.
:thumbup:
How do you use the EM Recovery via Kies? I click on it and all get is no phone listed in the Emergency Phone section and ask for recovery Code from the other PC or something..Not sure..