Related
I am not sure what is going on here. If anyone could help out, it would be much appreciated.
I am on stock AT&T Touchwiz. I was running the stock kernel and ktoonsez's 5/27 TW kernel with no problem. When I flashed ktoonsez's 5/30 TW kernel, I lost the ability to connect to wifi (when I try to turn the wifi slider to "on," it switches right back off). I cannot for the life of me get it to turn on.
I tried flashing back to the 5/27 kernel and I still can't get wifi to turn on. I also tried odin-ing back to stock, which has the same problem.
The odd thing is that I can still use wifi tethering, so I know the wifi can work. I just can't get the wifi settings to enable wifi anymore.
Just for fun, I flashed the AOKP rom and ktoonsez's 5/30 AOKP kernel, and wifi will work in that rom. I just can't get it to work in Touchwiz.
Any thoughts?
Make sure your baseband and build are the same, ex. baseband MDL, Build MDL.
If these 2 are different wifi will not enable.
C13v3r0n3 said:
Make sure your baseband and build are the same, ex. baseband MDL, Build MDL.
If these 2 are different wifi will not enable.
Click to expand...
Click to collapse
Baseband and build are both the same: 1337UCUAMDL.
before you flash do a system wipe so you have a clean slate, then flash rom and kernel and see if that helps, also you may try resetting to default settings from within the os.
C13v3r0n3 said:
before you flash do a system wipe so you have a clean slate, then flash rom and kernel and see if that helps, also you may try resetting to default settings from within the os.
Click to expand...
Click to collapse
I wiped system and then odin-ed to stock and it still didn't work. I am not sure how much "cleaner" I could get it.
Hmm well, it seems like you did everything right, thats really strange.
C13v3r0n3 said:
Hmm well, it seems like you did everything right, thats really strange.
Click to expand...
Click to collapse
Yeah. I would understand that wifi was totally dead if if didn't work in the AOKP rom, but it does, so I'm stumped. I may just go over to the AOKP rom since I don't really need the Touchwiz features anyway.
after you odin back to stock did you do a factory reset from within the OS?
1. Open Settings.
2. Select Accounts.
3. Select Back up and reset.
4. Tap Factory data reset.
C13v3r0n3 said:
after you odin back to stock did you do a factory reset from within the OS?
1. Open Settings.
2. Select Accounts.
3. Select Back up and reset.
4. Tap Factory data reset.
Click to expand...
Click to collapse
I did not do that, but I will try it later. Thanks for the help!
C13v3r0n3 said:
Make sure your baseband and build are the same, ex. baseband MDL, Build MDL.
If these 2 are different wifi will not enable.
Click to expand...
Click to collapse
Odd... My baseband is MDB and build is MDL. I thought baseband had nothing to do with kernels..
Sent from my I337~SGS 4 using Xparent Skyblue Tapatalk 2
It doesnt, i was telling him to look at those because i experienced something similar.
I flashed back to stock and my baseband and build were different, baseband was mdl and build was mdb and i couldnt turn on my wifi at all.
C13v3r0n3 said:
It doesnt, i was telling him to look at those because i experienced something similar.
I flashed back to stock and my baseband and build were different, baseband was mdl and build was mdb and i couldnt turn on my wifi at all.
Click to expand...
Click to collapse
Oh ok... Maybe it was rom related and you probably needed a kernel to fix it (as it did for me).
Sent from my I337~SGS 4 using Xparent Skyblue Tapatalk 2
I started having similar issues today with my WiFi.
Back story: I was playing around in ES Explorer trying to get WatchOn app to show in my app drawer and changed something that apparently shouldn't have and ended up sending my phone into boot loop. It also wouldn't recognize my SD card. After several faiked attempts due to my computer not recognizing my phone I was finally able to Odin to stock, re-root and restore from my Nandroid backup.
Which leads me to my problem. When I try to enable WiFi it just shuts back off and I get a security pop up saying, "Prevention Information - The device has detected an application attempting unpermitted actions and has stopped working. It is recommended that you reboot your device." And gives me an option to rabbit now or later.
After reading this thread I noticed that my baseband and build number were different and I will try doing a complete wipe and Odin to stock. Any other input would be greatly appreciated.
Thanks!
Sent from my Galaxy S4 via Tapatalk
C13v3r0n3 said:
before you flash do a system wipe so you have a clean slate, then flash rom and kernel and see if that helps, also you may try resetting to default settings from within the os.
Click to expand...
Click to collapse
nope he is right..there is a problem with the new ver KT...lost xposed mod completely on mine.
wyazell said:
I started having similar issues today with my WiFi.
Back story: I was playing around in ES Explorer trying to get WatchOn app to show in my app drawer and changed something that apparently shouldn't have and ended up sending my phone into boot loop. It also wouldn't recognize my SD card. After several faiked attempts due to my computer not recognizing my phone I was finally able to Odin to stock, re-root and restore from my Nandroid backup.
Which leads me to my problem. When I try to enable WiFi it just shuts back off and I get a security pop up saying, "Prevention Information - The device has detected an application attempting unpermitted actions and has stopped working. It is recommended that you reboot your device." And gives me an option to rabbit now or later.
After reading this thread I noticed that my baseband and build number were different and I will try doing a complete wipe and Odin to stock. Any other input would be greatly appreciated.
Thanks!
Sent from my Galaxy S4 via Tapatalk
Click to expand...
Click to collapse
Maybe there is something wrong with the Kernel you are using. I don't know because I am on stock. However, the security message you are getting might be remedied by freezing "knox" and "SeAndoid". It probably wouldn't hurt for you to try it.
scott14719 said:
Maybe there is something wrong with the Kernel you are using. I don't know because I am on stock. However, the security message you are getting might be remedied by freezing "knox" and "SeAndoid". It probably wouldn't hurt for you to try it.
Click to expand...
Click to collapse
I'll try that first.
I should also note that I'm on stock room with clockwork recovery installed.
Sent from my Galaxy S4 via Tapatalk
Just to update, I did a factory reset in CWM, reset davlik cache, factory reset from within setting and odin back to stock and wi-fi is working.
I'm about to re-root and not install the Nandroid backup and see if it's still working after that.
Final update.
I was able to get WiFi working again. Im not sure if doing this would help anyone else but this is what worked for me.
I did a wipe in CWM, cleared the cache and Odin back to stock. I then updated the software through the phone's setting menu. I tested WiFi before and after the update and it was working just fine.
Went ahead and rooted my phone again and WiFi was still working. Installed CWM again and tried the restore from my nan droid backup again and all is functioning normally.
On a side note, my 64GB SD card is working again also.
Sent from my Galaxy S4 via Tapatalk
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
JJ2013 said:
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
Click to expand...
Click to collapse
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Further details of whats been tried
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Yes, I neglected to include that I tried wiping cache first, then re-boot attempt, then cleared cache and factory reset, then tried to boot, then wiped cache and factory reset followed by CWM recovery then boot attempt, then cleared cache, re-boot attempt, then all over again and flashed stock - all with no change - boot loop prevailed. What troubles me is that with no other changes the phone froze and re-booted on stock firmware?? And weirder still that once it re-booted the first time it stayed alive for 5 minutes, then 2 minutes, then less than 1, to 'that's all folks' and continued to decrease how far it even went in boot attempt. To the 'slightly informed' like me that seems strange - that's why I was wondering if it could be a hardware failure causing ROM or RAM to be corrupted further with each boot attempt - or - with time 'on'.??
Will try one click mf9 and post back
rimgarciag said:
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
JJ2013 said:
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
Click to expand...
Click to collapse
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Very wise advise
ROMANTiC KiD said:
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
The title say's it all - but this is very wise advise for us all! Electronics can suffer from infant mortality issue's, and I would agree 101% with you!
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
No to 4.3
BIGSAMDA1ST said:
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
I am actually sure it was on 4.2.2 the day it died - still had the notification nag that update was downloaded. I was going to look for how to remove that 'nagging' notification but hadn't yet. Since I rooted the day I got it and installed CWM any OTA update (4.3) should have failed even 'if' I accidently hit the 'system update downloaded' prompt on my notifications screen, which I didn't. The phone had been on for about 4 hours when it first locked and re-booted while texting - and had it updated it would have had to re-boot which I think I would have heard/seen/witnessed some kind of evidence that it had. I think you are going in a good direction though, looking at all possibilities. I know from root checker it rooted successfully and since I made a CWM backup I know stock recovery was gone - so very unlikely 4.3 found it's way in.
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Will try removing SD card
cruise350 said:
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
No, I only installed but never opened or set up folder mount so that never even crossed my mind. I just got home and have a few things to try - and I think the first and simplest is removing the SD card! OK, tried that to no avail - boot loop get's to samsung logo and repeats. Tried to clear cache and factory reset with card removed and tried again after battery removal for 2 minutes. Same situation - nothing has changed. Will try 1 step restore next. Downloaded on my laptop but had to leave that with a co-worker for data aquisition project - have to download again here at home.
This is off track, but I have never asked for help and//or participated in a forum like this before. I am happily suprised by the intelligent, thoughtful responses I have recieved so far. Didn't expect anything, but am glad I asked - and even though I am still 'stuck' I have had incredibly good input into potential resolutions for this issue. Thank you all for the assistance so far
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Verified through download mode - no Knox line present
cruise350 said:
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
No luck - bricked or dead phone...
JJ2013 said:
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
Click to expand...
Click to collapse
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
JJ2013 said:
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
Click to expand...
Click to collapse
I haven't tried this and not sure of the possibility of it working but if you could establish a connection via fastboot or download mode to a computer running adb you could be able to pull the log from dev/log/ and see exactly what is going wrong.
Look here http://stackoverflow.com/questions/12995030/how-to-use-adb-pull-command for info on pulling files in adb
Sent from my SPH-L720 using XDA Premium 4 mobile app
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
HELP
JJ2013 said:
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
mndbtt said:
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
Click to expand...
Click to collapse
No garantee, but I had rooted mine before it went haywire and bootlooped. When I took it in they had the phone for 15 minutes in the back out of my site - expect they went into download mode and could see it was not original (rooted) but replaced it anyway without any fanfare. BTW, after 3 weeks with the new device I rooted it as before - this time using TWRP becouse I had recently helped a friend root a tablet and used TWRP recovery - liked it so... In any case, I have had my rooted S4 (#2) running without issue ever since.
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!
Hello all! This is the second time this has happened to me, I've rooted my phone for about a week, and then for some reason when I decide to restart my phone -- it no longer boots up. It is stuck at the t-mobile screen and vibrates for a bit then stops, I have booted in to recovery mode and tried wiping that cache, but to no avail.
Any help would be appreciated -- or even how I can backup my data would be great too.
Wah gwan! My T-Mobile S7 Edge running TekHD v2. To have your phone running very nicely, you need to download the APD8 fireware. Make sure everything on your phone running APD8. download the files from max on highonandroid, flash the tar file twice using modified Odin from max. Once boot up screen say custom, next step download and extract TekHD.rar file .there's a part in the file that operates like cmd, right click and let it do its thing. Make sure your phone is on and a low USB debugging.
---------- Post added at 10:09 PM ---------- Previous post was at 09:43 PM ----------
Also this TekHD Rom is best for unlimited hotspot for Windows, Android and Mac. I have download about 20 more GB of files to make sure its good. The tutorial from max is good, the easiest way I see so far is to click on the root.dat in max files to add superSU. For TekHD click tekhd.bat. That was the easiest way after flashing the tar file. The hold process take 2 minutes once done right. I'm not a developer but a big Samsung Android fan. I have a Note 3,4,5 S6 Edge+ and S7Edge, I tried and tested many Roms at my own risk. Never had any problems. Make sure you always have the stock rom tar file for your device before any flashing any roms, is case something goes wrong you can start over.
first of all this is an eng boot root, so expect some hiccups and proble.. before u root make sure u back up everything then odin back to stock then root or else u will run into problems
You're going to have to ODIN back to stock. This seems to be happening to a lot of people (myself included) and a stock flash is the only way anyone has been able to recover. Flash all 4 files in ODIN simultaneously, but if you don't have a backup, try flashing the Home_CSC and see if it'll boot. I've heard reports that the Home-CSC file doesn't wipe your phone. If that doesn't work, then unfortunately you're going to have to re-flash, but this time use the standard CSC file, which will wipe your phone. Good luck.
I just had this happen for my second time and was stuck phoneless out of the house :/ I wish we could figure out the cause... Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
ph00ky said:
Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
Click to expand...
Click to collapse
No, that is not related, dm-verity verification fails because recovery still checks dm-verity even though the kernel does not.
Damn same thing just happened to me at work. Had to do factory reset...
When at that tmobile screen, hold down volume down + home button + power. It will reboot,and as soon as it does, switch volume down to vol up until it loads recovery to reset
This happened to me also. Go to lockscreen and security options and disable automatic security updates.
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
I can almost certainly say that the vibrate crash has something to do with the phone installing something behind the scenes. After getting the Amazon/Google/Samsung services multiple crash followed by the reset to the vibrating T-mobile screen I did a non-wipe ODIN, which works and works perfectly. What seems to not work though is re-installing root, it just leads back to the same screen, so I think Samsung is pushing something sneaky onto our phones probably through the security thing as mentioned.
---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
TekHD Only works on PD8, it's mentioned in the thread.
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
Can't run that ROM on APG1. If you want to try it, you will have to ODIN PD8. There is a post in a thread in this section that shows how.
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
rp3 said:
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
Click to expand...
Click to collapse
That might work to prevent this problem -- but what needs to be reverted once this problem starts? I can flash stock PG1 and if I use the (home_csc) it will fix the problem and not wipe my data.... but if I reflash the engineering bootloader it goes back to hanging at the tmobile screen.
im stuck on tmobile screen, and it keeps vibrating, idk what to do
swaggyyd said:
im stuck on tmobile screen, and it keeps vibrating, idk what to do
Click to expand...
Click to collapse
I haven't rooted but if your stuck just Odin back to stock.
I came to post that I'm having these issues as well, this is the second time it's happened to me.
The first time I had TEKHD on my Phone, and so with it constantly nagging to do a system update.
I figured when it did this the first time, it was because the update ran over my TEKHD side load "ROM" and corrupted. Ok , whatever, reloaded.
But now I'm just rooted, and stock ROM otherwise. Just happened to me again
Each time it's happened, I start getting "playstore has crashed" errors - dismiss and it comes right back. So I reboot, and then it boot loops and gets CRAZY hot. Man I've never been able to fry an egg on a phone quite like my S7 Edge...
Is there any light shed on what could be doing this? I may have to remain stock which makes me want to :crying: but I can't keep bothering my Work Admin's to unlock my Token account so I can re-register my same phone -
I shall try that home_CSC Flash when I get home though, hopefully I can recover it at least in a way to transfer token to my tablet or something.
posted that at work, I'm at home now. I tried to flash just the home CSC and that did not work, just booted into recovery with an error and wouldn't resurrect at all.
I shall try that disable auto updates thing though and see if it helps in the long run...
wotan2525 said:
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
Click to expand...
Click to collapse
you got a link for the home csc file you can send me I was good for about a month and a half and it finally happened to me as well and can confirm I was getting the play store/ google services errors right before the reboot and tmobile screen
Was having this issue as well, forgot that I needed to turn off Security policy updates.