Related
FYI - I just updated my T-Mobile SGS2. After the wipe and update, I'm unable to re-setup the application because I can't get another Serial and Activation Code from the SWTOR website.
Later I reloaded a custom ROM and tried to restore the app with Titanium, but I keep getting an "An unexpected error has occured."
So in short, if you are expecting an update for your phone, or load custom ROMs a lot, DO NOT USE THE ANDROID AUTHENTICATOR APP (until those awesome hackers find out what going on).
Fortunately I was rooted and able to restore a full system backup, to get the app back running correctly. But now I'm forced to run an older version of software on my phone.
Hopefully CS can help with a better solution or App.
I wrote down the key information I entered into the app when I set it up. I don't know if that will work later on though.
The other thing I have going for me... is that both my phone and tablet are configured for it. I did them both at the same time. That way, if one device is lost or stolen, or gets wiped, I can rely on the other.
khart1978 said:
FYI - I just updated my T-Mobile SGS2. After the wipe and update, I'm unable to re-setup the application because I can't get another Serial and Activation Code from the SWTOR website.
Later I reloaded a custom ROM and tried to restore the app with Titanium, but I keep getting an "An unexpected error has occured."
So in short, if you are expecting an update for your phone, or load custom ROMs a lot, DO NOT USE THE ANDROID AUTHENTICATOR APP (until those awesome hackers find out what going on).
Fortunately I was rooted and able to restore a full system backup, to get the app back running correctly. But now I'm forced to run an older version of software on my phone.
Hopefully CS can help with a better solution or App.
Click to expand...
Click to collapse
You can't restore the data files from an different rom, delete the data files in titanium backup and the app should work again (you just have to configure it again)
Gesendet von meinem GT-I9100 mit Tapatalk
wooki said:
You can't restore the data files from an different rom, delete the data files in titanium backup and the app should work again (you just have to configure it again)
Gesendet von meinem GT-I9100 mit Tapatalk
Click to expand...
Click to collapse
yes but what ur not getting is that in order to set it up again u have to be able to log into ur account which u cant do without a security key
I havent checked yet, but i will soon. Is there a way to shut off the security key (temporarily, of course) so that we can just shut it off, load a rom, turn it back on and "re-marry" the app? Might not be great for nightly users, but I'd like to try some different roms without losing the ability to play my game.
Psionfenix said:
I havent checked yet, but i will soon. Is there a way to shut off the security key (temporarily, of course) so that we can just shut it off, load a rom, turn it back on and "re-marry" the app? Might not be great for nightly users, but I'd like to try some different roms without losing the ability to play my game.
Click to expand...
Click to collapse
The only way to detach the security key atm is to phone support and have them remove it. I read somewhere that adding that functionality to the webpage is a high priority.
yeah. I got my ticket back about that. I went ahead and just ordered a standalone key. Not going to take the chance. haha
There must be a way to backup the application. Moving it to an emulator on my pc would be nice, but I couldn't do it...
Sanraith said:
There must be a way to backup the application. Moving it to an emulator on my pc would be nice, but I couldn't do it...
Click to expand...
Click to collapse
Any news about this?
Successfully Restored Authenticator
I know this post is old, but I've seen several similar posts concerning the same issue, and the resolution was calling Customer Support and having it removed. Anyway, I've restored the app successfully several times today. Last week, I contacted Titanium Track (Titanium Backup Support), and one of the suggestions they gave me led to an answer. "If you leave the app installed and just switch between the ROMs without a wipe, does the same problem happen or not?".
It indeed did continue to function. I then tried a "factory reset" and restoring the app, which led to the dreaded "unexpected error occurred". My next step involved, restoring all system app data/rebooting...and then the authenticator functioned. After a couple of hours, I narrowed down the 2nd app that needs to be restored. Under Titanium Backup it's - [SETTINGS/BLUETOOTH...-> "Settings Storage". By exploring this data using Titanium Backup, I saw one variable that I believe is the cause of the issue. "Android_ID".
Sorry, I can't post the link but this is from "adrynalyne" on Android Forums - "Warning. Do Not Share Nandroid Backups".
Even if your apps aren't there, and no personal information has been entered on a fresh wipe.
If someone asks for a stock Nandroid backup, kindly tell them to get lost
contagous and I learned the hard way. I sent him a completely tweaked and clean nandroid, with none of my personal info or anything like that. He has been using it and it works great.
Until AppBrain fast web installer is used. See, it IDs your device by the Android_ID, which is unique to every phone, or is supposed to be.
Nandroid backups will record this device ID, and clone it onto another device. Well, when contagous installs an app using the web installer, I get it. Without a prompt or nothing.
While I can do the same thing, and it was fun sending him pron apps and sexy men wallpapers, it has a real potential for a security nitemare. I trust contagous, but let this serve as a warning to everyone. Its also not so simple as installing another ROM and factory reset. So far as I can tell, as long as you stay on the same build OS, you will keep the same ID. The only thing that changed my ID to something else was going back to 2.1.
So friends, don't let friends share nandroids. If you do, play it smart, and delete all but the system and boot images and recalculate the md5.
Click to expand...
Click to collapse
I believe that the Star Wars: The Old Republic Security Key app is looking at the Android_ID key for a match, and then bombing out. This is only a theory from my experience. But I would suggest to anyone that's willing to try it to attempt to restore both the SWORSK and Settings Storage "SETTINGS/BLUETOOTH", rebooting, and see what happens. Of course, make a NANDROID backup before trying this!
Cbjohns said:
I know this post is old, but I've seen several similar posts concerning the same issue, and the resolution was calling Customer Support and having it removed. Anyway, I've restored the app successfully several times today. Last week, I contacted Titanium Track (Titanium Backup Support), and one of the suggestions they gave me led to an answer. "If you leave the app installed and just switch between the ROMs without a wipe, does the same problem happen or not?".
It indeed did continue to function. I then tried a "factory reset" and restoring the app, which led to the dreaded "unexpected error occurred". My next step involved, restoring all system app data/rebooting...and then the authenticator functioned. After a couple of hours, I narrowed down the 2nd app that needs to be restored. Under Titanium Backup it's - [SETTINGS/BLUETOOTH...-> "Settings Storage". By exploring this data using Titanium Backup, I saw one variable that I believe is the cause of the issue. "Android_ID".
Sorry, I can't post the link but this is from "adrynalyne" on Android Forums - "Warning. Do Not Share Nandroid Backups".
I believe that the Star Wars: The Old Republic Security Key app is looking at the Android_ID key for a match, and then bombing out. This is only a theory from my experience. But I would suggest to anyone that's willing to try it to attempt to restore both the SWORSK and Settings Storage "SETTINGS/BLUETOOTH", rebooting, and see what happens. Of course, make a NANDROID backup before trying this!
Click to expand...
Click to collapse
Some good news. I requested for the ability to restore the "Android_ID" be added to Titanium Backup, and they have made it so. I tested a couple times and can verify that it is the Android_ID that this app relies on. So for those out there, give it a try if you wish. I should note though that may have to switch the time sync "from auto to manual, then back to auto" to be able to get the site to accept the key. But yes, restoration of the Security Key has been achieved! Good luck everyone!
@Cbjohns
It's working!
I've got nandroid-backup from some months ago, when I used to play SWTOR. Now on the new ROM I couldn't make it working.
So I
1. nandroid-backup this ROM
2. nandroid-restore previous one
3. backup this SETTINGS/BLUETOOTH(only data) and SWTOR app(data+app)
4. nandroid-restore again present ROM
5. restore SETTINGS/BLUETOOTH(only data) and SWTOR app(data+app)
6. reboot(without it, it doesn't work) my phone
-and it's working.
Thanks again!!
I recently got a new phone and had to call support every time I tried a new rom. This has saved me TONS of time, thank you so much!
Cbjohns said:
I know this post is old, but I've seen several similar posts concerning the same issue, and the resolution was calling Customer Support and having it removed. Anyway, I've restored the app successfully several times today. Last week, I contacted Titanium Track (Titanium Backup Support), and one of the suggestions they gave me led to an answer. "If you leave the app installed and just switch between the ROMs without a wipe, does the same problem happen or not?".
It indeed did continue to function. I then tried a "factory reset" and restoring the app, which led to the dreaded "unexpected error occurred". My next step involved, restoring all system app data/rebooting...and then the authenticator functioned. After a couple of hours, I narrowed down the 2nd app that needs to be restored. Under Titanium Backup it's - [SETTINGS/BLUETOOTH...-> "Settings Storage". By exploring this data using Titanium Backup, I saw one variable that I believe is the cause of the issue. "Android_ID".
Sorry, I can't post the link but this is from "adrynalyne" on Android Forums - "Warning. Do Not Share Nandroid Backups".
I believe that the Star Wars: The Old Republic Security Key app is looking at the Android_ID key for a match, and then bombing out. This is only a theory from my experience. But I would suggest to anyone that's willing to try it to attempt to restore both the SWORSK and Settings Storage "SETTINGS/BLUETOOTH", rebooting, and see what happens. Of course, make a NANDROID backup before trying this!
Click to expand...
Click to collapse
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
People could do it theirselves, but some are even stupid enough to not be able.
So it would be a good solution.
Good that you can use Aroma, but I don't think most users are able to use it, do they?
EDIT: Aroma seems quite simple... But I hope for you it's stable enough when trying to stabilise the device
Hello, I'm brand new to these forums, but I've been browsing them for the past week, and Im thinking about making the plunge to CM7. I've never done anything like this before, so could you guys answer a few of my questions, and maybe put my fears to rest?
First off, let me say that I read the Moto Atrix noob guide and updated thread.
This is my phone info:
System Version: 4.5.141.MB860.ATT.en.US
Android Version: 2.3.6
I have had this phone for over a year, and everything is completely stock.
Questions:
1. I have seen various threads about the latest firmware from Motorola causing an inability to change the OS. Is this true? And if not, do all the guides I've read regarding flashing, roms, backup, etc. still applicable?
2. I want to run CM7, but is it better to install CM7 directly from their website, or use some of the versions that I have seen members offering here. What are the main differences? What do you recommend?
3. Is CM7 as stable as stock?
4. Is it possible to flash different kernels to see what type of battery life difference they make, and can you do this without changing the OS?
5. I've seen multiple times of the importance of backing everything up. My only concerns are the contacts and sms. My contacts are stored on "Motorola Services." How can I back them up? As for sms, I use an app called SMS backup and restore. It creates an xml file I think, so when I go to restore my sms messages, everything should be as i was before, right? I'm worried about formatting issues here.
I just want to make sure I understand everything so I dont mess anything up. Thanks for your help!
yep. being a virgin and knowing it has to happen gives ya them butterflies in the tummy. Don't worry, you'll be fine, WE were all virgins at one time also. There will be somone here to assist you if you need it.
1.Follow the automatic bootloader thread. http://forum.xda-developers.com/showthread.php?t=1182871
2. Read a little on the roms you are considering. The ones based on cm7 are basically the same. differences will be in themes, and extra/different features like diff apps and launchers & more or less customization options such as for settings. Have to choose which one appeals to you, and go with it. Beauty of this is if you want to try something else, only takes a matter of minutes and you can change to a differnt cm7 rom. In a lot of instances, once you are on cm7, flashing a different cm7 rom, you don't have to erase or lose your data, just wipe system and caches and load new flavor. Only takes a couple of minutes to flash a new rom, or kernal, or radio, and your data stays intact. Changing to a CM9 or a different base rom is when you will need to wipe the whole phone including data.
3. Yes, cm7 was the last revision when devs were still able to use OEM drivers, so they are stable.
4. Answered in #2
5. I don't recall which apps were good for saving your sms stuff on cm7. Seems like ages ago since I was using that! Might want to consider moving your Motorola based stuff over to Google. Contacts will be availabe there and will load automatically when you initiate your new rom. You don't need to do any formatting, but erasing will wipe areas, and will erase personal data if that option is chosen, so your concern is noted. Pay attention to what you are doing, don't wipe data from CWM when flashing if you intend on keeping your user data. You can wipe system and caches and not lose your data.
Yes back everthing up. Make a copy of your PDS folder and stash it away on your pc (do this before starting flashing), this has your phone id stuffs and a couple other valuables. Don't share that with anyone either. Make a nandroid b/u (an option in your new CWM) as soon as you can after installing CWM. You can reload that if things don't go good, and be back where you started. Install SuperuserSU (not the plain Superuser) from google play.
Just do it, you'll like it! become one of the elite!
If you ask me... You'll need a custom recovery to be able to flash CM7 anyway, so why not use it to make a proper full nandroid backup too?
I mean sure, you can try messing around with specialized apps to save and restore only the parts most critical to you (like contacts and texts), but if for any reason you'll want to completely go back, at least you'll know you can.
ravilov said:
If you ask me... You'll need a custom recovery to be able to flash CM7 anyway, so why not use it to make a proper full nandroid backup too?
I mean sure, you can try messing around with specialized apps to save and restore only the parts most critical to you (like contacts and texts), but if for any reason you'll want to completely go back, at least you'll know you can.
Click to expand...
Click to collapse
Will this full backup allow me to then only restore the data I wanted to keep? Because I know I wouldnt want to restore the whole thing.
wvcaudill2 said:
Will this full backup allow me to then only restore the data I wanted to keep? Because I know I wouldnt want to restore the whole thing.
Click to expand...
Click to collapse
CWM will allow you to restore individual partitions. So you can, say, restore just /data and leave others intact. It won't let you restore specific folders in /data though. Basically such a backup is most useful if you need to restore the entire phone to a specific state.
wvcaudill2 said:
Will this full backup allow me to then only restore the data I wanted to keep? Because I know I wouldnt want to restore the whole thing.
Click to expand...
Click to collapse
Use titanium backup to restore individual apps and their data...
Sent from my MB860 using Tapatalk 2
ravilov said:
CWM will allow you to restore individual partitions. So you can, say, restore just /data and leave others intact. It won't let you restore specific folders in /data though. Basically such a backup is most useful if you need to restore the entire phone to a specific state.
Click to expand...
Click to collapse
what all is stored in the /data partition?
Also, is there some comparison of roms out there? I've been searching through the forum, and can't seem to find any. I see NottachAtrix4G alot. Is this based off of CM7? Also, does the fingerprint scanner work in cm7?
wvcaudill2 said:
what all is stored in the /data partition?
Also, is there some comparison of roms out there? I've been searching through the forum, and can't seem to find any. I see NottachAtrix4G alot. Is this based off of CM7? Also, does the fingerprint scanner work in cm7?
Click to expand...
Click to collapse
The data partition is where your contacts, messages, settings and apps that you have installed go to.
I'm sure I saw some threads comparing ROMs, even though I recommend you try all the ROMs and see which one best fits your needs. Back when I had my old Milestone 2, everyone talked about the CM7 ROM, as it was the best to the device, but as soon as I tried the MIUI 2.3.7, never came back to CM7 (at least with M2, used it again with atrix)
Nottachtrix isn't based off CM7, it's a stock gingerbread ROM with modifications.
Yes, the fingerprint scanner works (at least on Neutrino CM7).
MaxK47 said:
The data partition is where your contacts, messages, settings and apps that you have installed go to.
I'm sure I saw some threads comparing ROMs, even though I recommend you try all the ROMs and see which one best fits your needs. Back when I had my old Milestone 2, everyone talked about the CM7 ROM, as it was the best to the device, but as soon as I tried the MIUI 2.3.7, never came back to CM7 (at least with M2, used it again with atrix)
Nottachtrix isn't based off CM7, it's a stock gingerbread ROM with modifications.
Yes, the fingerprint scanner works (at least on Neutrino CM7).
Click to expand...
Click to collapse
Thanks for a good answer. I have yet another question though.
Some of the ROMS I have been looking at advertise that they are packaged with a certain kernel. Do all ROMS contain a kernel, or will I have to flash my own depending on which ROM I choose?
Again, sorry for all the questions, I just want to make sure I dont screw this up!
Every ROM is a complete system, so it must come with a kernel. In most cases after flashing a ROM you're ready to go. You'd only want to flash a different kernel if for some reason you're not happy with the one supplied with the ROM.
This is basically identical to this thread:
http://forum.xda-developers.com/showthread.php?t=2402021
It is posted in the Nexus forum, however, and I don't know how much overlap there is between the users of that forum and this one, so I wanted to ask it here since I'm using an S4.
Basically, when ever a ROM that you're using comes out with a major revision, the expectation is that you do a clean install and wipe all data. This can be quite a hassle when it comes to restoring everything when you boot back up. Especially if it's an active ROM and you find yourself needing to do this monthly. I personally have been using Titanium Backup to restore user apps, but I don't use it for system apps as I presume some of that data might be incompatible with the newer revision of the ROM and I don't want to screw up any of the benefits that the update offers me. However, this still leaves a lot of system settings non-restorable and I was wondering what the experts on here did to minimize the complication of restoring all of their settings after their wipe their device for a software update. For example, Ringtones, WiFi/Bluetooth settings, system application options/settings. Does anyone have a good method to simplify this process of getting your phone back to exactly the way it was prior to the update or is it mostly just a tedious process you put up with every month or so?
Thanks.
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!