Develop Bugs

[Q] Insufficient storage available-Installation errors & other aggravations?

Hey all, I've been getting "Insufficient storage available - Installation errors" on my EVO 4G eventhough I have a 32GB sdcard (but only 30MB of internal storage & yes I've moved all existing installed possible apps to sdcard, cleared caches & unmounted-remounted sdcard), what's the best way to resolve this?
I'm still running 2.2 unrooted but considering rooting soon & maybe cm7 or other rom but I'm not sure I want to risk issues when I need it working..
Also notice it is slow to respond upon reboot, maybe due to apps trying to update but encountering the insufficient storage available installation error..
-Appreciate helpful replies

BumpBump..

Dude you need to be rooted and switch rom bc stock evo don't allow you to place Apps on sd card, even with the apps2sd application
Sent from my PC36100 using XDA Premium App

You can try formatting your sd card. Also you should obtain S-OFF asap while you still have 2.2. I read a few threads about people's phones auto updating and now they are SOL!! Even if you don't flash a new rom you can get S-OFF b4 its too late. Get S-Off and ruu back to stock at least...

smartboy36 said:
Dude you need to be rooted and switch rom bc stock evo don't allow you to place Apps on sd card, even with the apps2sd application
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Not true. It just doesn't let you move all of them.
OP, rooting is going to give you some options, notably the ability to use an ext partition for your apps and/or dalvik cache. How many apps do you have? Even if every app were movable to SD (which of course it isn't), dalvik cache will eat up space on your /data partition. This is basically an optimized version of each installed application's code, and it can eat up as much as 1-2 MB per app. It's not listed in the app's storage usage under Settings -> Applications, and you can't do anything about it if you're not rooted.
Of course, another thing to look at is whether any apps are using excessive amounts of data. For example, I use Good messaging from work, and I have to clear data about once a month because the app accumulates data that never goes away. There's no option to purge or limit the amount of email it stores locally from within the app, and it stores big log files too.

Dude I'm on kings Alliance and I have 150 Apps with room for more. Come to the alliance and don't worry again
Sent from my PC36100 using XDA Premium App

This phone should've had more space for apps anyhow. Lol

I tried a new card today, same crap, I have about 100 apps..
jayare313 said:
This phone should've had more space for apps anyhow. Lol
Click to expand...
Click to collapse
Totally agree especially since it was originally released with 2.1, I got it the day the Nexus S was released which I seriously considered but since I use it a lot for Nav preferred EVO's larger screen & louder speaker.
I've been tempted to root & custom ROM since even before I got it but every time I read about brick risk I become less inspired to try it until I have another device I like as much as the EVO 4G..honestly what is the brick risk?
BTW, people keep telling me how much better the battery life is on cm7 etc, is there are a comprehensive chart of all the ROMs & battery life-feature set?
-Thanks

SMARTPHONEPC said:
I've been tempted to root & custom ROM since even before I got it but every time I read about brick risk I become less inspired to try it until I have another device I like as much as the EVO 4G..honestly what is the brick risk?
Click to expand...
Click to collapse
Very, very low. I can't say there's no risk, but as long as you follow the instructions, it's very low. I personally used Unrevoked back in the day. As others have mentioned, since you're still on 2.2, you should do it. Once you take the OTA update to 2.3, it's game over on rooting for now. You can even just root but leave the stock ROM on there. Just get S-OFF while you can.

the way i see it you have to purposely want to mess up your phone when it comes to rooting as long as you you got a recovery yer good

Ugh i have the same issue.
TO preface:
Yes I know how to free room up...see here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yet every time i try to install an app from the market OR even an APK on my SD card I get the insufficient storage space available.
I am rooted and on Synergy ROM but have never had this issue before. if ANYONE knows how to fix this that would be great. I can't even finish my restore from Titanium Backup.

DougB541 said:
Ugh i have the same issue.
TO preface:
Yes I know how to free room up...see here:
Yet every time i try to install an app from the market OR even an APK on my SD card I get the insufficient storage space available.
I am rooted and on Synergy ROM but have never had this issue before. if ANYONE knows how to fix this that would be great. I can't even finish my restore from Titanium Backup.
Click to expand...
Click to collapse
Hmmm rooted with space & you still have this ?

I think ive answered this question 10 times already .
All you have to do is install a task killer...kill all apps...then go download and install your app.
This always works for me
The error is memory..not storage
-storm

http://forum.xda-developers.com/showthread.php?t=855424

How bout everytime I post this, nobody lets me know if it worksfor them or not....
-storm

r.storm85 said:
How bout everytime I post this, nobody lets me know if it worksfor them or not....
-storm
Click to expand...
Click to collapse
Nope..
The other day when you posted it I was actually able to update-install a few apps without the error so I didn't need to try it but now that I was getting that error again I tried your suggestion with no difference. I was hoping it would be that easy but no such luck

SMARTPHONEPC said:
Nope..
The other day when you posted it I was actually able to update-install a few apps without the error so I didn't need to try it but now that I was getting that error again I tried your suggestion with no difference. I was hoping it would be that easy but no such luck
Click to expand...
Click to collapse
Oh ok cool.
It always works for me.
So maybe it is storage??
Its weird. First time I came across this I was trying to flash a recovery through terminal emulator.
I got this read memory error. Thay totally screwed my recovery.
It was fixed by killing all apps then installing the recovery.
Have you tried installing your apps right after a reboot??
-storm

r.storm85 said:
Oh ok cool.
It always works for me.
So maybe it is storage??
Its weird. First time I came across this I was trying to flash a recovery through terminal emulator.
I got this read memory error. Thay totally screwed my recovery.
It was fixed by killing all apps then installing the recovery.
Have you tried installing your apps right after a reboot??
-storm
Click to expand...
Click to collapse
Yup on trying to install apps right after reboot, it may have worked a couple times but doesn't work consistently now..
It's lame that the EVO only came with 1GB internal storage, I refused to get it until 2.2 in part because when it released with 2.1 you couldn't even natively run apps off microSD so you would have to rely on that whopping 1GB. I didn't anticipate having this issue with 2.2.
I still love my EVO but this is aggravating. Before I would try to root-customROMs I'd try to delete some non-essential apps, any suggestions on how much storage room to shoot for?
I didn't expect to still be unrooted stock 2.2 at this point but I may be more pissed if something went wrong than psyched with the added freedom-at least until I see my next phone in the market I like more than the EVO..

So my EVO became so unresponsive part of me wanted to take a bat to it, I had to remove the battery, reboot where it was still ridiculously slow, saw that my storage was down to 500k..
I deleted a couple apps & got it back up to 40MB, was able to update an app without this error but couldn't download another where the error occurred again. After another reboot was still getting a Low on space Notification but at least the EVO was useable again except when trying to open the Market-just hangs..
Considering backing everything up & doing a factory reset (& even dumping Android if the next iPhone is cool enough-but probably not )
I still can't believe HTC only put in 1GB internal storage for an otherwise great phone, EVO 3D is pretty cool but its speaker seems quite weak compared to EVO..
Thoughts?

[Q] PLEASE HELP!! Work phone w/ JMTx4 stuck at Samsung logo after battery died

NEED HELP RIGHT AWAY! WORK PHONE DEAD IN WATER!
My battery died during a boot and the phone is still stuck at the Samsung S screen. The boot sound plays and the samsung animation plays continuously but never gets further. I left it for 20+ minutes and rebooted trying several times without success.
I can still access TWRP recovery. I tried fix permissions and clear caches but same problem exists. I mounted the internal and external sd and did full backups to my PC but I do not have a current full backup in TWRP or nandroid I may have an older TWRP backup from just after flashing the ROM but does not have apps or data.
Is there anything I can do to repair the boot without reflashing the ROM? What would happen if I flashed the same ROM over the current ROM? Just want to know if there is a possibility that I would not have to completely resetup the phone.
I have been on here before but just created a new account to ask for help. I have read the ENTIRE Jedi Mind Trick Rom thread before but dont remember seeing anything that would help this and I really could use a solution ASAP!
Thanks in advance. Any help is very appreciated!!

DirtyBreakz said:
NEED HELP RIGHT AWAY! WORK PHONE DEAD IN WATER!
My battery died during a boot and the phone is still stuck at the Samsung S screen. The boot sound plays and the samsung animation plays continuously but never gets further. I left it for 20+ minutes and rebooted trying several times without success.
I can still access TWRP recovery. I tried fix permissions and clear caches but same problem exists. I mounted the internal and external sd and did full backups to my PC but I do not have a current full backup in TWRP or nandroid I may have an older TWRP backup from just after flashing the ROM but does not have apps or data.
Is there anything I can do to repair the boot without reflashing the ROM? What would happen if I flashed the same ROM over the current ROM? Just want to know if there is a possibility that I would not have to completely resetup the phone.
I have been on here before but just created a new account to ask for help. I have read the ENTIRE Jedi Mind Trick Rom thread before but dont remember seeing anything that would help this and I really could use a solution ASAP!
Thanks in advance. Any help is very appreciated!!
Click to expand...
Click to collapse
I think you would have to reflash, sorry . You should:
1.) Delete cache
2.) Delete dalvik cache
3.) Delete data/factory reset
4.) Flash new ROM
5.) Flash GApps (if not included in the ROM).
You might be able to salvage some data back by going into download mode, but I'm not to knowledgeable in that area. Good luck.

