Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
thunderstorm116 said:
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
lordcheeto03 said:
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
Click to expand...
Click to collapse
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
thunderstorm116 said:
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
Click to expand...
Click to collapse
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
lordcheeto03 said:
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
Click to expand...
Click to collapse
Ah, okay. I think I understand that, I'll give that a try. Thanks for all your help.
Okay, so I tried doing everything you told me to do and got some weird results and thought I'd post them for anyone else that may run into this problem.
I flashed a custom recovery through Odin, then flashed the AOSP Liquid Rom like you said. I then flashe the stock MD5 file through Odin and let it do its thing. Once it was done, that's where the weird stuff started. The phone rebooted as it should, but then it got hung on the white T-mobile screen. It just sat there for a very long time. Now I've done this enough times to know when its taking too long and there's a problem.
So I did something that I know probably shouldn't have done and I held down the power button until it turned off. I then tried to boot it again to no avail, same thing.
After this I booted into the stock recovery and decided to do a factory data reset from there. (I was pretty sure there was nothing wrong with the stock Rom as I've used it before; there must have been something still there from the Liquid Rom causing problems.) When I rebooted from the recovery this way, it finally booted right up.
I now thought that I needed to flash CF-AutoRoot and then triangle away, but no, for some strange reason my device status now reads OFFICIAL!
I searched for the update and it is now in the process of downloading.
(Strangely enough though, the lock sound from wicked V8, is STILL there. I don't get it and I don't even want to know anymore.)
Sorry for the super long post, but I thought that if anyone else was having my same problem they should see this.
Thanks again for all your help and I hope you'e having a great Thanksgiving.
I've been trying, without an ounce of luck, to flash a custom rom. I'd love to update to Kitkat, and I'm currently running a rooted stock ICS. Almost every ROM that I've looked into says to flash with CWM, but I can't seem to find a version that will properly flash onto my phone. Am I doing something wrong here?
In the process of flashing the stock JB for Virgin Mobile. Hopefully once that's complete, I'll be able to get the next step going.
I have been reading through many threads last night and today trying to figure out the best way to get rooted stock back on my AT&T S3 i747. I had hoped to figure it out myself, but have come to the realization that I need a little guidance.
In light of that, I'll try to give concise information. First of all, I am simply looking to end up with stock.
Series of events:
*Have had stock since given this phone in August; it was kept up to date with OTA and it was current (4.4.2) as of yesterday morning when att pushed the newest update to the phone.
*I rooted the phone in September using CF root and Supersu to both root and block Knox and it had been working very well until the attempted update yesterday.
*I no longer have a custom recovery backup
*yesterday my phone went through the update (download and install), but when it rebooted, it only made it through the Samsung splash screen and then went black.
*I am able to boot up both stock recovery and into download mode
*Using the stock recovery to reset the phone has not fixed the problem
Having never used Odin or installed a custom ROM, I am hesitant to flash anything to the phone until I verify that the new bootloader (that is now possibly there due to the OTA update) and anything I try to install won't conflict and make my problem worse.
It seems to me that I should use Odin to load a custom recovery, make a backup, and then flash a ROM. If that is correct, would the recovery ROM found in this thread be the correct one: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
If it is not the correct ROM, what would be the correct one?
Thank you,
M
For a custom recovery, flash the most recent tar.md5 file from here using Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Boot into recovery, create a backup, and flash a custom ROM. I recommend the most recent CM10.2 so you can determine the bootloader currently installed on your phone. Once you determine the bootloader, you can decide how you want to proceed.
Thank you so much for your response.
I did as you suggested and I do indeed have the UCUFNJ1 bootloader. That does help me determine which direction I can take. Although, now having tried out a non-Samsung ROM, I may have changed my mind about keeping stock on the phone. If I decide to go back to stock, I'll just keep my eyes open for a stock ROM that states it requires that bootloader, correct?
Again, thank you so much for your help!
I was on CM 12.1 and I want to go back to completely stock Note 4, as if I purchased my device from the Sprint Store!
I went to download Odin and the stock firmware of Android 5.0.1 for my device, I followed instructions online, and when I press start in Odin, after about 3 seconds it Fails.
Can I not go back to stock Touchwiz 5.0.1 firmware after being on CM 12.1? I do not have a nandroid backup, and even when I try and access Recovery, it is no longer custom recovery, it is a very simple looking recovery screen, with no option to restore a backup.
What can I do! ): I'm extremely stressed and worried I'm not quite sure what to do.
My phone does go into Download mode just fine and show up in Odin.
Also, my phone actually boots up fine, and works fine, but there is no custom recovery, and Odin is failing when trying to flash the stock firmwares
Down load the latest tar from samsung its in the dev section that will fix your phone with odin
pbedard said:
Down load the latest tar from samsung its in the dev section that will fix your phone with odin
Click to expand...
Click to collapse
Since you're familiar with CM and recent OE1 writes both on TW and CM, can you tell the OP if reactivation lock exists on CM, please? How to disable, if enabled?
He's trying to flash OF5 in Odin but it quickly fails or he's downloading the correct OF5 tar now. Add any suggestions you think he might need when coming from CM12 to stock tar these days.
I suspect the recovery is now stock due to partial flash (if possible), reactivation lock or attempt to root in Odin again.
Thanks in advance.
Sent from my SM-N910P using Tapatalk
Hello everyone,
I have a TMO Note 3 running Lollipop at this moment, the phone is rooted, but I tried flashing a new ROM and it soft bricked on me. ODIN stopped at the very beginning of flashing and just bricked the phone. Also TWRP was not working either and still not, but I was able to bring the phone back from the semi-dead state it was in. I want to flash it again but now I don't know if I did something wrong (most likely) and I just need some feedback on what to do. I wanna go to a stock rom so i can upgrade to the actual Lollipop Rom from T-mobile but I was also wondering if I can just flash a stock 5.0 rom that runs better than the one I have. Additionally, I just cant get TWRP to stick at all; every time I try to flash it and try to go into recovery, phone goes into boot loop. Here are some screenshots of the current "about phone" section. I am sorry if i am not asking the right questions but I gotta start somewhere. Thanks everyone in advanced!
https://imgur.com/a/dpn3Y
If you can get into download mode, flash the latest stock rom from Sammobile.com.
audit13 said:
If you can get into download mode, flash the latest stock rom from Sammobile.com.
Click to expand...
Click to collapse
look for the samfirm tool, its faster then going through sammobile:good::highfive: