So, after much research and trepidation, I flashed my first ROM to my i717 last week. Then I decided I didn't like that ROM and flashed another an hour later. So far it's been stable and speedy. I'm very happy. Thanks to XDA-Developers, Google, the Internet, and everyone who made this possible.
So, now, here's my simplified guide to doing what I did. This should NOT be taken as gospel. Please read as much as you can first. But, in an effort to give back, I thought a simple, step by step guide (or, more like links to the guides I found helpful) would be useful to someone. Are we sitting comfortably? Then let us begin.
1. Go here - http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/ - and root your phone. It will also install ClockworkMod Recovery. Both of these need to be done before you can flash a new ROM.
NOTE: I hear that TWRP is the preferred recovery app. I've tried it and it's very nice. It just so happens that I had ClockworkMod installed when I actually decided to flash a ROM. But use whatever you like.
2. Go to the Play Store and buy Titanium Backup Pro. Well, actually, download the free version then buy the Pro key. There are other backup methods, but I like this one.
3. Backup EVERYTHING. You might never restore a particular app, but best to have it and not need it than need it and not have it. I like to use the Google Drive option in Titanium to push by backup off my phone. But you can just hook it up to your PC and copy the backup folder from your SD card to your PC. This is just in case something REALLY bad happens. Best to have an off-phone backup.
4. Find a nice ROM to settle down with. I'm using Revolt (http://forum.xda-developers.com/showthread.php?t=2288566&highlight=revolt) but do your research and find one you like. If you decide to go with something built off Android 4.2 or 4.3 then you'll lose the Samsung Touchwiz stuff (fancy SPen features, etc.), but to me that wasn't as big a deal as I though.
NOTE: Make sure you know if the ROM need an additional Google Apps package. Sometimes they're listed with the ROM, sometimes not. Read and make sure or you could lose a lot of phone features or it may not even boot. Again, READING IS YOUR FRIEND.
5. Save the ROM (and GApps file if needed) to your phone's SD card (internal or external doesn't matter)
6. Boot into recovery (Hold Vol UP+Vol DOWN then press PWR and hold all 3 until you feel a vibration, then let go of PWR). When ClockworkMod (Or TWRP) comes up, RUN A BACKUP!
7. Read 6. Make sure you actually do it. I'll know.
8. Once you're sure you have your Titanium and ClockworkMod backups, follow the instructions for installing the ROM. Usually this involves (from ClockworkMod or TWRP):
a. Factory Reset
b. Wipe Cache (this is usually a part of Factory Reset, but doesn't hurt to do again)
c. Wipe Dalvik Cache (see cyanogen's response here for what this does - http://forum.xda-developers.com/showthread.php?t=519495)
d. Flash new ROM
e, Flash Google Apps (you can also wipe cache and Dalvik cache between d and e)
9. Now the moment of truth. Reboot. Wait. This can take some time, so don't fret if it seems to be taking too long. I'd say if it's over 15 minutes then you might need to worry, but chill before then)
10. When it does boot, you'll basically have a fresh, new phone. You'll need to enter your Google account and follow all the usual stuff you did when you first got your phone.
11. Leave your phone alone now. You can click around, but don't install anything new just yet. I've seen many a post about letting things settle. So, maybe, poke around for 15-30 minutes just to see but don't change anything. Then Reboot
12. Now reinstall Titanium. You can start reinstalling your apps. DON'T reinstall standard apps or they could break (e.g. email app or its data) as the new ROM might not support the old version of the app. My rule of thumb is don't restore any data I can get back from my online accounts (Email, FB, G+, Keep, etc.). All of your pics and that should be on your SD card and should not need to be restored.
13. That's it. If you enabled a scheduled backup in Titanium you might want to disable it for a while to make sure you like what you have. That way, you can go back if you don't like it.
Hopefully that helps someone. Please forgive any mistakes or omissions and if anyone with more experience wants to give it a once over I'd appreciate it.
Thanks and good luck.
Sorry guy, but on step one there is a very high probability of someone bricking their phone.
Why? Because it has happened about 100 times over the past two years from people using that site/method. If you flash the wrong kernel you kill your precious.
You should edit your step to say in the strongest terms triple check your operating system and get the correct kernel.
And step one is unnecessary because all roms here are already rooted.
1. Flash TWRP using pc and Odin.
2. Download new rom.
3. Boot into recovery.
4. Wipe cache, system, data.
5. Flash rom. Boot and wait 10 minutes.
6. Check settings for networks.
7. Optional modem flash.
Only wipe that's needed is a factory reset within recovery. That wipes /cache too. The dalvik cache resides on the data partition and is thusly wiped as well.
The Rom will have a format /system line within the updater script.
And within titanium backup don't backup or restore system settings (anything in the list that's red.)
And as said rooting first isn't needed unless you've been using stock for awhile and have apps you'd like to backup first... the easiest way to root is simply flash the latest twrp with Odin.. boot into recovery... then when you go to reboot the system it'll see that you're not rooted and ask if you'd like to do so.
Thanks for the feedback. Like I hope I stressed, this is the method that worked for me.
I guess I have the terms mixed up in 1. I'm saying to install ClockworkMod (or TWRP) and root your phone. I want to root it here because I want Titanium installed before I change ROMS so I can go back to exactly how everything was before modding if I want. Does that make sense?
Also, can you tell me what's specifically wrong with the site I link in Step 1? I was on ICS at the time I think. Does it brick if you do it on JB?
I'll change the step to say to go here instead - http://teamw.in/project/twrp2/96
Is that better?
Also, can you explain your cache wipe suggestions. I've seen the official instructions say to Reset, then Wipe Cache, then Wipe Dalvik. I know the last 2 are included in the first, but why are we explicitly asked to do them again? Why do you think we don't?
My thinking behind adding it here is that it does no harm and if some devs think that not doing it will cause problems then why not include it to be extra safe.
If you wanted it back to the way it was before modding anything then you could flash a custom recovery and do a nandroid backup before rooting at all.
Titanium backup needs root. If you want your app data after flashing a rom then that's when it's needed.
As far as extra wiping... putting your arms over your head spinning in a circle while chanting a manta does no harm either and is just as effective.
When you flash as often as I do... you wanna streamline the process. Extra anything is just that... Extra... and is just a waste of time
His first step is correct. No one that I know has bricked their phone using those directions because that link does not install any kernels. And it never did. It works for all versions of android. Even after all this time there is so much misinformation given.
Studacris's help is as good as gold though. He has put me in my place in the past.
Thanks Everyone.
Related
Hello everyone,
I'm new to the Eris. I've had it for a few months, but this is the first "in-depth" thing I've done with it.
I've decided to take the plunge and root the phone. I'm going to use the on-screen method.
My question is this: What do I need to do to prepare? I've got all my apps backed up to the SD card, and the phone is charging right now.
Any suggestions as to what ROM to use? Or what I need to get the Froyo update, etc?
I'm new, so I'm browsing and learning, but any information you guys have would be great. Thanks in advance.
If you want a Froyo rom, that is what you'll need to download. There are about a half dozen in the development section and all mention "Froyo" in the title. Read the entire thread and it's not a bad idea to read some comments. If the developer says you need the google apps aka gapps zip, get it too. Put both files (or only one if gapps isn't needed) on the root (not in any folders) of your sd. Once you're rooted you should enter recovery by powering off, then boot holding power and vol up (rooting instructions may take you there anyway). Youll see options to reboot, ms toggle, backup/restore, etc. Go to back up/restore and create a nandroid by following the prompts. Press vol down until you return to the home screen, then go to wipe. Wipe data/factory reset and wipe dalvik cache. Vol down back to the main screen and flash the new rom and gapps (if needed). ENJOY. Note: Read all instructions thoroughly before rooting. If any instructions i've listed are different then those listed in the official instructions, follow them first. Once you're rooted and begin changing roms frequently you need to always make a nandroid of the current rom your own (in case you dont like the new one or have problems flashing it), wipe data and dalvik (ext partition too if your sd card is partitioned and you're using a rom which allows apps2sd via a partitioned sd card - froyo currently does not), and backup your apps/settings via the app of your choice before flashing. If your upgrading your current rom you usually wont have to do a wipe (the developer will indicate it in the instructions).
It's a good idea to back up your apps before flashing new roms. Titanium is my favorite app but its for root only. Search the market. You can probably find an app to use before you root.
Sent from my Froyo Eris using XDA App
joshw0000 said:
If you want a Froyo rom, that is what you'll need to download. There are about a half dozen in the development section and all mention "Froyo" in the title. Read the entire thread and it's not a bad idea to read some comments. If the developer says you need the google apps aka gapps zip, get it too. Put both files (or only one if gapps isn't needed) on the root (not in any folders) of your sd. Once you're rooted you should enter recovery by powering off, then boot holding power and vol up (rooting instructions may take you there anyway). Youll see options to reboot, ms toggle, backup/restore, etc. Go to back up/restore and create a nandroid by following the prompts. Press vol down until you return to the home screen, then go to wipe. Wipe data/factory reset and wipe dalvik cache. Vol down back to the main screen and flash the new rom and gapps (if needed). ENJOY. Note: Read all instructions thoroughly before rooting. If any instructions i've listed are different then those listed in the official instructions, follow them first. Once you're rooted and begin changing roms frequently you need to always make a nandroid of the current rom your own (in case you dont like the new one or have problems flashing it), wipe data and dalvik (ext partition too if your sd card is partitioned and you're using a rom which allows apps2sd via a partitioned sd card - froyo currently does not), and backup your apps/settings via the app of your choice before flashing. If your upgrading your current rom you usually wont have to do a wipe (the developer will indicate it in the instructions).
It's a good idea to back up your apps before flashing new roms. Titanium is my favorite app but its for root only. Search the market. You can probably find an app to use before you root.
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Wow, thanks for getting back to me with such detail. Very, very much appreciated. It turns out however, that I won't be able to do this.
I checked out http://forum.xda-developers.com/showthread.php?t=742228
I found that I had release keys under my build number, which indicates is the 2.1 leak - which really sucks, because I got the update OTA... why would they send out a leaked platform? That sucks
Ah well, thanks very much for your help. I'm going to take a look at my brothers phone, and see if we can root that. Thanks
You CAN root ANY eris now. Do a little more research.
Sent from my Froyo Eris using XDA App
my advice would be to save yourself the hadache and just dl the 1 click root app. soo worth it plus it goes to a good cause...http://forum.xda-developers.com/showthread.php?t=742228
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
skot85 said:
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
Click to expand...
Click to collapse
You will lose your bootscreen during any ROM flash, plus whatever your boot script is I assume it's somewhere where it would get lost, too.
This may not work for your apps and system settings, but it's safe to try, then you'll know for sure if it'll work.
1. Go to your recovery and create a Nandroid backup of everything just the way it is.
2. Wipe Dalvik cache ONLY, do NOT Factory Reset/Wipe Data.
3. Flash GSB v2.6 and immediately after flash the GAPPs package, just like before.
4. If you had flashed the Cache2Cache script before you have to do that again as well, right after flashing the GAPPs.
5. Reboot and test everything to see if everything works to your satisfaction.
If it's doesn't then you have the Nandroid backup that you can restore. I can provide instructions that I use, and at least one other person has recently used and reported good about which uses Titanium Backup, but you'd really probably want to buy it off the market for it to be easier to do Batch backups and Restores (choose Menu/Batch from TB's main screen).
1. First, make sure the option is checked in TB's preferences to "Force to same location". FYI I do NOT use the checkbox for "Migrate system data". At THIS time (you can change it later), I suggest changing the Compression method to No Compression. This'll make sense in step 6.
2. From Menu/Batch, choose "Backup all user apps + system data".
3. Boot into recovery, do a COMPLETE wipe (Factory Reset/Data/Dalvik cache), flash your ROM and then your GAPPs (it's recommended at this time to NOT flash C2C just yet).
4. Reboot, SKIP setup of your Google account, go into Preferences/CyanogenMod settings/Application and check the box for "Allow application moving". I also change "Install location" to External, but that's up to you; this is just what works for me.
5. Boot back into recovery and flash C2C and reboot the ROM again.
6. Use File Manager, which comes with GSB and navigate to the TitaniumBackup folder (not TitaniumBackup-system). Find the Titanium Backup apk app installer file and reinstall it from here.
7. In TB, under Menu/Batch, choose "Restore all apps with data".
After this is done, reboot. If this works for you and you want to do this again in the future, you can make a copy of the Titanium Backup apk file to some other folder, that way you can re-enable compression in TB's preferences for future backups. I recommend LZ0.
I've been using this second method for the last 3-4 new versions of GSB, don't know how it would work with such a big jump in versions. If neither of these work for you, let me know if you still need help.
You will lose your bootanimation and any scripts you have but your apps will be fine. Like WRT said above just make sure you do a nandroid back up in recovery then wipe cache only. Once that's done flash 2.6 and gapps. Enjoy!
DINC|CM7|SLAYHER#27
Awesome. I had done a nandroid and ti backup to prepare, but I never saw the option in ti for force same location. I know how to backup and reinstall my lockscreen sounds and bootani, so I've got that down. Now that I look there's a 2.7 release which integrates the sdcard speed fix, so I won't need my init script now
Thanks for clearing that up for me, I'll post back when its done and tested if there's any issues.
Update: Well everything worked great! Thanks for all the help guys
i just recently rooted my droid eris, i've had it for about a year and had the latest ota update. I did the one click root and now i'm currently running the vanilla tazz rom. I noticed there is a new gingerbread cynogenmod, http://forum.xda-developers.com/showthread.php?t=944430 and i'd like to to run that rom, is there anything i should know from switching from one rom to another? Or any other advice anyone might have would be useful as well. Thanks
1. I would download Titanium backup from the market. Instructions for its use can be found on its official page. Backup your apps but not your settings using Titanium Backup.
2. In the link I'm about to give you insert this step after step 4:
(step 4.5) On the recovery screen use the volume down button to select "make nandroid backup option". Make nandroid backup by depressing trackball.
3. Here is the link with info on copying ROMs
http://forum.xda-developers.com/wiki/index.php?title=How_to_copy_a_ROM_to_your_Eris
4. If you experience serious problems with your new configuration, you can always reboot to recovery and use the nandroid restore option to revert back to your previous ROM.
5. You can use Titanium Backup to restore your apps to the new ROM.
Best of luck to you.
I'm sure you have read this and done it having a new ROM ànd all but after completion of your NAND backup it can't be said enough to do your wipes prior to flashing. Follow directions in the thread for the custom ROM but just to be safe I always wipe data and dalvik unless instructed specifically not to do so. Also, depending on your SD storage capacity I always keep extra copies of the ROM I have and the one I'm flashing but you definitely not necessary esp with a nandroid backup. I'm just always flashing and it can't hurt.
Also you may need to enable USB toggle in recovery and delete 'android secure' folder. I guess my best advice anyone can give is follow the directions in the ROMs thread I didn't look to see which it was. If you are unclear on anything before flash wait until you are sure. Hope we helped. I'm still learning every day.
sent with FR$H lemunz
I was attempting to mod my build prop to look as the phone was a different phone. Well, like an idiot. I deleted it all together from the system folder. But, I did make a copy of it. But, My phone goes into a boot loop. Any ideas as to how i can push the backed up build prop to my system folder? I can get into CWR. if this helps.
[Edit] So, here is what I have tried so far.
While in CWR I made a Nandroid backup of the broken system. Then i connected the phone to my computer. And i copied all of my Nandroid backups over to it. A little info on my backups. The ROM that I was running before I killed it was BAMF SoAb 1.04. I had made a backup of that ROM when i first installed it. So I opened the good Nandroid and extracted the build prop from that. Then i went into the broken ROM and did and Un RAR of the system folder. I then took the build prop and inserted it into the system folder. I attempted to Re RAR it. But, I keep getting error messages. So, what i am looking for is a fool proof way to Re RAR/ZIP or what ever is the best course of action in my case.
So, I might as well give the answer that I was not looking for to the question. But non the less it did work. So, this is what I had to do to get it back to what looks like the working version of the ROM that I broke.
What I did was an advanced restore. I would suggest one thing that every one do. Once you load a ROM onto your phone and you see that all the basics are working. I would do a Nandroid of that ROM. That way in the future, you will have the base to build off of if something goes wrong in a mod.
If you never did a Nandroid of the ROM when you first loaded it. I would suggest downloading or finding the copy of the ROM in question. Installing it on the phone and then doing a Nandroid of it.
So, lets say that you make it so that you can not boot into your current ROM after doing something dumb like. I don't know, like deleting the build prop file. LOL
Here are the steps that I took after semi bricking this thing.
Step one- Boot into clockwork recovery
Step two- Make a Nandroid of the ROM that you broke. Reason being is because that ROM is set up just the way that you like it.
Step Three- Go to mounts and storage then mount USB storage and backup everything you deem important for that just in case scenario. But most importantly, backup the nandroids that are in your clockwork folder.
Steep Four- Go to wipe data/factory reset and after that wipe the cache partition
Step Five- Go to backup and restore. Select advanced restore and select the original just out of the box ROM that you had made a back up of when you first loaded it to your phone. Select restore system. After that restore has completed back out of there.
Step Six- Select backup and restore again. Then advanced restore again. Now select the ROM that you had broken. Select restore boot,data and cache. Do not select system. That part of the image in this case is broken.
After you have completed these steps boot the phone. You should be good to go. I know that I am now. I know that depending on what it is that you broke will depend on what you do and do not load to your phone through the advanced restore options. But I suppose if we did things correctly . Like making a Nandroid before we went messing with things, we would not have had to go through this in the first place. But, some of us get a little to impatient at times and jump the gun. Any way, lesson learned. Well at least for now.
I would hope that no one has to look for a post such as this. Because it most likely means that you are going insane looking for ways to get back all that you have lost. I know that I was a bit irked. And I literally spent all day looking for help. And to no avail. So I decided to experiment with things. Luckily, I had the patience to not give up. Now I am right back to where I started before I messed the phone up. Oh by the way. I suggest making a backup now. You don't want to have to do this again. Not that it was hard or anything. But do the smart thing and save your self a hand full of steps and time. If I had done the proper thing last night. I would have been able to go to work today. Yes, me working is dependent on me having my cell. Why? Because, I use tethering on my Thunderbolt to connect my Xoom to the internet. And Google maps is in need of data to work properly. And i drive allover New England. Any way, enough about me. I hope this was helpful to whom ever found this.
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
opethfan89 said:
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
Click to expand...
Click to collapse
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Mightycaptain said:
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
opethfan89 said:
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
Click to expand...
Click to collapse
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
opethfan89 said:
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
Click to expand...
Click to collapse
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Mighty, just wanted to report that flashing TWRP 2.5.0.2 from within ROM Toolbox Pro worked like a charm. I'm on TWRP as we speak.
Thank you so much for your responses. If anyone else has anything to add, or a different response to my questions, please do so! In the meantime, I'm going to try to figure out how to get my nandroid backup working...
Cheers!
*EDIT* Made a backup with TWRP (whose interface is bloody phenomenal, btw), flashed CWM and its working like a charm!! Going to try the st0ckdr0id one as well. Still working on getting that nandroid working so I can recover my stuff and get to customizing!