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
Related
What I want to do is install a stock non rooted rom, kernel, and recovery. I am not sure how to change recovery to stock either is it like flashing a rom? Please give me some links for these I can't seem to find them, besides the stock kernel I found that.
----------------------------------------------------------------------------------The reason I want the above is bellow, if it matters.-----------------------------------------------------
My phone is about 95% broken.
Before, every rom/kernel combination would randomly restart, it was my phone it self I believe.
I went to a stock rooted rom, but then it restarted, and my lock screen worked, yet my home screen was black all i could do was slide my status bar down.
After that i restarted my self and then it got stock forever on the screen where it says Samsung galaxy s4.
The 5% working part is my recovery, for the most part.
I keep having to do a full wipe, not just system wipe otherwise it says error unable to mount preload or i/o or a few other things, I have to system wipe before every rom attempt.
I tried several popular roms such as sacs and triforce and a few other roms and all the kernels also.
The phone will turn on, work for a little normally, then crash again and go into the infinite loading screen where is simply says galaxy s4.
This phone is only 3 months old, so I want to take it back to sprint being completely stock so they give me a new phone.
I need links to files I need, and if i am forgetting to change anything back to stock please let me know. Thank you.
I replied to you in the newbie thread, but to return to complete stock download the latest firmware from here: http://www.sammobile.com/firmwares/ and install it with odin. Do a factory reset before and after install to make sure you have cleared out what ever is causing your problems. After this process you will be completely stock and unrooted. If you are still having problems after this it is probably hardware related.
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.
try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version
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!
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
FlinderMouse said:
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
Click to expand...
Click to collapse
Try a factory reset and then install stock ROM
i7vSa7vi7y said:
Try a factory reset and then install stock ROM
Click to expand...
Click to collapse
Could you point me in the right direction for that? Everything I have tried so far seems to fail...
Edit: I got back to the NAE stock rom, but I can't downgrade the modem from NG2 back to NAE...
Edit2: I didn't need the correct modem to activate, I guess. Flashing back to GPE, will update this again.
Final Edit: Once I activated on the stock ROM, everything seems to work perfectly on the GPE. Thanks for the suggestion, i7vSa7vi7y!
Hi there
I have recently picked up my old S4 since my OPO screen broke. I was annoyed with the buggy CM 12 nightly it was running and tried installing the newest CM 13 nightly. It gave me no signal and I decided to try to revert to stock, following the guide Unroot/Unbrick, Flash official stock firmware on S4. Applying the I9505XXUAMDE_I9505OXXAMD8_NEE 4.2.2 stock rom through ODIN was a breeze but after booting i realized it had no sound.
Also placing or receiving calls makes the phone hang, even occasionally reboot, and sometimes a window with "android.phone.. app" or "process system is not answering" appears. For example also not possible to record video.
I did both factory reset and wipe cache in bootloader, but when wiping cache I get the lying down android with red exclamation mark for a few seconds then reboot.
I then tried to reflash above stock rom with repartition (pit file) and the problem remains.
I dont suppose it is a hardware problem since it started after I flashed new rom. It seems like some audio related software issue that I cant seem to get rid of - can anyone help or should I just give up and get another phone?
Thanks in advance, sorry for the long post
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Pwnycorn said:
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Click to expand...
Click to collapse
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
fiedes said:
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
Click to expand...
Click to collapse
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Pwnycorn said:
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Click to expand...
Click to collapse
I will try to install TWRP and the newest stock firmware and see what happens. Thanks
Ok, upgraded to latest stock rom and everything works!
No idea what was wrong specifically though.. Thanks for the help!