Related
I'm sorry but I'm a N00B at this and I can't seem to find a clear and concise answer to this:
If I have a rooted 2.1 stock ROM and want to move to 2.2, how can I safely do so while not losing my settings or apps?
I was going to just do an OTA update and re-root with Unrevoked 3.2 but the OTA install keeps failing - if anyone has thoughts on that I'd love to hear them too!
I don't need or really want anything special other than root - stock rooted is actually preferred!
Help is appreciated!
not a good idea to restore 2.1 data when going to 2.2 bite the bullet and just go for it
OBTW this needs to be in Q&A
Well since you can upgrade from 2.1 to 2.2 using the stock rom updater and keep your data there is a way to do it safely... just trying to figure out if anyone knows how that works.
Titanium Backup for apps and data. MyBackup Pro for home screens. Do not restore any system settings as this will causing conflicts with the 2.2.
Also use AppBrain Market after upgrade to re-sync your apps with the Market so that you can continue to receive updates for your apps.
That being said, in order to upgrade to 2.2, you do a full wipe which means you will lose your apps and data. After you upgrade you can then restore your apps and the data (not settings - remember conflicts!) for those apps. Because the two OS's are so different, a full data wipe is necessary. Use Amon_RA's recovery for best results.
Sent from my PC36100 using XDA App
as stated above there are ways to get the app and app data over pretty smoothly. Doign a lbind systems ettingrestore however is not a good idea.
The way i have done it in the poast and gotten good results os by using titanium back up. restoring all apps+app data. I then go to the batch/restore tab of titanium back up and select things that should not cause any harm such as wireless access points bluetooth pairings and sms back ups. i restore those only. This has created the least amount of problems for me. I tried doing all system settings int he apost and had lot of issues moving from 2.1 to 2.2
Also i know it was said but yuo should always remember to ask questions in the Q&A forum. I am supprised you dont have 4 pages of flames yet so count yourself lucky.
I struggled with that as well. All the sugestions are great but you can take the Sprint OTA upgrade to 2.2 and not lose anything and Keep root if you do it right.
I outlined the proess in this thread. Basiclly u apply the OTA update manually and before u reboot apply the Root patch reboot and when ur phone finishes updating u are on 2.2 and have root, but u lose clockwork and will need to reflash it back But if you choos not to flash it back ur Basicly 99% stock sprint with the 1% being rooted.
http://forum.xda-developers.com/showthread.php?t=748335&page=6
Install Sprints OTA Froyo update. Then use unrevoked 3.2 and you are set.
Sent from my PC36100 using XDA App
freditoj said:
Install Sprints OTA Froyo update. Then use unrevoked 3.2 and you are set.
Click to expand...
Click to collapse
That's exactly what I was trying to do tonight. Stock 2.1-update1 (1.47) that I used unrevoked2 to root (no NAND unlock). The only reason I rooted it was for the wifi teather, for now.... held off going to 2.2 until it was rootable and then tonight I sat down to go through the "2.1 root + NAND + 2.2 pre-rooted flash" process and saw that Unrevoked3 has a 1-click root/NAND/S-OFF. I realize they pulled it, but I'm guessing it's going to be back out pretty quickly.... so I figured I'd just do the OTA and get some froyo love while I wait.
I downloaded the update and it verified and prompted me to install. I hit OK and it boots with a little android guy and a progress bar. About halfway through that, I get this screen:
{
"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"
}
Then it just sits there forever. The only way to get it to respond is to pull the battery and reboot (back into 2.1-update1).
I thought maybe the download was corrupted over the crappy hotel WiFi here, so I cleared my dalvik cache, re-downloaded via 3G, and tried again. Same problem.
Any idea why I can't apply the simple OTA update????
Thanks,
Rich
Make sure you've run unrevoked forever. Flash the stock recovery. Then attempt the ota update. This is assuming youre running a stock rom as well.
Sent from my PC36100 using XDA App
SharkUW said:
Make sure you've run unrevoked forever. Flash the stock recovery. Then attempt the ota update. This is assuming youre running a stock rom as well.
Click to expand...
Click to collapse
I was hoping for a no-data-loss solution.
I have the RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe file, but it's a Windows program to flash. Is it possible to just use the ClockworkMod recovery that's already on the phone to flash it as a PC36IMG.ZIP file instead?
I've got a Mac, so the RUU*.exe doesn't help me much.
with the methods of back up what specific data are you worried about login? most of it can be back up and restored easily. Apps + app data can be backed up and restored. contacts, calanders, wifi pairings, bluetooth pairings, call history, sms/mms history, can all be backed up and restored easily.
from stock you will have to redo your widgets on the screens and log back into google but otherwise there really isnt much that i can think of that cant be backed up and restored that would be vital to not lose.what information can you not back up and restore that you are worried about to go through 5x the work and all this effort searching on. : \
Just use clockwork to apply the Sprint OTA, save the Sprint OTA to SD boot into clockwork and apply zip from SD card. note this will get rid of clock work and if u haven't got s off you will be stuck I recommend flashing unrevoked forever first.
Omegasun18 - I have a nandroid backup but that's it. Titanium doesn't work because I'm not NAND unlocked (yet), just rooted with Unrevoked2.
detcup4evr - Where is the OTA stored in the filesystem when it's downloaded over the air? [edit: i found /cache/OTA_Supersonic_3.26.651.6-1.47.651.1_releasexjg0a0vqdw5cor7z.zip but haven't figured out how to get it to /sdcard; mv doesn't work] I assume I just need to mv it to the root of the SD card and call it PC136IMG.ZIP and reboot in recovery to flash it?
Am I risking bricking my phone doing it that way? The android warning phone scared the bejeezus out of me the first time...
um titanium used to work with just root and not nand unlocked. the original root method had you use the old unrevoked to unlock root and then back up then unlock nand. when did this change? once you can give superuser permissions you should be able too (this is normally possible at root)
since it isnt editing anything in system (except maybe to attempt to back those up which i dont think it will but ... you dont need to it doesnt make sense to me why it would need nand and not just root. Have you tried using Tb or are you just going by what you read somewhere?
it was mentioned earlier, but seems to have gotten lost in the thread.
DO NOT USE TITANIUM BACKUP TO BACKUP/RESTORE DATA WHEN UPGRADING TO 2.2 FROM 2.1.
it will screw up your phone.
actually i have used it on several phones making a blanket statement is not very helpful. YOU CAN RESTORE APPS AND APP DATA USING TITANIUM BACK UP PERFECTLY FINE!YOU JUST DONT WANT TO RESTORE SYSTEM DATA.
you can actually manually restore most system data too just fine if you know what you are doing. things like bluetooth pairings wifi pairings etc can easily be restored no issues you just have to be selective.
the people who have run into problems restoring are the ones that do a plain batch install of all data. this causes issues. i have posted several times methods that work and have been successful for myself and others. it just isn't using one of the batch restores. so making a blanket statement saying you cant use it at all is ignorant and untrue.
I don't know about unrevoked forever since ppl claim that's not a "full" root (I used Toast's method), but when I went from 2.1 to 2.2 rooted roms, I made a full apps+data backup with mybackup pro and didn't have any problems. Was able to restore most of my apps except for a few which is quite easy enough to reinstall instead of the whole setup. If you have root/su, get mybackup pro and you should be able to restore most if not everything. Just don't backup/restore your SU since that conflicts with the SU that usually already comes with custom roms.
omegasun18 said:
actually i have used it on several phones making a blanket statement is not very helpful. YOU CAN RESTORE APPS AND APP DATA USING TITANIUM BACK UP PERFECTLY FINE!YOU JUST DONT WANT TO RESTORE SYSTEM DATA.
you can actually manually restore most system data too just fine if you know what you are doing. things like bluetooth pairings wifi pairings etc can easily be restored no issues you just have to be selective.
the people who have run into problems restoring are the ones that do a plain batch install of all data. this causes issues. i have posted several times methods that work and have been successful for myself and others. it just isn't using one of the batch restores. so making a blanket statement saying you cant use it at all is ignorant and untrue.
Click to expand...
Click to collapse
Thanks for clarifying - it looked to me like folks were saying TB was fine on all counts when going from 2.1 to 2.2, and I wanted to make sure people knew it wasn't quite that simple.
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.
Hello, I am totally new to rooting and etc.
I am trying out the wicked sensations v4.1 for galaxy s 3 and every time I attempt to load up my titainium backup to restore my apps my phone hard resets to the prompt and etc. I don't know whats the cause and I would appreciate every bit of info I could get.
Sometimes it does it on its own just a hard reboot for no particular reason. Any info on this? I wiped my dalvik (sp) cache and did a factory reset before I started the rom. I had it rooted to an earlier model of Blaze. I wanted the multiwindow function but if there is an easy way to get this I am willing to change the rom to something with Premium suite on it. Any info guys? will thank who ever contributes.
also I tried to search for similar. Nothing that i found or the search engine found was really point on. sorry if I offend you old-heads..
love.
M F Money said:
Hello, I am totally new to rooting and etc.
I am trying out the wicked sensations v4.1 for galaxy s 3 and every time I attempt to load up my titainium backup to restore my apps my phone hard resets to the prompt and etc. I don't know whats the cause and I would appreciate every bit of info I could get.
Sometimes it does it on its own just a hard reboot for no particular reason. Any info on this? I wiped my dalvik (sp) cache and did a factory reset before I started the rom. I had it rooted to an earlier model of Blaze. I wanted the multiwindow function but if there is an easy way to get this I am willing to change the rom to something with Premium suite on it. Any info guys? will thank who ever contributes.
also I tried to search for similar. Nothing that i found or the search engine found was really point on. sorry if I offend you old-heads..
love.
Click to expand...
Click to collapse
Does the phone reboot when you restore any app, or only certain ones? I know that some (if not all) system apps shouldn't be restored through titanium backup, as differing versions and mods will affect these differently. Below I have quoted a simple guide I wrote up a while ago to help someone else with TiBu issues. Hopefully it helps you understand TiBu more.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"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"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse
My thought is that restoring system apps/data is what's causing the reboots. Steer clear of those and you should be fine.
Hope this helps!
Thanks!
I have been trying g to get back to you for 20minutes. It just kept restarting without me doing anything. It's a blessing this went thru. But I think something is wrong with this room. The smart rotation and the other things was turned on.
I turned them off and now it doesn't seem to want to restart.
Problem is now that I gotta find a room with the full capabilities That I wanted in this rom, I really wanted to show this off any advice?
Sent from my SPH-L710 using xda app-developers app...
update:
it just reset again i jumped to pc for a second. im getting ready to goto work, i have the app installed i jst hope i didnt wreck my phone any advice is appreciated
Usually when I flash a rom and it just blasts off with random reboots right after i restore apps from TiBa, it's probably a bad download / Custom Kernel being wonky
or you're coming from AOSP JB to TW JB Vise Versa.
I'd suggest re-downloading the rom on PC w/ Lan connection, using the original USB Cable to transfer files from PC to Device.
Underclocking your devices max speed to 1026, or 1242. Usually coming from a different JB Based Rom, AOSP to TW or TW to AOSP, its best NOT to restore
data of apps when you restore from Titanium Backup, App Data from AOSP JB can really conflict with App Data on TW JB whether or not
you've wiped Dalvik Cache, or Cache. At least that was the issue with me when i switched between the two and im talking normal installed apps
and not system apps.
Usually if your coming from DeOdexed to Odexed roms, some apps / system apps FC because of the files being built on one or the other with different type of
data being restored as well.
So something like... SecLauncher2.apk and SecLauncher2.Odex, If you went from TW DeOdexed to TW Odexed, and restored data on the apk, it'll start force
closing.
Most of the times if you are restoring system type apps, Titanium Backup would Hot Reboot, or quick reboot, at least that would happen to me.
Hopefully this info helps the least bit to trying out your ROM.
Has to be something your doing because I know first hand there isn't anything wrong with the wicked rom
Sent from my SPH-L710 using Tapatalk 2
To be my wifi because when I'm up connected to 4G damn right around town there's nothing wrong with my connection in doesn't force close I was just at a buddies house and it just kept going left n right kept force closing they would you still for a whole 10 minutes
Sent from my SPH-L710 using xda app-developers app
Not to bash any developers, but when I tried out Wicked Sensations I experienced an amalgam of bugs. Even after troubleshooting.
Sent from my SPH-L710 using xda app-developers app
Ok I switched to the new phantom blaze. And even it is restarting. I really don't know whats going on. Is there a way I can go back to straoght up sprint stock and start the whole process over? Its just becoming a headache with the constant restarts and ****.
Sent from my SPH-L710 using xda app-developers app
There is a rooted version of sprint stock rom in the android development section. Are you clearing cache/factory reset between flashes? I've flashed both those roms recently and have had no issues.
Sent from my SPH-L710 using xda app-developers app
Yeah man I do all three matter fact I'm tired of losing numbers because I'm doing the factory reset / flash and the Dalvik cache wipe. I don't understand. Is my clockwork dated?
Sent from my SPH-L710 using xda app-developers app
Good chance of it, I've used twrp since I started flashing roms. The touch interface is nice and I haven't had any issues with it. If yiu haven't tried that recovery yet that's the next step I would take.
Sent from my SPH-L710 using xda app-developers app
Look for SXTapes thread on the full AIO stock ROM ODIN-OCs.
Use the Rooted DeOdexed MD4 that resets user data. After
you've completed Odin flashing let the device auto reboot and let it
sit and optimize for 10 minutes. Power off and
pull the battery and wait 15 seconds. Put the battery back in and
turn on your device, look for an application made by chain fire called Mobile
Odin lite v3.65 on xda forums. Download and install on device and accept
root permissions. Accept extra download package content.
Now look for TWRP 2.5.0.0 tar file and download it to the root
of your internal sdcard ( preferred to find it easier )
Open up your recents s app list ( Hold home button )
Select Mobile Odin Lite. Scroll down and select Open file
then select internal SD Card. Select the twrp tar file.
Scroll down and select Flash Firmware. It should auto boot you
into Custom Recovery. If not power off device and hold volup+home+power.
Once that is all done. Nandroid ( Backup ) your stock ROM. It'll take awhile
so be patient.
Reboot device.
Transfer Wicked sensation to device.
Reboot to recovery.
Once done go to wipe > advanced wipe
Check mark the following
- Dalvik cache
- System ( Data is also wiped )
- Cache
Do this 2x times to make sure those parts are fully cleared and wiped.
Then install Wicked and have it boot up all the way. Have it sit
for 10 mins to optimize. Then reboot.
Run it like you would any other day. If it reboots on its own then reboot
to recovery wiped dalvik twice. Reboot.
If it keeps rebooting on its own again, reboot to recovery.
Restore stock nandroid.
If it keeps on rebooting when your on stock ROM then your
phone probably has an issue with flashing ROMs / being rooted.
Or just plain bad luck defective.
Sounds doable I'm gonna try this when I'm off..not having my gps on delivery
Is a pain
Sent from my SPH-L710 using xda app-developers app
Spark91 said:
Once done go to wipe > advanced wipe
Check mark the following
- Dalvik cache
- System ( Data is also wiped )
- Cache
Click to expand...
Click to collapse
Correction: Data is NOT wiped when you wipe system. You need to wipe it separately.
So @M F Money, you need to wipe system, data (dalvik is part of data partition) and cache for it to be a FULL, CLEAN wipe.
Ops thank you for that CN.
What I meant was dalvik, system, data, cache. OR factory reset ( data also wiped )
Cache, dalvik ( CWMR ). I was typing on phone at 650 am, I was tired ._.
After doing multiple data, cache, and system wipes. I can successfully say my GS3 is holding the wicked sensations v.4 awesomely. It works...thanks to all people posted in this thread. You all helped me whether I had to research terms you used and etc. Thanks for helping me learn more.
Sent from my SPH-L710 using xda premium
M F Money said:
After doing multiple data, cache, and system wipes. I can successfully say my GS3 is holding the wicked sensations v.4 awesomely. It works...thanks to all people posted in this thread. You all helped me whether I had to research terms you used and etc. Thanks for helping me learn more.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
The restarts are back...It happens when I am at home most frequently yesterday I was out on the town for about 10 good hours and not a single hard random reset. As soon a I got close to my Wi-Fi (even though I turned it off and was running 4g) it hard resets like crazy. I mean it loads..then instantly hard resets before i can even swipe my screen to open my menu. This is really annoying. and I have no Idea why it is doing this.
some of the steps Above are a little to advanced. to the point where I created another thread asking how to update CWRM 6.0.1.2 because some one said that that could be an issue. This is a step that I don't know how to do. Again any help is greatly appreciated. Like this S.O.B will charge all night and as soon as i get ready to do something to the phone it Hard Resets. none of this makes sense and it makes me want to rage on my phone lol
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.
Ok I recently manually checked for update on my rooted S4 and for my surprise it said and diwnloaded a 4.4.4 SO update, but I cant seem to find where was this file downloaded to.
1.- Does anyone knows wherr was this file downaloded to?
2.- the OS downloaded warns of a Knox 2.0 that may disable some of my apps or something like that.
Can someone help? Is there a stock rom that I can download thatbis already rooted and stable?
Also does anyone knows of a good custom recovery, I currently have twrp and I hate it cause everytime that I erase or restore the phone, everything remains in the phone exept user info but folders prevoiusly created remains there. So basically the phone doesnt factory restore. :'(
{
"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
1) It's better to just download the stock NH7 from general section and flash with Odin.
2) Yes there are ROMs like that
And for your last question, factory resets are supposed to do that. They wipe the user data except the internal SD.. There is an option to wipe the internal SD in twrp and in any other recovery
I'm torn between updating to NH7 from the MDL bootloader or keeping it like it is until the Note Edge comes out and jumping to it. Don't know what I want to do but I will say I feel performance wise being on the MDL bootloader I feel I'm sacrificing speeds, abs oddball problems associated with not upgrading.
Sent from my SGH-M919 using Tapatalk
mrbmg said:
I'm torn between updating to NH7 from the MDL bootloader or keeping it like it is until the Note Edge comes out and jumping to it. Don't know what I want to do but I will say I feel performance wise being on the MDL bootloader I feel I'm sacrificing speeds, abs oddball problems associated with not upgrading.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Having the MDL bootloader, someone might find it more valuable if you decide to sell it. Because it is KNOX free You never know. But if you plan to keep it and just want to get rid of it, updating would be better.
serio22 said:
1) It's better to just download the stock NH7 from general section and flash with Odin.
2) Yes there are ROMs like that
And for your last question, factory resets are supposed to do that. They wipe the user data except the internal SD.. There is an option to wipe the internal SD in twrp and in any other recovery
Click to expand...
Click to collapse
Actualy no, when I had my sensation with CWM I remember factory resetting the phone through the regular phone reset setting and it used to boot into recovery and do it by itself. And also deleted all user data, and all previously created data and folders.
So, going from this can you tell me where or under what settings in the recovery is the option to erase the internal sd card, cause I remember the last time a did choose something like that the phone didnt pass the boot logo and I had to reinstall, re-root and everything again, redo everything again and thats time consumming.
Thanks for your response bro.
Sent from my SGH-M919 using Tapatalk
So does anyone knows where is this file downloaded ti si I can extract it from the device and save it
Sent from my SGH-M919 using Tapatalk
dr69 said:
Actualy no, when I had my sensation with CWM I remember factory resetting the phone through the regular phone reset setting and it used to boot into recovery and do it by itself. And also deleted all user data, and all previously created data and folders.
So, going from this can you tell me where or under what settings in the recovery is the option to erase the internal sd card, cause I remember the last time a did choose something like that the phone didnt pass the boot logo and I had to reinstall, re-root and everything again, redo everything again and thats time consumming.
Thanks for your response bro.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
So it wiped your external SD? Because sensation does not have internal SD.. To wipe the internal SD go to wipe, and I think its in advanced wipe
Soooo, can anyone help here?
Sent from my SGH-M919 using Tapatalk
dr69 said:
Soooo, can anyone help here?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Download it, root your device, use a file explorer with root permissions, do a search for update.zip
Its either in /cache/ or /data/ I honestly cant remember. Do post a link if you do it tho.
Yep, thanks it was right there. Now I have the OTA for T-Mo US official 4.4.4.
Im gonna save it just in case
Sent from my SGH-M919 using Tapatalk
Just wanted to throw my advice in on this. I've had my phone rooted since the day I got it in August of '13. Had the MDL bootloader, never updated it, but always updated the modem's to the current modem.
I noticed something weird on this last update to NH7 though. Something was just different. My LTE speeds definitely slowed down to a crawl, and my phone was rebooting on a stable rom that I've ran for over 6 monthes, GoldenEye. Battery drains have been plaguing me this last month as well. I tried different kernels, fresh installs, nothing was working. Finally got to the point of, screw it, I'm updating the firmware and will go from there.
Yesterday I upgraded firmware without completely wiping the rom that I was on. Odin'd NH7 and everything loaded back up the way it was, and Yes I now have the Knox bootloader. Immediately I noticed my LTE speeds had returned back to normal. I haven't had one reboot in the last 17.5 hours, and I'm at 75% battery left. I definitely think being on such an old bootloader impacted the way my phone was acting. Could just be me, but it helped me ten fold, from the problems I was having, to what I have now. I'm debating on just leaving it stock so I don't screw knox, just in case I want "JUMP" to the Note Edge whenever it comes out.
Again, this is just my case. I'm sure in a couple of days without customizing stupid crap or loading a few different roms to try out, I'll go ahead and root it and void the knox (I don't really care about it anyhow.) If the damn Note Edge was here I would have already pre-ordered and wouldn't have to worry. Since it's not, I might just pay this phone off and keep it and start up a new line for the Edge. Our phones are kick ass and almost impossible to brick, and very fast for what all I do on it.
Thanks,
BillY
Just root the phone, otherwise what is the point of having android ;-P
check out this rom if you want TW 4.4.4 with some modifications:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-4-4-4-nh7-insane-kit-kat-v1-9-14-14-t2876946
there is another that it is just stock rooted 4.4.4, no mods, just plain stock here:
http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-base-4-4-4-nh7-rooted-deodexed-t2873695
:laugh:
---------- Post added at 01:02 AM ---------- Previous post was at 12:49 AM ----------
mrbmg said:
Just wanted to throw my advice in on this. I've had my phone rooted since the day I got it in August of '13. Had the MDL bootloader, never updated it, but always updated the modem's to the current modem.
I noticed something weird on this last update to NH7 though. Something was just different. My LTE speeds definitely slowed down to a crawl, and my phone was rebooting on a stable rom that I've ran for over 6 monthes, GoldenEye. Battery drains have been plaguing me this last month as well. I tried different kernels, fresh installs, nothing was working. Finally got to the point of, screw it, I'm updating the firmware and will go from there.
Yesterday I upgraded firmware without completely wiping the rom that I was on. Odin'd NH7 and everything loaded back up the way it was, and Yes I now have the Knox bootloader. Immediately I noticed my LTE speeds had returned back to normal. I haven't had one reboot in the last 17.5 hours, and I'm at 75% battery left. I definitely think being on such an old bootloader impacted the way my phone was acting. Could just be me, but it helped me ten fold, from the problems I was having, to what I have now. I'm debating on just leaving it stock so I don't screw knox, just in case I want "JUMP" to the Note Edge whenever it comes out.
Again, this is just my case. I'm sure in a couple of days without customizing stupid crap or loading a few different roms to try out, I'll go ahead and root it and void the knox (I don't really care about it anyhow.) If the damn Note Edge was here I would have already pre-ordered and wouldn't have to worry. Since it's not, I might just pay this phone off and keep it and start up a new line for the Edge. Our phones are kick ass and almost impossible to brick, and very fast for what all I do on it.
Thanks,
BillY
Click to expand...
Click to collapse
what i did since the latest NH7 came out was update through ODIN, never had a problem with it, so i guess i got lucky
Lasted a whole 2 days stock and un-rooted after I updated to NH7.
I only owe another $200 on my phone so there is really no sense in "Jump" at this point. The Edge not being out made this decision real easy for me. Just going to keep the S4, and pay it off and start over again once the Edge comes out.