If you flash over your current rom with same rom you will still have your apps and data. All a dirty flash does is install new system apps from the rom itself so your data should not be effected.
Sent from my SGH-T989 using Tapatalk

Still wont boot
richardlibeau said:
If you flash over your current rom with same rom you will still have your apps and data. All a dirty flash does is install new system apps from the rom itself so your data should not be effected.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ok, I thought I remembered hearing that. I just reflashed the ROM over the old one without clearing any caches. Unfortunately the phone still gets stuck at the Samsung S boot screen. The animation continues and it does not appear frozen but it never goes anywhere.
I am thinking of wiping the system/factory reset then reinstall the ROM. before I do that though, is there any way to copy over files from the system partition before flash and then copy them back overwriting the current ones after flashing the ROM. Will this work since it is the same ROM? I dont care if its stable. Just want to recoup my data and backup and then I will completely redo the ROM again.
Thanks for your input guys!

Restore a backup
----------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm full of great idea's, but don't have the time to create them or learn the coding to create them. If you want to make one of my ideas a reality just message me and I will give you my idea as specific as possible.
ideas:
-launcher/lock screen
-line rider type game where you control the character
-2d fighting game like art of fighting for the SNES
-multiplayer fps where you create your own map with a creative mode (minecraft style)
-roller coaster tycoon style game
-many more!
Just message me which idea you want info on and I'll tell you!
----------------------------------------------

