Database Users

[Q] Is it possible to go 100% stock with update

Here is my problem. I would like 100% stock with update.When I first got the phone I rooted with motochopper and installed SPH-L720 OUDHS Recovery. I tried ForceRom 1.0, but went back to my original Nand. Everything worked fine. I used odin to go stock and factory reset data and cache, im good to this point. When I install the sprint update I get the error "Prevention information: This device has detected an application attemping" blah blah blah. Also when i try turning on WiFi the error message pops back up. I checked and the phone is not rooted. I have tried every back to stock thread in these forums. One thing I found in settings: about phone: Status: device status: This still say's custom, even after all the attempts to go stock. Thanks for you help in advance.

How to unroot Galaxy S4, restore to stock and reset the flash counter
Or you can go to the Developer's section and find some threads about restoring. The security thing sounds like you still have Shabby's custom kernel installed. (I could be wrong.)
But the official stock MDC rom from Samsung includes the official kernel. I've restored a couple of times with the official ROM, and I was always back to the original stuff, including kernel. To completely restore, you can always also do a factory reset from the stock recovery (after you flash back the original rom). It will wipe all your data and settings, of course, so be warned.
Edit: A Local Thread: http://forum.xda-developers.com/showpost.php?p=40947712&postcount=6
Also, I forgot to mention, but after this, you'll either just have to wait for Sprint to push the MDL update to you (since you say you want to be updated), or go find the thread (in dev section) from crawrj (I think him) about how to install it manually; but I think that will require a custom recovery, and you are trying to avoid customizations, so...

I have done exactly what the video posted said, even wiped data factory reset. The problem is after i install the OTA update I get the error message and my WiFi does not work. When I try and turn on WiFi it keeps popping up the error. Unrooted I should not get the error and WiFi should definitely work either way.

(At this point, then, this is somewhat like the blind leading the blind, so hopefully a more seasoned ROM manipulator will respond soon to help fix ya up, but until then...)
Maybe you can try crawrj's "Wipe All" script first before flashing the stock ROM? *shrug* (Link: [SCRIPT]Wipe All Zip)
I mean, if you wipe everything and then flash the stock ROM, I would be puzzled as to why something you installed before the wipe would still be lingering around to mess up your system. Again, though, I make no claims this will fix you up--it probably won't. Just throwing out ideas until someone more knowledgeable comes along to help you.

vertualrod said:
I have done exactly what the video posted said, even wiped data factory reset. The problem is after i install the OTA update I get the error message and my WiFi does not work. When I try and turn on WiFi it keeps popping up the error. Unrooted I should not get the error and WiFi should definitely work either way.
Click to expand...
Click to collapse
I had same problem when following the steps to return to stock after flashing custom kernel, Wifi wasn't working and was getting nagging Update and Information notifications. However I did notice after flashing Stock rom via Odin when checking 'about phone' that the Broadband Version was still MDL while Software Version did revert back to MDC. I was also under the impression that flashing the stock rom would restore stock everything, including Broadband Version back to MDC. However wasn't a big deal, I went ahead accepted the OTA update, which downloaded and went through the install process. Afterwards I went ahead and flashed ForceRom 1.0 and the 1.1 update, followed by flashing shabby's custom kernel to get Wifi working. I'm now completely happy with my setup, no nagging notifications and showing Software and Broadband Versions running MDL with shabby's custom kernel. Been running smooth for a couple of days now without any issues..

Figured it out! Had to reset the Flash counter with triangle away in order for the Device status to become official. Then i did data factory reset then flashed the stock .tar with odin. I installed the update on the phone and Viola! device official and everything is stock and working. Thanks for the help.

Good info, there, about Triangle Away. Glad you sorted it out!

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Slimbean 4.2.2 Build - media issues

Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance

Update: Any ROM I install... Phone and sounds do not work.

Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.

jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.

Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP

[Q] Can't wipe or factory reset encrypted phone

I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.

not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.

Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!

Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!

not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!

Soft brick - Need some guidance

It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.

You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app

Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!

Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?

kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app

Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!

[Q] hyperdrive ROM and a near disaster

I have now tried to install Hyperdrive ROM three times. The first time I had found an old thread written well before much of the S4 debauchery got as thick as it is now and it was definitely the wrong version. I`m on NI1 4.4.2 and downloaded the latest HD rom file (21?) as well as the UI. Followed the instructions to a T and wound up with it stuck on the orange HD/Kit Kat animation for eleven minutes. Finally got it to shut off, wouldn`t reboot. Tried a few times hoping to get it to at least get me in a position to restore a backup. Nope. It would get to the setup procedure but every action on the screen resulted in a "Samsung key lock has stopped working" message. Ended up just installing an older Odin stock rom (4.3), rooting and reinstalling Safestrap and finally getting to load my backup. I~m really interested in the HD rom, so can I ask for (a) what I might be doing wrong and (b) how do I do it correctly? I`m on NI1 again, rooted, using safestrap.