Related
hi, i recently got an ATT note 2. The phone I got already got Clean ROM 3.5, so I presume it is rooted, with custom recovery (TWRP when I checked). I am thinking of flashing to a diff rom and just want to ask a few questions.
1-do I need to run triangle away every time I flash to a diff rom?
2-since the phone already has a custom rom, I should not have to root it, am I correct?
3-If I want to install custom, ROMs, can I just put the ROM in the external SD and flash it that way (of course with clear cash, davik, etc as states in the rom).
4-I am thinking of playing with the CleanROM 4.2.4 or the ACE version? any issue with either one compare to the 3.5 that I am using now? any recommendation?
5-anything I need ot watch out before I flash it? I have flashed a coupole of time with htc phone and this is my first samsung phone so I don't watn to brick it.
thanks a lot guys, XDA rocks.
PUTALE said:
hi, i recently got an ATT note 2. The phone I got already got Clean ROM 3.5, so I presume it is rooted, with custom recovery (TWRP when I checked). I am thinking of flashing to a diff rom and just want to ask a few questions.
1-do I need to run triangle away every time I flash to a diff rom?
2-since the phone already has a custom rom, I should not have to root it, am I correct?
3-If I want to install custom, ROMs, can I just put the ROM in the external SD and flash it that way (of course with clear cash, davik, etc as states in the rom).
4-I am thinking of playing with the CleanROM 4.2.4 or the ACE version? any issue with either one compare to the 3.5 that I am using now? any recommendation?
5-anything I need ot watch out before I flash it? I have flashed a coupole of time with htc phone and this is my first samsung phone so I don't watn to brick it.
thanks a lot guys, XDA rocks.
Click to expand...
Click to collapse
1. No you do not need to run triangle away usually only have to run it if you are going back to stock and may want to return the phone.
2.Nope it has a Rom you are rooted !
3.That is what I do when installing a new rom factory reset wipe davlik and cache and install you may have to fix permissions with some installs as well after installing.
4.From the bit I played with the new Clean rom it is very stable with minimum if any grief Jedi 9 is also a awesome ROM and my current fave.
5.Just read up lots before you do it follow every step they tell you to take your time it is easy just make sure ya know what you are doing before you start.
6.Enjoy they are a awesome phone !!
Thanks a lot for your prompt reply. It heped a lot. I will definitelycheck the roms. I am using 3.5 and it runs really good and hate to ruin it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
PUTALE said:
Thanks a lot for your prompt reply. It heped a lot. I will definitelycheck the roms. I am using 3.5 and it runs really good and hate to ruin it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
do a backup in twrp before flashing a new one, you can always come back
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
PUTALE said:
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
Click to expand...
Click to collapse
This is one of nice features of TWRP... ability to backup/restore individual partitions. Android stores various blocks in different partitions. To name a few, System, Data, Modem, Recovery, Boot, Cache, etc. If you just want to backup your modem for example, just check the "modem" box (and I recommend naming the folder to something significant so down the road you'll know which modem it is). When you restore, that folder will only have your modem.. so you can restore a different modem without having to change your rom, (etc). Kernels are stored in the "boot" partitions.. again, if you want to change kernels, backup the boot partition and name it properly if case you want to reflash that kernel. Generally, after my first flash of a new ROM, kernel, modem, I'll create a "boot" backup, "modem" backup, and ROM (system/data/boot) partition backups. If you look in the TWRP folders themselves, you can see the blocks which are backed up... or will be restored. Hope that helps.
PUTALE said:
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
Click to expand...
Click to collapse
When I back up in TWRP, I usually just go with what is default checked off. You will not mess up your root unless you really really tried to. The last time I ever had to flash back to stock then to a custom was on my Xperia X10a... You should be fine flashing a new rom without having to go back to stock as long as you do a good wipe (Wipe System, Factory Rest, Davlik, and Cache is what I do only because it doesn't hurt... I've read you do not need to do all those steps but I do them nonetheless). Do not use Triangle Away unless you plan on returning your phone or send it in for warranty. Only then should you start asking questions about that tool.
The only issue that may cause SOME confusion (not too much but some) is flashing back and forth between a 4.1.2 and a 4.2.1 since the SD card adjusts to User settings (some folders open up for individual users on 4.2 but as far as my experience goes, I have not had any issues with it, I just needed to study my SD card after each flash).
So you should be fine... just do backups, rename them to make sure you know which rom belongs to which backup, delete the old ones from the RESTORE menu in TWRP in case you are backing up the same rom to save you some space (my backups take around 2 gigs sometimes EACH) and you should be good to go... Enjoy tweaking out on your roms!
DoctorQMM said:
This is one of nice features of TWRP... ability to backup/restore individual partitions. Android stores various blocks in different partitions. To name a few, System, Data, Modem, Recovery, Boot, Cache, etc. If you just want to backup your modem for example, just check the "modem" box (and I recommend naming the folder to something significant so down the road you'll know which modem it is). When you restore, that folder will only have your modem.. so you can restore a different modem without having to change your rom, (etc). Kernels are stored in the "boot" partitions.. again, if you want to change kernels, backup the boot partition and name it properly if case you want to reflash that kernel. Generally, after my first flash of a new ROM, kernel, modem, I'll create a "boot" backup, "modem" backup, and ROM (system/data/boot) partition backups. If you look in the TWRP folders themselves, you can see the blocks which are backed up... or will be restored. Hope that helps.
Click to expand...
Click to collapse
Much appreciated for your detail explanation on the TWRP. I did a quick backup and selected all of the option and now I see the files in my external SD:
modem.emmc.win
data.ext4.win
cache.ext4.win
recovery.emmc.win
boot.emmc.win
efs.ext4.win
data.ext4.win
system.ext4.win
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
[email protected] said:
When I back up in TWRP, I usually just go with what is default checked off. You will not mess up your root unless you really really tried to. The last time I ever had to flash back to stock then to a custom was on my Xperia X10a... You should be fine flashing a new rom without having to go back to stock as long as you do a good wipe (Wipe System, Factory Rest, Davlik, and Cache is what I do only because it doesn't hurt... I've read you do not need to do all those steps but I do them nonetheless). Do not use Triangle Away unless you plan on returning your phone or send it in for warranty. Only then should you start asking questions about that tool.
The only issue that may cause SOME confusion (not too much but some) is flashing back and forth between a 4.1.2 and a 4.2.1 since the SD card adjusts to User settings (some folders open up for individual users on 4.2 but as far as my experience goes, I have not had any issues with it, I just needed to study my SD card after each flash).
So you should be fine... just do backups, rename them to make sure you know which rom belongs to which backup, delete the old ones from the RESTORE menu in TWRP in case you are backing up the same rom to save you some space (my backups take around 2 gigs sometimes EACH) and you should be good to go... Enjoy tweaking out on your roms!
Click to expand...
Click to collapse
thanks for the info/warning on the triangle. I read that it can brick the phone and also needs to be on the stock to use it. Also read that if there's too many counts, it may not work. I guess for now, I just won't touch it.
Since there's no 4.2 roms available (at least not what I have seen and want to play, CleanRom or Jedi as they are highly rated), I guess for now I do not have to worry much on the SD card issue. It will be safer I guess for now just stick with 4.1.2 until the kinks are worked out.
For the wipe system, factory, davlik, cache, do I do that before flashing it?watched a couple of video and instruction and they all have diff answers. Some people said do factory reset, flash, and then wipe davik and cache.
Again, really really appreciate all of the support guys.
PUTALE said:
Much appreciated for your detail explanation on the TWRP. I did a quick backup and selected all of the option and now I see the files in my external SD:
modem.emmc.win
data.ext4.win
cache.ext4.win
recovery.emmc.win
boot.emmc.win
efs.ext4.win
data.ext4.win
system.ext4.win
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
thanks for the info/warning on the triangle. I read that it can brick the phone and also needs to be on the stock to use it. Also read that if there's too many counts, it may not work. I guess for now, I just won't touch it.
Since there's no 4.2 roms available (at least not what I have seen and want to play, CleanRom or Jedi as they are highly rated), I guess for now I do not have to worry much on the SD card issue. It will be safer I guess for now just stick with 4.1.2 until the kinks are worked out.
For the wipe system, factory, davlik, cache, do I do that before flashing it?watched a couple of video and instruction and they all have diff answers. Some people said do factory reset, flash, and then wipe davik and cache.
Again, really really appreciate all of the support guys.
Click to expand...
Click to collapse
Think of your Nandroid (TWRP) backup as a roll back to what you are comfortable with (check everything off so you do not lose a thing if you want) in case you find that the new thing you flashed isn't all that it was cracked up to be for you or something messes up. The Nandroid backup is EVERYONE's friend.
As for flashing a new ROM and having to start all over, I will use this as an example: I have two backups; one for Paranoid Android (4.2.1 AOSPA) and Clean 4.2.5 (4.1.2). When I originally flashed my stock to Clean, I must've gotten lucky by just wiping the system (ROM only and not a factory reset) and all my data transferred over just fine with no issues... but when flashing to PA, I had to do a full wipe then start from scratch (which was not bad if you sync your apps and contacts thru Google). Also, you might want to get another backup system such as Super Backup to back up your contacts and SMS messages (be careful with backing up call logs if you go to 4.2.1 ROMs because for some reason, things went wacky for me). Titanium is a good system to use for power users but sometimes, to keep it as simple as possible, count on Google at first for your app syncing (and if you get Amazon App Store, you will have to get that APK to download the apps from that store).
Anyway, from there (if you want to play with multiple ROMs) you now have a foundation. Dirty flashing (flashing a new version of a ROM you currently have without doing a full wipe... just in case you didn't know... for me, I just wipe System [no factory reset] then flash the upgrade) should be fine... again, I'm typing from experience because there are some people who do run into issues dirty flashing and is usually not supported by the devs unless you do a full wipe and flash. I have not had any issues whatsoever dirty flashing both PA and Clean versions.
As for methods of wiping, honestly they're all right... I just posted what I usually do when I want to do a full wipe. Only if you want to do a dirty flash, you won't have to wipe or do a partial wipe (I partial wipe e.g. Clean 4.0.5 to 4.2.5: Delete last Clean Rom backup through the Restore menu, Nandroid Back Up current working Clean Rom 4.0.5, Wipe System, Install the new 4.2.5, wipe Davlik and Cache (again, I do this just in case but some devs say it's unnecessary), then reboot and wait for the apps to reset... all was where it was when I left 4.0.5.
PUTALE said:
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
Click to expand...
Click to collapse
Yes... if you're retaining your current modem and recovery... to restore a rom just as it was when you backed it up, restore boot (which has the kernel), system and data. One your second question, when restoring a different rom , it's best to always restore system/data/boot together. You can use TiBu to restore your user app DATA, and individual apps usually have their own backup files you can restore (like Nova/Apex launchers [which can restore your widgets], calendar, etc).
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
PUTALE said:
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
Click to expand...
Click to collapse
I have never used that rom so I can't say for sure. Try it out and see what happens. If you don't like it, restore your backup.
PUTALE said:
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
Click to expand...
Click to collapse
That rom is one of the most recent 7105 (note2 international) samsung firmware releases... supposedly better battery life than LL7 or LL4. It's the stock MA6 pre rooted (i.e., has SuperSU app and binaries included). No other features added like you would find with CleanROM 4.2.5 for example. It includes rom and kernel... so it will write to your system, data, and boot partitions. Whatever custom recovery you have now and flash this with will not be touched.
thanks again.
Hi i want to apply the OTA (MD4) and keep my root acces, so my question is, if is possible to use voodoo root keeper app to apply this update. thanks in advance
juancaperez2000 said:
Hi i want to apply the OTA (MD4) and keep my root acces, so my question is, if is possible to use voodoo root keeper app to apply this update. thanks in advance
Click to expand...
Click to collapse
Hey Juan,
I'm assuming you just got the notification for the OTA. You actually don't have to apply it to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
topherk said:
Hey Juan,
I'm assuming you just got the notification for the OTA. You actually don't have to apply it to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Click to expand...
Click to collapse
thanks!!! i tought that i need do like qbking77 did on his videos using oding for i can keep my data but you'r right dirty flash can work too (stock to stock)
juancaperez2000 said:
thanks!!! i tought that i need do like qbking77 did on his videos using oding for i can keep my data but you'r right dirty flash can work too (stock to stock)
Click to expand...
Click to collapse
That's right, dirty flashing should work fine. If you're noticing any major issues (FCs, reboots, etc), you might want to use Titanium Backup to back up your important stuff and do a clean flash. But hopefully the dirty flash will be good.
I saw this post earlier, and was going to reply pretty much the same thing. Then I said to myself nope im going to leave it alone Topherk will come by soon enough with a way better reply and exact instructions!! :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Keep up the great work
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
I saw this post earlier, and was going to reply pretty much the same thing. Then I said to myself nope im going to leave it alone Topherk will come by soon enough with a way better reply and exact instructions!! :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Keep up the great work
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks Ed, I appreciate the feedback.
Thankfully, I put the hard work in a while ago, so now (for most questions) all I have to do is paste that one post and I'm good to go.
As an aside: yesterday I helped a friend root his GS3 and realized I'm much better at explaining things here on XDA than I am in real life. I kept jumping ahead of myself and trying to explain about wiping /system before I even explained what a custom Recovery is. I should've just asked him to post a question "how do I root" and I could've done a better job explaining it, haha.
Ok I wrote this for the OP of my ROM because the issues some people were PMing me about were just plain out dumb, This phone has been out quite a long time and still almost every thread I goto, you got people flashing in way's I didn't even know were possible and posting weird issues that were not being reproduced by the community. so I'm just gonna post this guide for all the developers sake and in hopes the people that actually need this information, receive it before posting and clogging up development threads
If you're having issues on rom's that no one else is reporting, or the DEV has not reproduced on his phone, read the following.
1) Full wipe
2) Do not restore System data or data from CWM
3) Do not dirty flash from other ROM's
4) When was the last time you did a odin to stock? this is important in my opinion and I'm not saying you need to do one but I just want to explain that custom zip's that I make and other dev's make in the shape of "roms" only affect
a few partitions on your device, other's do not get touched and can get messy/corrupt over the months (This explains why the GPS icon disappears in some peoples cases during rom switch) and this is why I get posts in this thread about people wondering why their baseband hasn't been updated after flashing my rom when my post states "MF1"
With this being said my personal rule of thumb is to odin to stock latest and then boot into stock recovery and factory reset, wipe cache/dalvik (BACKUP YOUR SD CARD TO YOUR COMPUTER), this gives your phone fresh partitions everywhere, a fresh system to root and the latest bootloader (which you need for any AOSP 4.2 rom). This is also a good time to unlock your phone if you have not already, then reroot and install custom recovery, update the recovery if need be and flash again on a brand new system. here are my steps
1) backup all user apps and data with titanium backup, DO NOT BACKUP SYSTEM APP'S
2) backup internal storage onto PC
3) Odin to stock latest
4) wait for phone to boot then reboot into stock recovery and full wipe and clear all cache
5) reboot and root the phone and custom recovery
6) flash away and put what you need on your internal storage back onto your phone via usb, see my 2nd set of instructions below
this fixes more issues then you will realize. some of the way people flash rom's on XDA and complain to me with problems is rather funny considering I have the install instructions in the OP, not to mention many of you rooted your phone when you first got it in the ICS 4.0.4 day's and haven't done an odin to stock jellybean to update all your partitions including your bootloader, now I will go over my every day flashing step's.
1)backup all USER APPS/DATA with titanium backup, DO NOT BACKUP SYSTEM APP'S (skip this if you did a odin flash to stock)
2)reboot recovery
3)nandroid (skip this if you did a odin flash to stock)
4)factory reset, wipe system, wipe both cache/dalvik
5)install rom
6)boot system
7)*(OPTIONAL) reboot to install a kernel now if needed, always wipe cache/dalvik and fix permissions after installing a kernel
8)setup phone and download titanium backup from the market
9)restore all user apps and data (you will have to put the titanium backup folder that is backed up on your computer back onto your internal storage via usb first)
Every 6 months, backup internal storage to PC and I odin to stock, much like formatting a computer
6 months is actually a long time considering how much I flash, but this device can take a beating let me tell you =P
I DO THIS WITH EVERY ROM I INSTALL, AOSP or TW
Great info, that is actually my same process when I have an issue with anything
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
KorGuy123 said:
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
thanks man, hoping this gets a sticky.
Danvdh said:
thanks man, hoping this gets a sticky.
Click to expand...
Click to collapse
I'll add it to my sticky
Galaxy S3 / AoCP / V4A / Turbocharged
s3 unrooting issues
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Custom ROM data issue
dannyteo14 said:
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Click to expand...
Click to collapse
So scrap the unrooting issue i have that figured out now, i just reinstalled the rom and again it doesnt have data, it is the deadly venom rom, anyone else that i know who is using this rom has absolutely no problem. I have tried a few fixes i have found via youtube, google, etc.... but none were successful. If anyone knows a fix or has any ideas please let me know.
I have an I747M S3 from a friend and trying to get it back to stable stock. It had lost it's IMEI and some NVdata corruption but I was able to resolve that searching the forums, But it has issues with apps crashing and rebooting quiet frequently. It can sometimes go feeling pretty stable ofr awhile then just kind of blows up. I have cleared away the flash counter and restored factory stock images from Odin and Keis, still having the issues. Is there a partion or something that could be getting missed? Or possible further problems related to the NVdata issues?
if you have any ideas I would appreciate it.
I used twrp to back up system, data, and boot, should I still use titanium back up to back up anything else, or is that enough to be relatively safe?
I was happy as a lark with TWRP. But 4.3 happened and it is a new process. There are variations, here is one way to get your phone and 4.3 to play nice together. I'm on Sprint Galaxy Note 2 and if you are coming to a 4.3 or 4.4 for the first time, or having trouble. Try this first! I give credits Below, but it's for all ROM's. "Google process stopped" is a common sign that this wasn't done. Or if it just hangs on the samsung screen... Btw it does seem like an eternity sometimes. Lol
General theory: skip to the next paragraph if you dont care. I've Googled and read. You should too. We are trying to clean and prepare your phone for 4.3. "Wipe" is not the same as "format. " We need to remove all the little pieces of data that may still be there from before. We need to start fresh. Also, the partitions sizes are different in 4.3. In general we need to clean.
PROCESS A is this link. Billard412 This is back to stock, completely cleaning your phone. It requires odin and a computer. If you want to try procees B alone, you can skip A and just do "process B" and see if that works. If you still have trouble, you know you need to do the full thing. Just a note, you might think it works, but then your nandroids don't restore.. Time for process A. Back to stock. It's good to do this once in a while to start fresh, also.
http://forum.xda-developers.com/showthread.php?t=2086769
Then install USE PHILZ recovery 6.07.9 (link below)
-Install philz. Some people have luck with TWRP , i didn't. I don't think TWRP works with 4.3
There is a newer Philz version, not sure all the bugs are worked out, use 6.07.9
One thing that might be confusing, the process A restore from billard recommends TWRP and I'm recommending Philz recovery. So best advice, although possibly confusing, is install TWRP, billard restore, then flash Philz. It's not any more work really. The back to stock will put you in a stock recovery. So you have to flash something. I was a TWRP fan too, but Philz has had less problems in 4.3.
1. You can follow billard 's instructions
2.there is a YouTube if you want to follow that in billards thread
or3 . Jlmancuso provided this to try and simplify the process:
a. Boot into download/bootloader mode.
b. Connect to pc and use odin to flash TWRP. Make sure you uncheck reboot and flash twrp in the pda slot.
c. Once flashed pull battery and disconnect from pc.
d. Press vol+ menu power buttons while inserting battery (yes it is difficult but can be done)
e. Now in recovery perform factory reset.
f. Flash this http://forum.xda-developers.com/showthread.php?p=36388145
g. Now reboot it will act/look weird but dont worry this is normal. It will reboot and take a long time to boot.
Now you are on stock mc2 (no knox anymore). Root using cf autoroot http://forum.xda-developers.com/showthread.php?p=33278464
Now use odin once again and flash your recovery again, this time Philz. Now you are rooted and have a custom recovery. Oh and you have a working phone again.
PROCESS B.
This is done before any ROM install and before any nandroid restore.
Preparation: BACK UP INTERNAL IF DESIRED, I WILL RECOMMEND WIPING IT in the next steps . NOT REQUIRED, BUT RECOMMENDED. You can move it to external, external doesn't need to be wiped.
In PHILZ recovery 6.07.9 (link below)
1. Mounts and Storage
Format / systemFormat / casheFormat / data Recommended optional. Format internal SD card
Format / data and /data /media (/sdcard) ALL INTERNEL SD CARD DATA IS LOST.PREVIOUS IS NOT EXTERNAL, EXTERNAL IS "SDCARD1" which i would not recommend
2. Power Options > reboot recovery
3. Wipe cashe partition
4. Advanced > Wipe dalvik cashe
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
I would stick with 4.3 and Philz backed up things. Don't restore something from before. Neither a 4.2 rom or a TWRP backup. Once you know you have got this process down, then try / do those sorts of things. Philz is supposed to be able to do that, but let's keep it simple until you have this figured out.
If you want to try process B first only , it may be all you need. But if it doesn't work, do all of it.
I hope this helps - LINKS & CREDITS in next post
4.3 general wiping and preparatory instructions
LINKS
same as above Billard412 back to stock - http://forum.xda-developers.com/showthread.php?t=2086769
alternate back to stock - Rwilco http://forum.xda-developers.com/showthread.php?t=2591898
Philz Recovery Thread - http://forum.xda-developers.com/showthread.php?t=2552653
On the Philz recovery site the "L900" looks more like "l900" and is confusing - so here is a more direct link - select 6.07.9 http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900
TWRP http://teamw.in/project/twrp2/117
To get root- one option is CF Autoroot-
[SPH-L900] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1956180
WIFI FIX just in case. Flash in the PDA tab of Odin http://d-h.st/6qX
If you want to change modems i use this (not required / optional) - http://forum.xda-developers.com/showthread.php?t=2537713
General
I am not trying to take credit for anything. Notice how none of this is my work. Just hoping to pull together and clarify this process. Others my post different ways, and you can try other ways, but if it doesn't work, use this process exactly. It works for many. If you want to post that you tried another way and it didnt work, you are welcome to, but then my reply will be to try it this way...or i wont reply. I just had to keep typing this over and over to many, and i figured I would put out a detailed version. This works. (you know the drill, its your phone, not my responsibilty, of course)
CREDITS AND ROMS
I picked up a lot of this process from Lorjay589's thread. His OP pointed me at the Billard412 back to factory
jlmancuso has posted refined and explained this process 100 times as well.
this is for SMOOTHEST ROM, CUSTOM ROM, SYNERGY ROM, DIGIBLUR ROM, FTW ANNIHILATION, ROM AND MANY OTHERS.
therfore jlmancuso, chaz187, ianmb, digiblur, lorjay589, rwilco12, phil3759, fryingpan0613, jimmydene84, cbucz24, wwjoshdew, agent soap AND MANY OTHERS.
constructive criticism is always welcome i have a tough skin, just be nice and don't hold back to let me know. i am not that knowledgeable, this is my first thread. Just been following some 4.3 threads for a while and saw a recurring problem.
Very nice guide Cole
Sent from my SPH-L900 using Tapatalk
Reserved
Darn it I want a reservation too!!
Thanks now I have a thread to link to instead of a single post.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Very nice tutorial. U nail all that we need to do for a smooth install
Thanks
SGNote2
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
justppc said:
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
Click to expand...
Click to collapse
Some people have just had some problems when using the new version, therefore the previous version is more reliable. Better chance of everything working. Once you have your phone running smoothly using this process, you are welcome to try it. If you have problems... Revert back.
Start with post 87 of the Philz thread, if you like.
http://forum.xda-developers.com/showthread.php?t=2552653
Thanks, this resolved an issue with 'Inconsistent System UIDs"
KNOX with options A/B
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Dedline said:
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Click to expand...
Click to collapse
Process A completely wipes your phone and resets it to stock. B is just general wiping process when flashing a new rom. You shouldn't have a Rom on your phone when you are done with either. (other than the one backed on you external sd)
Head on over the the Ballard thread to read more about process A
justppc said:
Thanks, this resolved an issue with 'Inconsistent System UIDs"
Click to expand...
Click to collapse
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
mr.pope said:
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
Click to expand...
Click to collapse
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
justppc said:
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
Click to expand...
Click to collapse
alas, I have tried that as well. I finally made some headway and think I have it. I had to fix permisions for all apps using Rom Toolbox Lite Looks like that has fixed it. Flashing forward as I type.
Just a bump to keep this where everyone can see it.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Gotta try this on my note 2
K
Sent from my SPH-L710 using xda app-developers app
Just a reminder
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Lyvewire said:
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Click to expand...
Click to collapse
Philz is the only way to go when choosing a recovery. Twrp will not backup or restore mk4 properly and wont woek correct with 4.4 aosp either. When ypu do your first backup choose custom backup and backup everything but Efs. When that is done go back into custom backup and only backup efs (it must be done by itself). I would then suggest copying both backups to a pc or cloud storage for safe keeping.
Sent from my SPH-L900 using XDA Premium 4 mobile app
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
aeneas1 said:
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
Click to expand...
Click to collapse
If it boots at all you didn't kill it.
Not sure what rom you got from the CWM site. They do recoveries, not roms. The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Skipjacks said:
f it boots at all you didn't kill it.
Click to expand...
Click to collapse
hallelujah!
Skipjacks said:
Not sure what rom you got from the CWM site. They do recoveries, not roms.
Click to expand...
Click to collapse
my apologies, i meant that i downloaded recovery files from the cwm website, not a rom files - i got them from https://www.clockworkmod.com/rommanager - i downloaded both (touch & non-touch) s4 t-mobile versions (6.0.4.7). i'm assumed those were recovery files?
Skipjack" said:
The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Click to expand...
Click to collapse
again, my apologies - i meant that i downloaded *.img files, not zips, and converted them to tars for odin use. i used a batch file to convert them from img to tar, found at xda, here: http://forum.xda-developers.com/showthread.php?t=2281287 - it seemed to do the job, odin ran and reported success. wrong files? wrong conversion?
Skipjack said:
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Click to expand...
Click to collapse
given a choice, i'd like to do what's bolded in red - but that's what i thought i was doing by flashing the cwm file i downloaded from the cwm website - but after the flash attempt it wouldn't boot into cwm, it would just boot into (i'm assuming") the stock rom i restored, which was a mess. i also unchecked auto-boot to see if that helped - but when i manually booted it didn't boot into cwm, it booted into the stock recovery, with the animated android.
i'll try downloading cwm from the sources you provided, and see if that does the trick. btw, why do you think i was able to flash the cm11 rom with (seemingly) perfect success, but wasn't able to restore either one of the full system (android) backups i made after i rooted my phone?
anyway Skipjack, thanks a ton for your assistance and i'll report back after i give your sources a try. fwiw, it sure is a great charge when a newbie like me sees a custom rom load for the first time, displaying a new ui as it boots, fun stuff.
Just download the ready yo flash tar files. Cwm has them. Twrp has them.
success Skipjack thanks to your generous time and assistance!
i ended up downloading the latest odin zip i could find and philz_touch_6.08.9-jfltetmo.tar.md5... my first try didn't take, with auto-reboot checked, my phone simply rebooted into the same problematic rom i had restored. i then tried it with auto-boot unchecked and manually booted when odin reported pass/success, and it worked. what struck me as odd was how long it took to flash, to report pass/success, around 3-5 minutes if i had to guess, a big difference compared to when i first used odin to root my phone with the["SGH-M919] CF-Auto-Root *.tar.md5 file - i'm guessing that's why it didn't work with auto-boot checked, just took too long?
anyway once i booted into philz_touch recovery i executed the wipe data/factory reset > clean to install a new rom command and then flashed the cm11 m7 (snapshot) rom, which i had flashed once before, right before i attempted to restore the stock rom it had replaced. and as was the case the first time around, it installed without a hitch and is running smooth and fast.
however now when i boot the phone, as soon as the cyanogen logo appears, very tiny text appears in the upper left hand corner which reads (i had to use a magnifying glass!) - it doesn't seem to effect the performance of he device but i'd like to get to the bottom of it, i've already searched and it appears to be a rather common issue.
kernel is not seandroid enforcing
set warranty bit: kernel
btw, i forgot to mention, when i purchased my sgh-m99 it already had 4.3 installed - when i flashed my first rom (cm11 m7) it included kitkat 4.4.2... could this be what caused my problems? did trying to go back to (restore) a 4.3 rom after flashing a 4.4.2 rom screw things up? can this even be done successfully?
and finally, at the risk of bugging the heck out of you, what roms do you prefer for your s4, assuming you have an s4? do you like aosp roms or touchwiz? does one type have a better reputation of being more stable? the primary reason i wanted to rot my phone was to get rid of a bunch of t-mobile / samsung bloatware, which i thought i could do by installing a lean custom rom. any suggestions, which are your favorites? thanks again Skipkack.
ouhned after
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
Joku1981 said:
You are right.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2594483
aeneas1 said:
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
http://forum.xda-developers.com/showthread.php?t=2594483
Click to expand...
Click to collapse
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Skipjacks said:
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Click to expand...
Click to collapse
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
aeneas1 said:
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
Click to expand...
Click to collapse
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling
Sent from my SGH-M919 using XDA Premium 4 mobile app
Kriptik210 said:
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling.
Click to expand...
Click to collapse
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
so if i'm using a 4.4.2 custom rom and want to restore a 4.3 backup i should be able to boot into recovery and restore from there? or would i need to do a 4.3 flash first, before restoring a 4.3 backup?
aeneas1 said:
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
Click to expand...
Click to collapse
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
serio22 said:
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
Click to expand...
Click to collapse
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
aeneas1 said:
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
Click to expand...
Click to collapse
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it. And you should not experience any issues restoring your back up. What were this problems?
btw serio22, do you have a favorite tw rom?
Yea serio22, what is your favorite TW ROM?
Sent from my SGH-M919 using XDA Premium 4 mobile app
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple app not working popups that made navigating almost impossible. well now when i try to restore it fails and i get the following message:
checking md summs...
md5 mismatch
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. as i mentioned, when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple "app not working" popups that made navigating almost impossible. but now when i try to restore the 4.3 backup it fails and i get the following message:
checking md summs...
md5 mismatch
update:
well it looks like the *.md5 file was pointing to my internal drive rather than external which is where i had moved the 4.3 backup (and apparently the *.md5 file didn't update or account for the move), anyway i copied the backup to my internal drive and, viola, no more md5 mismatch errors. more importantly, it restored the 4.3 backup perfectly, in the exact same state as before, without all of lagging and pop up issues i was having before, so i'm one happy camper! not sure what i did the first time around, but all is good now, for he time being, sure wish i knew what i mucked up to cause the problems in the first place, i really have no idea, other than being a newbie at this. also, fwiw, the tiny text in the upper left hand corner that appears during boot (kernal message) no longer appears now that i have restored the 4.3 system backup... fwiw2, i'm liking the philz_touch_recovery but it sure has taken some getting used to, the commands are so close together and the thing is so sensitive, very easy to accidentally select the wrong option, and some of the wrong options aren't too friendly if it wasn't what you had intended to select.
aeneas1 said:
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
Click to expand...
Click to collapse
Read my previous post more closely below. Good to see you up and running though! And no I don't have a favorite tw Rom
serio22 said:
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it.
Click to expand...
Click to collapse