DirtyBreakz said:
Ok, I thought I remembered hearing that. I just reflashed the ROM over the old one without clearing any caches. Unfortunately the phone still gets stuck at the Samsung S boot screen. The animation continues and it does not appear frozen but it never goes anywhere.
I am thinking of wiping the system/factory reset then reinstall the ROM. before I do that though, is there any way to copy over files from the system partition before flash and then copy them back overwriting the current ones after flashing the ROM. Will this work since it is the same ROM? I dont care if its stable. Just want to recoup my data and backup and then I will completely redo the ROM again.
Thanks for your input guys!
Click to expand...
Click to collapse
Do a full back up now then wipe the whole phone, Flash new rom then boot into recovery and go to advanced restore and you can just restore system or data instead of the whole back up. But it sounds like your problem is in your system somewhere though since it is not booting all the way. Do you have scripts that clash? Tweaks etc. Try flashing a new kernel and see if it boots up.

richardlibeau said:
Do a full back up now then wipe the whole phone, Flash new rom then boot into recovery and go to advanced restore and you can just restore system or data instead of the whole back up. But it sounds like your problem is in your system somewhere though since it is not booting all the way. Do you have scripts that clash? Tweaks etc. Try flashing a new kernel and see if it boots up.
Click to expand...
Click to collapse
Ok. I flashed the same rom over top of the current one and got the same results. I then booted into recovery, wiped system, flashed the rom again and got the same results.
One thing I noticed is that when I ran fix permissions both before I reflashed and after, it was super quick to finish lasting only a couple seconds where normally it takes a couple minutes for fix permissions.
I did a backup in TWRP right after the crash. I will try flashing a kernal as a last attempt before doing a full wipe and flash. I have to find which kernel it is. Do you recommend flashing the same kernel or a specific kernel?

DirtyBreakz said:
Ok. I flashed the same rom over top of the current one and got the same results. I then booted into recovery, wiped system, flashed the rom again and got the same results.
One thing I noticed is that when I ran fix permissions both before I reflashed and after, it was super quick to finish lasting only a couple seconds where normally it takes a couple minutes for fix permissions.
I did a backup in TWRP right after the crash. I will try flashing a kernal as a last attempt before doing a full wipe and flash. I have to find which kernel it is. Do you recommend flashing the same kernel or a specific kernel?
Click to expand...
Click to collapse
What rom and os are you on ics or jb? Same kernel is ok but a new one might be better
Sent from my SGH-T989 using Tapatalk

richardlibeau said:
What rom and os are you on ics or jb? Same kernel is ok but a new one might be better
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I'm running Jedi Mind Trick x4 (JMTx4) ICS with its kernel. It looks like it uses Faux kernel. Not sure where to get it or one that will work. I was just looking through the thread here and also googled it but didnt get much. I went to the Faux repository but it was a bit confusing. I have never downloaded or flashed a separate kernel. Always just used the one packaged with the rom. Please direct me to a link to place to download the kernels that I could use with this rom.

DirtyBreakz said:
I'm running Jedi Mind Trick x4 (JMTx4) ICS with its kernel. It looks like it uses Faux kernel. Not sure where to get it or one that will work. I was just looking through the thread here and also googled it but didnt get much. I went to the Faux repository but it was a bit confusing. I have never downloaded or flashed a separate kernel. Always just used the one packaged with the rom. Please direct me to a link to place to download the kernels that I could use with this rom.
Click to expand...
Click to collapse
Any of these will work. I can't find faux right now. Just flash and reboot.

richardlibeau said:
Any of these will work. I can't find faux right now. Just flash and reboot.
Click to expand...
Click to collapse
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.

DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.[/QU
Corruption is usually in the system somewhere so that's odd. Hopefully one of the kernels will help you.
Click to expand...
Click to collapse

richardlibeau said:
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.[/QU
Corruption is usually in the system somewhere so that's odd. Hopefully one of the kernels will help you.
Click to expand...
Click to collapse
Ok. I restored data again and confirmed no boot, then flashed the new kernel and still no joy
Looks like something is corrupted in the data. Do you know of anything else I can try before fully wiping/reflashing again?
Click to expand...
Click to collapse

Not at this point sorry. Seems that something really weird. Best just to reflash now and be glad it's not fully bricked.
Sent from my SGH-T989 using Tapatalk

richardlibeau said:
Not at this point sorry. Seems that something really weird. Best just to reflash now and be glad it's not fully bricked.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Right on! Thanks again for all the advice. Just a quick question before I am off to reflash again...
Is it possible to recover any information from the data in the twrp backup once I have reflashed? Mainly looking for text notes from Note Everything and SMS messages.

If it's a tar file you can through a file explorer that can open tar files like winrar, winzip. etc. You just extract what you want. So yes you can salvage things that way.
Sent from my SGH-T989 using Tapatalk

file and data recovery
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.
Click to expand...
Click to collapse
I know I'm about two weeks after this one, but here are some thoughts on accessing the data in the backup.
My arsenal includes Root Explorer, FX Explorer by nextapp (File Explorer is the name that shows up in google play), ROM Manager, and Titanium Backup.
I do not use Root Explorer nearly as much as I use FX. To me, FX is easier to use, runs in the background, and can run multiple operations at the same time.
FX Explorer can extract .tar files so you can pull individual files from the archive, but it extracts the entire contents of the archive. FX Explorer can also mount read/write of the /system if the phone is rooted. You will get a little nag screen every time you mount r/w, but that's about it.
Yes, it's worth paying the couple of bucks in Google Play for the full versions of these apps. The only caveat with FX Explorer is that in order to get FULL app functionality, you have to install it in modules. I think there are a total of 4, maybe 5 modules for the app. The main app which is free, the root module which is NOW free, there is a paid module for media, and a paid module for network functionality which includes hosting a file server on the phone as well as accessing Google Drive, skydrive, and other cloud based storage solutions.
Titanium Backup can also pull individual app apk's out of a Clockwork Nand backup, but it will miss /lib files that some apps like swype need.
FYI, I just installed JMTX4 for my T989, and wanted the Swype from the stock rom. Turns out, installing JUST the swype apk out of the backup wasn't enough. Using FX, I extracted the system .tar portion of the backup, and extracted the two files I needed, including the swype apk, and using FX, I pasted them into the /system/app and /system/lib directories as the link I found said to do, only I did it directly on the phone without having to use the adb interface from my pc.

Not to revive an old thread but I wanted to update so others may be able to use the info.
Found out that the reason for the crashes was a hardware (power button) issue. The power button would get stuck in several different positions causing the phone to reboot or boot loop and not boot at all. T-mo was nice enough to replace my phone out of warranty for me after a little haggling so no more issues
I have since updated and running Jedi Mind Trick JBv4 now. I actually think I like JMTv4 better. It runs great. I'm just not entirely fond of some of the new Android changes in JB.

DirtyBreakz said:
Not to revive an old thread but I wanted to update so others may be able to use the info.
Found out that the reason for the crashes was a hardware (power button) issue. The power button would get stuck in several different positions causing the phone to reboot or boot loop and not boot at all. T-mo was nice enough to replace my phone out of warranty for me after a little haggling so no more issues
I have since updated and running Jedi Mind Trick JBv4 now. I actually think I like JMTv4 better. It runs great. I'm just not entirely fond of some of the new Android changes in JB.
Click to expand...
Click to collapse
my phone is doing the same thing. what did you say to tmobile?

adamwithane said:
my phone is doing the same thing. what did you say to tmobile?
Click to expand...
Click to collapse
Call tech support and tell them you are having problems with your power button. Hopefully you will get a helpful rep. If not, call back and try again. If you are in warranty it should be no issue.

Looking For some Guidance

Hello my Fellow s4 users,
Let me start off by saying I am looking for a little guidance here. I am fairly comfortable with rooting, modding, NANdroiding, Flashing, bricking, unbricking, following instructions and using the search button. I am a little dumbfounded on some of the issues I am having.
The issues seem to be isolated to touchwiz based roms only. GE and AOSP ROM's are not part of this problem.
My problem is that anytime I flash a TW based rom (For Example: The little Minions Rom, Infamous, or Wicked), which flash just fine, upon loading or the first time System UI always crashes. I click ok and let the phone sit for about ten minutes to settle. I reboot, and go through the setup wizard ( I have also done it where I skip the setup wizard altogether, with the same results.)
At this point everything is ok.
Until I try to do anything else. I experience extreme Lag, problems with apps Like the phone and Contacts, Titanium Backup is simply non-functional.
So at this point I assume it is user error.
So I Odin back to stock, run triangle away and start fresh.
I repeat this process, and root using the CF-Auto root, and reflash a rom with the same result.
The only thing I can think to do at this point is ODIN back again and try a different Root method.
Does anyone have any ideas or input?

Personally, I'm running Infamous S4 4.0 ROM w/BioShock 1.0 Kernel and 3.1.1 3Minit Framework. Have not experienced the issues you're describing though. You seem to have taken many of the appropriate steps to attempt to solve your issues.
The steps I'd do and some stuff I'd look at, whether related to your issues, and/or tried already are:
- if using TWRP Recovery 2.6.0.0, flash TWRP 2.5.0.2.
- if not already, format card, if 64gb, to Fat32, as some ROMs won't run ExFAT.
- Full Wipe and ODIN Samsung Stock Firmware.
- Save files needed and Full Wipe, including device memory, as you may have a conflict with certain files.
- with Infamous S4, it has Root, so it's not necessary to root via CF-AUTO-ROOT, but can't hurt I guess. CF-AUTO-ROOT is my preferred choice for rooting.
- Uninstall and reinstall TiBu if having issues after doing the above.
- Sometimes when there are issues after flashing ROMs, wiping Cache and Dalvik cache can rectify many issues.
- make sure running appropriate Kernel for the M919. Appropriate Radio goes without saying, although most ROMs don't have the Radio cooked in because the wrong Radio can Hard Brick.
Anyway, I'm sure I missed something which may turn out to be the Golden Challis :laugh:, but the above hopefully will help.
As a note, and possibly to get more feedbackffrom the source, you can post your inquiry regarding Infamous S4 in thetthread as all are extremely helpful, and the Developers offer excellent support. The same with Minions, as they are part of the Infamous Team. I don't run Wicked ROM but have heard excellent feedback, and their support appears to also be excellent.
Feel free to copy this post if you'd like to post it in Infamous S4 thread, as there'll be others to expand on my response

OP:
What phone?
What baseband?
What recovery?
I am M919 tmobile
MDL
CWM.
...and have no issues with Wicked 5.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-M919 using Tapatalk 4 Beta

Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
Sent from my SGH-M919 using xda premium

ODIN Recovery tips
3r0k said:
Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
You may find TWRP 2.6.0.0 the cause of some issues, and that 2.5.0.2 will resolve them.
I'll post some ODIN Recovery tips, if you should need them:
Here's the TWRP 2.5.0.2 file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
Install with ODIN.
Steps to follow........
Method #1 -
Place file in PDA box*
Uncheck all other boxes.
Press start.
When installation is complete, unplug usb cord and pull the battery.
Insert the battery but Don't turn on the phone.
Place phone in Recovery mode via the Power + Volume up buttons.
Method #2 -
The other way I've read to install TWRP Recovery is:
Place the TWRP 2.5.0.2 tar in the PDA box*
Check the auto reboot box and f time reset box.
Start the installation and let the phone reboot.
I believe the above method is the method of choice, but sometimes the Recovery doesn't take, so Method #2 above is recommended.
Here is an explanation why:
http://forum.xda-developers.com/showpost.php?p=41166759&postcount=28

Gunkk said:
OP:
What phone?
What baseband?
What recovery?
I am M919 tmobile
MDL
CWM.
...and have no issues with Wicked 5.1.
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
everything same as you except Im using twrp.

There's your sign...
Sent from my SGH-M919 using Tapatalk 4 Beta

Ok, getting home in a bit will keep you guys updates. thanks for the help.

3r0k said:
Ok, getting home in a bit will keep you guys updates. thanks for the help.
Click to expand...
Click to collapse
Sounds :good:
ODINing 2.5.0.2 I think will solve your issues.
Wipe cache and dakvik cache after booting into Recovery and prior to booting system.
If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.
Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed

Biker1 said:
Sounds :good:
ODINing 2.5.0.2 I think will solve your issues.
Wipe cache and dakvik cache after booting into Recovery and prior to booting system.
If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.
Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed
Click to expand...
Click to collapse
Yea, still gettting errors.
Even tried to switch to CWM, and that had issues with backing up.
Looks Like I am gonna ODIN Back and full wipe.

3r0k said:
Yea, still gettting errors.
Even tried to switch to CWM, and that had issues with backing up.
Looks Like I am gonna ODIN Back and full wipe.
Click to expand...
Click to collapse
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.
ODIN TWRP 2.5.0.2 and you should be good to go.
If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.
20m all together;
Firmware.
Recovery
ROM/Kernel
Infamous S4 Roots you, so hopefully you'll be up & running i nno time.
Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.
In your case, TWRP 2.5.0.2 only was worth a shot

Biker1 said:
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.
ODIN TWRP 2.5.0.2 and you should be good to go.
If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.
20m all together;
Firmware.
Recovery
ROM/Kernel
Infamous S4 Roots you, so hopefully you'll be up & running i nno time.
Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.
In your case, TWRP 2.5.0.2 only was worth a shot
Click to expand...
Click to collapse
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.

3r0k said:
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.
Click to expand...
Click to collapse
If you:
- did a Full Wipe
- ODINd Samsung Stock Firmware
- ODINd TWRP 2.5.0.2 Recovery
- checked your ROM download
- Flashed your ROM (with Kernel cooked in)
- Wiped cache and dalvik cache
and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.
Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.

Biker1 said:
If you:
- did a Full Wipe
- ODINd Samsung Stock Firmware
- ODINd TWRP 2.5.0.2 Recovery
- checked your ROM download
- Flashed your ROM (with Kernel cooked in)
- Wiped cache and dalvik cache
and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.
Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.
Click to expand...
Click to collapse
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.

3r0k said:
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.
Click to expand...
Click to collapse
At this point the only thing I can suggest is to:
- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.
I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.
I then come back to the issue and say, 'Hmmm, how'd I miss that?'
And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'
I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.
Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.
Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.

And you say this only happens on Touchwiz roms?
What about the stock touchwiz after you odin back to stock? Does that give you similar problems?
If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
And you say this only happens on Touchwiz roms?
What about the stock touchwiz after you odin back to stock? Does that give you similar problems?
If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
Stock ROM works great.
Wicked is now working and running great also.
I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.
I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.

Biker1 said:
At this point the only thing I can suggest is to:
- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.
I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.
I then come back to the issue and say, 'Hmmm, how'd I miss that?'
And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'
I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.
Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.
Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.
Click to expand...
Click to collapse
No apology needed, you have by far been the most helpful.
Maybe Ill just wait for a new build to come out and go from there.
Maybe Ill possibly look into a log cat to send the Dev. I dont know if the log can catch the errors in my process but maybe.

3r0k said:
Stock ROM works great.
Wicked is now working and running great also.
I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.
I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.
Click to expand...
Click to collapse
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?
If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.
If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?
If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.
If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
If I did restore any other system data it would be coming from other touchwiz ROMS, however I am not. The problem is at least on the ROMS I am having difficulty with I cant get far enough to reinstall TiBu anyways. The systemUI crashes immediately as soon as the setup wizard loads, then when I get to the Wi-Fi password screen, the settings force close and the Setup Wizard starts all over again.

[Q] Finally kitkat is available for my note... should I upgrade?

Hi,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know whether to upgrade or not..
I'm rooted on stock 4.2.2
My warranty was void since the first day I bought my note 8... I don't have something to worry about..
I'm talking about KNOX.. is there any topics to explain what is it? and what's bootloader?
Will I'm be able to root it again after upgrading? Can I revert back to 4.2.2 if something went wrong?

AhmadLight said:
Hi,
View attachment 2778433
I don't know whether to upgrade or not..
I'm rooted on stock 4.2.2
My warranty was void since the first day I bought my note 8... I don't have something to worry about..
I'm talking about KNOX.. is there any topics to explain what is it? and what's bootloader?
Will I'm be able to root it again after upgrading? Can I revert back to 4.2.2 if something went wrong?
Click to expand...
Click to collapse
Knox is a set of security tools included in the Kitkat update that lock down the device to prevent misuse and modification. This is great in a business/enterprise environment because it means that a company can buy Samsung devices, configure them however they want, and in theory a user is less likely to hack it for themselves.
For those who aren't part of a company or enterprise environment, Knox is a pain. Not only will it prevent you from rooting it (if you don't use the right root method), but it also is aware if you do root or try to flash a custom ROM to it. Included in Knox is a new bootloader (part of the firmware that manages the actual boot process of the device); part of that bootloader is a non-removable, non-editable e-Fuse. The e-Fuse detects if any non-officially signed software is flashed to the device. If it finds anything (Custom recovery, root package, custom ROM), the e-Fuse is permanently tripped and Samsung will no longer touch that device.
The e-Fuse is separate from the flash counter, which CAN be reset with a tool like TriangleAway (Flash counter is exactly what it sounds like; a counter that counts how many times the device is flashed with custom modification).
I realize this isn't an issue for you, as you don't care about the warranty. If you don't, then great! Hack and modify your device all you want to. Root, flash ROMs, modify kernels, do whatever.
I will say that before I upgraded to stock 4.4.2, I did try out a few custom ROMs available for the Note 8.0. I didn't find a single one that really fit the bill for me, and frankly found all of them to be a bit sluggish compared to the stock ROM; a surprising change-up from what I'm used to. I also rely a lot on the S-Pen, which didn't have the functionality I was looking for in any other ROM. So I'm flashing back to stock and upgrading to 4.4.2 so I can use the S-Pen exactly how I'm used to. I too don't worry about the warranty, so if I find a root method that works I'll probably root just so I can have that access, but I probably won't flash another ROM to it.

Sure, though losing writing to the card...
Via my Note 3

I would wait to see if someone can root it. I miss root on my note3 with kk. Otherwise I love it. PGP and programs that need to write while in external just will not work on the new bootloader.
Sent from my GT-N5110 using XDA Premium 4 mobile app

Just researched and tested stuff out; the same root process as before still works with 4.4.2.
http://forum.xda-developers.com/showthread.php?t=1980683
So, flash CF-Auto-Root with Odin, update SuperSU after rooting is finished, then disable Knox in SuperSU. I'm assuming updating it right from the Play Store will work just fine, but I'll report back if I have any problems with it. My Note 8.0 is busy updating everything else at the moment :-/
EDIT: Here's a better link for CF-Auto-Root for the N5110:
http://download.chainfire.eu/318/CF-Root/CF-Auto-Root/CF-Auto-Root-konawifi-konawifixx-gtn5110.zip
EDIT: SuperSU finally updated through the Play Store, no problems as anticipated.

As far as updating it's mixed. The multi user is great but loosing the ability to write data to the SD is frustrating. I knew we lost the ability to move apps but I didn't realize we lost the ability to move data. So now my podcasts and maps from Osmond have to set on the tablet. It's not gonna fit.
life is better with r00t

kenhicg said:
As far as updating it's mixed. The multi user is great but loosing the ability to write data to the SD is frustrating. I knew we lost the ability to move apps but I didn't realize we lost the ability to move data. So now my podcasts and maps from Osmond have to set on the tablet. It's not gonna fit.
life is better with r00t
Click to expand...
Click to collapse
What's that?? writing to SD isn't allowed without rooting?

no.
Kit kat gave me nothing. It did make my spen offset by an eighth of an inch. It made the handwriting recognition much worse in user interface and functionality. I can no longer disable the service that puts the recommended spen apps in my notification bar. My battery life seems worse but that may be because I reset the tablet and havent configured all the settings yet.
Im researching a way to flash 4.2 back on it. Its hard to find anything on this site but I did find this:
http://www.sammobile.com/firmwares/3/?download=19789
I have a usa galaxy note wifi version. If anyone with experience sees my post I would greatly appreciate it if you could reply and let me know if if this will work. Im not sure if flashing from kit kat is possible. I don't have any knowledge about this kind of stuff but I can follow directions and I was in love with my tablet before this happened.
Thank you for any help or information. I will update this post once I have decided to make a move towards flashing 4.2 back.

Apps still move to a degree.
Sent via my Note 8

AhmadLight said:
What's that?? writing to SD isn't allowed without rooting?
Click to expand...
Click to collapse
Nope doesn't work. Blame Google.
life is better with r00t

Sure. After upgrading to kitkat. I noticed that apps are opening much smoother and quicker resulting in significant improvement in battery life. Also I noticed that there is less heat issue with kitkat as compared to jellybean.
Sent from Death Note

If you want to use an sd card don't do it. I can't even access my music anymore.
Edit well I may have had a bad sd card beacuse everything seems to be ok including move to sd.
Sent from my iPhone using Tapatalk

kenhicg said:
If you want to use an sd card don't do it. I can't even access my music anymore.
Edit well I may have had a bad sd card beacuse everything seems to be ok including move to sd.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You ever get the SPen issue worked out? I updated from a clean install of 4.2.2 and I have had no issues with SPen tracking.

mstrswrd06 said:
You ever get the SPen issue worked out? I updated from a clean install of 4.2.2 and I have had no issues with SPen tracking.
Click to expand...
Click to collapse
I've got got hit by the S-Pen issue. Mine is a Canadian Note 8 that went from 4.1.2 directly to 4.4.2. The S-Pen accuracy is now off and for me, that wipes out whatever speed and response benefits may have come with KitKat.

shardsx said:
I've got got hit by the S-Pen issue. Mine is a Canadian Note 8 that went from 4.1.2 directly to 4.4.2. The S-Pen accuracy is now off and for me, that wipes out whatever speed and response benefits may have come with KitKat.
Click to expand...
Click to collapse
Does a factory reset fix the problem?

Fortunately I never had an issue with the spen.
life is better with r00t

@kenhicg
Again about writing to SD... I didn't get what you mean??
Wouldn't I be able to move or read data from my SD Card?? What about moving apps to SD?
What I understood is that you'd a problem with your SD card

AhmadLight said:
@kenhicg
Again about writing to SD... I didn't get what you mean??
Wouldn't I be able to move or read data from my SD Card?? What about moving apps to SD?
What I understood is that you'd a problem with your SD card
Click to expand...
Click to collapse
They were telling us that their SD card was bad. That's why they were having problems with moving data to and from that card.
I just tested my SD card by copying a small PDF from my card to internal storage, deleting from the card, then copying back from internal storage back to the card. Worked fine; I used Root Browser.
Then again, I don't use my SD card for apps or Android data. So I'm not fully testing it, but just a quick read/copy/delete/write worked fine with that PDF I used.

newbiechris said:
Kit kat gave me nothing. It did make my spen offset by an eighth of an inch. It made the handwriting recognition much worse in user interface and functionality. I can no longer disable the service that puts the recommended spen apps in my notification bar. My battery life seems worse but that may be because I reset the tablet and havent configured all the settings yet.
Click to expand...
Click to collapse
I would pay money to be able to revert back to 4.1.2 (I'm in Canada, we never got 4.2.2.). l also have the s pen offset issue and questionable battery life, although I've only done a couple of charges since upgrading. Hate the new handwriting input panel. I actually did use the page buddy features when I took out the s pen or plugged in my headphones. Very annoyed that this feature has been removed. Another peeve is that whenever the pen is just hovering over the screen, the menu and back touch keys light up. l had to shut the lights off entirely to keep them from coming on every time I moved the pen.
For all the hype about Kitkat, I really don't see much difference other than things that now don't work properly.

AhmadLight said:
Hi,
View attachment 2778433
I don't know whether to upgrade or not..
I'm rooted on stock 4.2.2
My warranty was void since the first day I bought my note 8... I don't have something to worry about..
I'm talking about KNOX.. is there any topics to explain what is it? and what's bootloader?
Will I'm be able to root it again after upgrading? Can I revert back to 4.2.2 if something went wrong?
Click to expand...
Click to collapse
i upgraded just for civato's kitkat rom. i like kitkat. i see marked improvement from jelly bean. but maybe that's just me. and absolutely not, you will brick your note if you try to downgrade to a 4.2.2 touchwiz rom. i think you could downgrade to an aosp 4.2.2 (don't quote me on that) but it's a totally different experience.
if you insist on staying stock a large offset to the s pen's accuracy comes with the upgrade. civato's rom and kernel fixes that though.
AhmadLight said:
@kenhicg
What I understood is that you'd a problem with your SD card
Click to expand...
Click to collapse
i have a lot of apps on my 64gb sd card with no issues.
EDIT: though again, i must stress, i am running a custom rom. i cannot speak for stock, but i am happy with my decision.

[Q] Losing root on deknoxed debloated stock 4.4

My phone has lost root twice now. It acted very strange when this happened. Hopefully you guys can help.
I'm on the stock kitkat 4.4.2 that I personally deknoxed and debloated. I have xposed framework and just a couple modules installed for it (gravity box, app settings, and keepchat) Everything is the same as it was on my phone when I had 4.3 app wise.
The first symptom I notice is that tapping the power button wont make the screen go to sleep. Holding it still brings up the power menu.
The first time it did this it also wouldnt connect to wifi and ate battery like crazy.
Used the flash zip to disable xposed and dirty flashed the rom. This fixed the wifi but not the power button.
Ended up totally flashing back to stock 4.4.2 with Odin and redoing everything. Downloaded pretty much all the apps from the app store and only used titanium backup to restore data on a couple things.
Everything worked fine ~3 weeks. Today it stopped working again. All the same symptoms. Absolutely nothing was changed between when it was working and when it stopped. All I did was reboot because I wanted to run speedtest from a clean boot. (comparing sprint 4G with verizon 4G at a friends)
Went to disable xposed straight from the app and it said it couldnt because I didnt have root. Downloaded rootchecker and it agreed that I did not have root.
Suddenly it started working again. Passed root checker and all. Then a couple minutes later it stopped again.
Downloaded towelroot and re-rooted with it. Everything seems to be back to normal for now.
Any ideas? Theories? Investigative follow up questions?

thedumbass said:
My phone has lost root twice now. It acted very strange when this happened. Hopefully you guys can help.
I'm on the stock kitkat 4.4.2 that I personally deknoxed and debloated. I have xposed framework and just a couple modules installed for it (gravity box, app settings, and keepchat) Everything is the same as it was on my phone when I had 4.3 app wise.
The first symptom I notice is that tapping the power button wont make the screen go to sleep. Holding it still brings up the power menu.
The first time it did this it also wouldnt connect to wifi and ate battery like crazy.
Used the flash zip to disable xposed and dirty flashed the rom. This fixed the wifi but not the power button.
Ended up totally flashing back to stock 4.4.2 with Odin and redoing everything. Downloaded pretty much all the apps from the app store and only used titanium backup to restore data on a couple things.
Everything worked fine ~3 weeks. Today it stopped working again. All the same symptoms. Absolutely nothing was changed between when it was working and when it stopped. All I did was reboot because I wanted to run speedtest from a clean boot. (comparing sprint 4G with verizon 4G at a friends)
Went to disable xposed straight from the app and it said it couldnt because I didnt have root. Downloaded rootchecker and it agreed that I did not have root.
Suddenly it started working again. Passed root checker and all. Then a couple minutes later it stopped again.
Downloaded towelroot and re-rooted with it. Everything seems to be back to normal for now.
Any ideas? Theories? Investigative follow up questions?
Click to expand...
Click to collapse
for some reason that happens to me when I'm on stock not on any other custom rom but when i clean flash a new rom everything is fine but if i Odin back to stock or flash one of the stock rooted via recovery i lose root a lot and when i re-root with Philz touch recovery i cant update the su binary with super su so i cant help you minus the flash a different rom answer I'm sorry :/

Not the answer I want to hear. But it is an answer and its appreciated.
By custom are you meaning stock based custom or full custom/AOSP based?
I know there are some stable custom roms out there but I like the general stability of stock especially since I still need to update my girlfriend's phone. She needs something that works all the time and a reboot will fix 99.9% of the issues she might see.
Our S3s are both ported to Ting. Hers is rooted mainly for the debloat and easy backup/recovery abilities. I told her until I knew mine was stable to just stay on 4.3 and ignore the update notification. She's had zero issues and I've had this one plus the external SD write crap. I'm definitely the nerd of the two of us and getting into flashing custom roms would be too much for her.
This might end up pushing me to something custom. If I do I'll just leave her behind at 4.3 and kill her update notifications permanently.

thedumbass said:
Not the answer I want to hear. But it is an answer and its appreciated.
By custom are you meaning stock based custom or full custom/AOSP based?
I know there are some stable custom roms out there but I like the general stability of stock especially since I still need to update my girlfriend's phone. She needs something that works all the time and a reboot will fix 99.9% of the issues she might see.
Our S3s are both ported to Ting. Hers is rooted mainly for the debloat and easy backup/recovery abilities. I told her until I knew mine was stable to just stay on 4.3 and ignore the update notification. She's had zero issues and I've had this one plus the external SD write crap. I'm definitely the nerd of the two of us and getting into flashing custom roms would be too much for her.
This might end up pushing me to something custom. If I do I'll just leave her behind at 4.3 and kill her update notifications permanently.
Click to expand...
Click to collapse
damn well i meant custom touchwiz and custom ASOP

And now it's deleting system apps. Wtf. My alarm clock and calculator are gone. I sure didn't delete them. Titanium backup list most of the clock stuff as crossed out.

thedumbass said:
And now it's deleting system apps. Wtf. My alarm clock and calculator are gone. I sure didn't delete them. Titanium backup list most of the clock stuff as crossed out.
Click to expand...
Click to collapse
that's strange what rom? and how long have you been using it i will do the research

Still stock ND8 deknoxed. I froze the bloat rather than deleting. I haven't had a chance to flash anything new since starting this thread.
Starting to wonder if my nand is shot... I couldn't find any apps that would do an integrity check on the nand.

Hi
thedumbass said:
Still stock ND8 deknoxed. I froze the bloat rather than deleting. I haven't had a chance to flash anything new since starting this thread.
Starting to wonder if my nand is shot... I couldn't find any apps that would do an integrity check on the nand.
Click to expand...
Click to collapse
Start ultra fresh:
1. Backup anything you absolutely must including from the internal storage.
2. Take the SD card out and leave it out.
3. Download is necessary and check the MD5 hash of the zip or tar of the stock ND8 tar. The hashes are somewhere in that thread, just search it for MD5.
4. Odin the stock ND8 tar.
5. Odin the very latest Philz Touch Recovery tar.md5.
6. In Philz's settings, use the re-root option.
7. Don't restore any data via Titanium Backup or other app. Only restore apps via the Play Store.
8. Observe if all weirdness has gone away.
9. If so, backup what you want from your SD card, reformat it and if you want flash a different ROM. Check the hash of anything you flash, especially ROMs and kernels.
10. Do not restore any Nandroids.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Just as a quick update bump.
I haven't had a chance to sit and do a proper wipe and flash from scratch. After I missed an appointment due to missing alarm clock I dirty flashed the rebooted nd8. This hit my clock calender and calculator back. Then I had to remove knox and bloat again.
My phone has locked the power button and WiFi a few times since. Running towel root seems to fix it though the towel root app freezes and has to be force closed.
I have noticed what seems to trigger it to screw up is letting the battery run dead to the point it auto offs. Just powering it off/rebooting or pulling the battery doesn't cause it though.
Do plan to wipe it clean soon. Between work and home I haven't had time.

thedumbass said:
And now it's deleting system apps. Wtf. My alarm clock and calculator are gone. I sure didn't delete them. Titanium backup list most of the clock stuff as crossed out.
Click to expand...
Click to collapse
I had the same thing happen to me. I *think* it had something to do with my debloating. Correct me if I'm wrong, but it think that many apps use the same processes. Deleting an app might delete processes needed by another app?
When using tibu, I've made it a habit to go slow. Wipe cache before I delete anything. Make a backup of any app I'm going to remove (after deleting data on that app). Only removing a few apps at a time, and making note if which apps I've removed.
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2