Hi,
Given that I have had the misfortune (self inflicted) of 'upgrading' to the MH8 firmware I am finding that even rooted Tasker can no longer do the things it once did, e.g. reliably turn on/off bluetooth or even kill a basic app (even using root). I am wondering therefore whether I could use something like CM10.2 instead. My Knox warranty qfuse is stuffed as it is, so no point trying to stay true to stock any more and thought I might give CM10.2 a go.
The question I have is can this be done now that I have the Knox'ed bootloader?
If so is the installation the same as for a normal 10.2 install, and will I have to do a system reset? I am assuming yes to the latter, just wanted to make sure.
If someone is able to clarify that would be great - I don't expect warranty to be intact any more, clearly the boat has sailed, so would it be possible to run CM 10.2 or similar now?
I figured in for a penny, in for a pound so I went ahead and tried it anyway.
On the first attempt I noticed I only had around 2Gb of free space so did some digging and see that this is partly because you can't change the partition table on the S4 and, using a file browser, because it looked like I had some crud left over from before (despite clearing caches etc).
Using the recovery I tried formatting everything but that just soft bricked things, so I went ahead and re-flashed MH8 to get back to stock and then followed the steps to install CWM recovery and ultimately CM10.2 nightly. I now had the majority of the 9.25Gb available to me which is enough for my needs, although a shame you cannot just use all of the space as you wish and not as Samsung wants.
So far quite impressed with CM10.2, feels nice and snappy and obviously without most of the Samsung cruft. Just missing the S-View cover functionality at the moment but other than that I'm happy an will probably stick with it.
Related
I have a T-Mobile US Tab that was only rooted, but running stock firmware. I liked it and it ran well enough for me. However, last night it started lagging and locking up a lot, to the point I tried to reset. Well, it appears this has a bad load because wiping it from in the OS or in the recovery didn't do anything but make it worse to the point where it wouldn't get past the lock screen. I have 8 Android devices, and this is the first that didn't wipe correctly.
Fine, I figured I'd go ahead and try Overcome 1.2.0 with CWM (3.0.0.0 it appears) and make the move to EXT4. CWM is on it, but it isn't mounting /data correctly (complains about arguments and acts like it's still RFS, which it may be). So, what do I do now? I wouldn't mind going forward with the Overcome ROM and EXT4, but at the same time I'd also be fine with a working stock ROM. I downloaded Rotohammer's deodexed stock ROM for T-Mo Tabs, but I didn't think it would work since some of the partitions are likely EXT4.
So what's next? Any ideas?
Sorry to hear that, but you can fix it.
I would recommend only something that I have good experience with, and this is Modako kernel and ROM developed by Paulobrien.
I also have Tmo Tab and after flashing these two don't look any further. No issues so far and the Tab has no noticeable lag with any application.
That's a consideration as well. I'm going to check out his ROMs tomorrow when I'm more awake.
I wound up sending it in to the Samsung repair center in Texas, and it had a bad part on it (BGA, Ball Grid Array component?). It's due back on Wednesday, which is around 2.5 weeks after I sent it in.
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Sorry to hear, sometimes starting over cures 90% of all issues, and the os gets better each time.. If it were me, I would quit wasting time and odin.
Thanks, and good luck.
Don't Forget -
jedimyndtryx said:
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Click to expand...
Click to collapse
Don't forget to immediately freeze the ATT update apps... Or you will get the MF3 OTA... which, for now, is NOT-ROOTABLE & Custom Recoveries NOT-Installable.
I always factory reset,wipe both cache and format system.even when I use a back up.
Sent from my SAMSUNG-SGH-I337 using xda premium
Well I ODIN'ed and went back to CleanROM. So simple. I'm dying to try one of the VZW AOSP themed TW ROMs though. Decisions, decisions. Oh man....when I first got the phone it was on MF3. I spent 3 days on craigslist and found someone to trade me their non-updated phone. Still new to this Android business. So far I love it. Don't see why I spent so many years hating. Thank you all for the help.
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
sounds like a voltage prob....or mem prob... id redownload a new rom..wipe wipe wipe..reinstall and that should fix it
Sent from my SPH-L720 using xda app-developers app
Insufficient voltage at idle was my first thought too, but if you haven't undervolted (since you aren't even rooted), that seems less likely. If I were you, I'd root the phone so I could do more to figure things out. Maybe try bumping up the voltage a little on the lower clock speeds.
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Edit: did you buy this phone new or used? If you bought it used, more than likely somebody ruined it for you. And more than likely, you can fix it. If this was a new device, more than likely it will be a warranty issue. That's why you shouldn't do anything to void the warranty.
If you're going to use odin for anything, just make sure you follow someone's directions step by step. Otherwise very bad things can happen.
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
I'll look into Odin before I root. The phone was also purchased new. I spent most of today monkeying around with different settings to see if I could trigger the issue as well. As it turns out, the phone will only restart at idle if it's plugged into the charger, or the wifi is on. If wifi is off and it's not plugged in it's fine. I am also using the stock Samsung charger that came with the phone. Again though, if I'm actively using the phone it doesn't happen (charging or connected to wifi). I did turn the phone off earlier to charge it but would keep freezing at the sprint logo upon boot up. I thought it was bricked for a second... I wiped the cache (didn't do a factory reset) and that fixed it, but now I have that stupid issue where videos won't play on wifi, only on 4G or 3G. It's an issue I thought I had solved.
Le sigh. This is frustrating. The Odin option is looking to be my best bet it seems.
Tizamarou said:
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
Click to expand...
Click to collapse
Since you are running a custom source-built ROM, first thing to do would be to ODIN a stock ROM. If the problems go away, you have your answer. If not, this would likely be a warranty issue. Of course you tripped KNOX most likely already.
sputnik767 said:
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Click to expand...
Click to collapse
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Dfeeds said:
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Click to expand...
Click to collapse
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
rebooting
i had this problem once and it was related to a corrupt file on my sdcard believe it or not. there are Defraggers out there for your android file system and internal SD card but your Ext sc you would have to do on your PC. it worked for me. the one i used is called CLEAN i got it off amazon app store.
cyberweasal
Dfeeds said:
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
Click to expand...
Click to collapse
sputnik767 said:
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
Click to expand...
Click to collapse
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Dfeeds said:
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Click to expand...
Click to collapse
Great, I am glad it worked out, and hopefully your problem is resolved. I doubt that your old battery failed due to a bad partition, and I have to wonder how your partition got messed up in the first place, but that's just a curiosity and is irrelevant in the grand scheme of things. Just remember that if you decide to root, cf_autoroot works but will trip the KNOX bootloader and potentially void your warranty.
I had done the CF-Autoroot for my wifes (already second) S4 when it was still on the 4.2.2 back in late September, simply for AdAway, Titanium Backup, and the HotSpot mod. Well, after much time had passed she didn't know it was pertinent, and decided to uninstall Superuser because she didn't know what it was and it was causing her to have "a whole extra page in her app drawer". Needless to say, Superuser was broken, and she no longer has root. I tried just installing the original SU to no avail. I haven't messed with it any further. It's been so long since I rooted it, and it has been a crazy 6 months. I'm a bit fuzzy on the do's and don't's, so I did nothing more in fear of doing something that will trip KNOX or similar.
I've been reading, but can't seem to find a definitive answer.
First Issue - I would like to get her phone back to being 100% stock, non-rooted, no flags tripped or anything. This is the second incident she's had, and I've decided that the few advantages root gives her isn't worth bricking a phone or ruining the warranty and not being able to get a replacement. She drops them frequently, and complains about the Otterbox, so she frequently takes it off...
Second Issue - I have an identical setup - SPH-L720 handset running the stock recovery and stock 4.2.2 ROM, but it is still rooted. Is there a way to bypass KNOX completely to get a custom recovery on there? It seems like every thread I come across is rather unresolved. Ideally I would like to remove KNOX completely, flash to a custom recovery, and install a de-bloated ROM of some sort (Play Edition Clone/SlimBean, etc). What is the easiest and safest way to go about this, with an option to flash back to full stock still being available?
If both phones are on 4.2.2 which is MDC,MDL,or MF9 then you do NOT have Knox bootlaoder so you are fine to Odin MF9 tar or what ever version of those three that you have. And bmake sure to back up anything important.
Sent from my SPH-L720 using Tapatalk
I have been running CM (currently CM11) on my SGS4 since I bought it from Sprint in summer 2013. However, Sprint changed their international partners pretty seriously in the past 2 years, so I *really* need a PRL update for international travel. Normally the easiest way to do this is to reboot to stock or TriForce, run the "update PRL" and "update Profile" options from in TriForce, and go on with my life.
But I encrypt my phone. So I had to boot into TWRP, wipe and format *everything* and make sure the phone came up unencrypted in CM. All is OK.
So I reboot, flash TriForce 5.4 custom with stock (not KK) kernel. Flash works fine, I reboot... and am prompted to decrypt the device before I can do anything. None of the decryption passwords I've used in the past (I checked my password safe) are working. When I flash back to CM, it boots fine, and the settings says that the device is not encrypted.
I downloaded and tried TriForce 5.2 and 4.0, both are giving the same problem. I have used TriForce in the past on this phone, so it SHOULD be fine....?
Someone in #twrp said that the location of the encryption key changed from Android 4.4 to 5.0. So my only remaining thought now is that there was also a change from 4.3 to 4.4, and the encryption key for 4.3 didn't get removed in the wipe, and since the partition is NOT encrypted, the decryption, even if I have the right key, fails, so I can't get into the phone. Hope that makes sense.
Anyone have any guess better, or, if I'm right, know what I need to move/edit to fix this?
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
docsmooth said:
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
Click to expand...
Click to collapse
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
docsmooth said:
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
Click to expand...
Click to collapse
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
http://money.cnn.com/2015/05/21/technology/resell-android-phone/
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
mikeprius said:
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
Click to expand...
Click to collapse
I was never able to get the stock odin download. The whole problem came up because I was going overseas... I got around it by just buying a local SIM rather than using the Sprint roaming (again, I was doing all this just to update the PRL. new GSM SIM = no PRL update needed). On the way home less than a week later, I cracked the screen so bad the LCD and backlight wouldn't even go on.
I replaced it with a Nexus 6. A bit big, but it doesn't suffer Samsung software awfulness, so I didn't have to flash it with CM to make it usable.