Related
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
dlcsboop said:
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
Click to expand...
Click to collapse
Well as long as you're wiping between different ROMs you should be fine. And even if you are there won't be any permanent damage. The only way you can brick your phone is by installing a bad/old radio.
Even if there's a limited number of "flashing" the phone you won't reach it before you get a new phone.
Likely in the millions of times.
Don't worry about it.
Its the same question like "how many times can you write data on a sd card", you already got a new one when you reach that number
Flash memory has a certain number of read write times until it fails. But that number is so high that it will be years from now.
how can i know if i have a bad sector??
Amritttt said:
how can i know if i have a bad sector??
Click to expand...
Click to collapse
You have to wipe/install a new rom and copy logs to sd card from either other or advanced menu, havent used amon_ra recovery in forever
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
Lol, I may be able to tell you soon, flashing nightlies every day
How many stars are there in the Galaxy?
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
EVERY DAY ISN'T ENOUGH!!!!!!!1111oneeleven
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
Hey, I am a total newbie but I would like to flash the nightlies as well. I usually backup all my apps and settings using Titanium Backup, do a Nandroid backup, wipe and then flash the new ROM. However, backing up all apps and settings using Titanium Backup and restoring them after flashing the nightly is quite time consuming. Even worse is arranging the application short cuts / widgets on the desktops after a fresh install.
Nandroid will allow me to go back to backed up version after I have played around with the nightly for a few hours. But then I lose all the features of the nightly once I am back to my old ROM. As I am carrying only a single phone, it becomes mandatory for me to restored the Contacts, Messages, Applications and Settings after flashing a new ROM.
It may sound stupid but is there a better and faster way of doing things without having to restore all applications/settings from the backup so that I also could try out the nightlies? How do you manage this?
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Exactly 6.3 times. That is all. But nobody mentions it.
danger-rat said:
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, danger-rat! I'll give it a shot
meechto said:
Thanks, danger-rat! I'll give it a shot
Click to expand...
Click to collapse
I strongly suggest wiping cache and dalvik-cache prior to flashing a new nightly, it prevents **** and doesn't affect your settings/files
Haven't been on CM for awhile, but if you use Launcher Pro or ADW they have Homescreen backups. Have had good luck with MyBackUpPro too.
Ken
3 times. 1...2...crunch...3. Haven't you all seen the tootsie pop commercial?
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
How many licks does it take to get to the Tootsie Roll center of a Tootsie Pop? LMAO, that's what I WANNA KNOW!
I've searched for half and hour and looked through XDA's suggested topics before, so I apologize if this is a beaten dead horse.
I've had a problem for a while, I believe when my phone (CDMA HTC Hero) was stock, then through Fresh, CM6 and now CM7 2.3.3. at least 50% of the time I try to answer an incoming call it immediately "boops" at me and hangs up. Additionally, at least 50% of the time I have to send/dial a number more than once for it to connect. It will ring, click off a few seconds and "boop", hang up. Often the person on the other end will tell me their's rang once but when they picked up I wasn't there.
Now adding to this oddness, unless I go through a tunnel I almost never drop a call once it's active. Adding more wierdness, I found out my sister who also has a CDMA HTC Hero (rooted so I could add wireless tether but otherwise still on Sprint's 2.1 stock) experiences the same sort of conditions.
Is there something I can solve here or is it just an anomaly I continue to live with for another couple months till I upgrade? Thanks to this forum and the developers I've managed to remain happy w/ my phone for 2 years because I get to make it "new to me" every couple months (more and more often, it's addictive) but I feel it's showing it's age and I'm ready to upgrade.
Thanks, Travis
have you updated your PRL and such recently?? sometimes that causes phone answering wonkiness..
I often say I know just enough to be dangerous
.....a search tells me the PRL is my phone's list of local towers?...... I haven't intentionally done this ever. Do I need to somehow flash back to a stock ROM (avail. in here?) and then restore my current after I "update PRL" or has 2.3.3 added this feature and I'm just missing it.
Thank you for the help, sorry for current ignorance
sobamaflyer said:
I often say I know just enough to be dangerous
.....a search tells me the PRL is my phone's list of local towers?...... I haven't intentionally done this ever. Do I need to somehow flash back to a stock ROM (avail. in here?) and then restore my current after I "update PRL" or has 2.3.3 added this feature and I'm just missing it.
Thank you for the help, sorry for current ignorance
Click to expand...
Click to collapse
yeah.. there are plenty of stock based roms floating around here.. nifinite has some of the best..nandroid your current setup, flash a stock, then go to settings update PRL/Profile, after everything updates, just use your nandroid to get back to your current setup..
easy as pi
Nandroid equivalent to my CWM backup I assume?
I'll search to find stock based (those the sense ones?) or point me to one if you don't mind.
I'll happily do this 3.142 times if it corrects this minor irritation
sobamaflyer said:
Nandroid equivalent to my CWM backup I assume?
I'll search to find stock based (those the sense ones?) or point me to one if you don't mind.
I'll happily do this 3.142 times if it corrects this minor irritation
Click to expand...
Click to collapse
yes your CWM backup is what i am referring to..
THIS is the one that i use to update
EDIT: forgot i had it in my dropbox
Much Thanks!!
sobamaflyer said:
Much Thanks!!
Click to expand...
Click to collapse
no problem
New Question:
backed up current rom, applied one above and I'm stuck in a boot loop? How do I get back to the recover boot screen where I can restore the backup and try another rom?
sobamaflyer said:
New Question:
backed up current rom, applied one above and I'm stuck in a boot loop? How do I get back to the recover boot screen where I can restore the backup and try another rom?
Click to expand...
Click to collapse
lol.. sorry..
pull the battery.. hold down power and home, will boot you to recovery.. wipe everything then flash the ROM again and reboot, that should fix..
Whew, minor panic averted. See how I learn new stuff, only by screwing it up
I wondered if I need to wipe cache and davlik before, will have a go at it again.
sobamaflyer said:
Whew, minor panic averted. See how I learn new stuff, only by screwing it up
I wondered if I need to wipe cache and davlik before, will have a go at it again.
Click to expand...
Click to collapse
always a good idea to wipe cache and dalvik before any new installs.. git rid of the "dingleberries" so to speak
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing
When should you do a full wipe when installing a custom rom and when is it ok to dirty flash? Can someone please explain?
Sent from my HTC One using xda app-developers app
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
lampel said:
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
easyrabbit said:
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
Click to expand...
Click to collapse
What rom are you using?
CYNiCAL2KX said:
What rom are you using?
Click to expand...
Click to collapse
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
Click to expand...
Click to collapse
Sorry I meant ViperOne...
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
Sorry I meant ViperOne...
Click to expand...
Click to collapse
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
Thank you very much for the info. So now I understand what the base is. Aside from time or laziness I would think that doing a full wipe is the way to go. Maybe I am wrong but I would rather not take chances.
Right now Iam currently having some issues. I basically did a dirty flash of the same version I am on to clear the theme and it went wrong. It never came back up after an hour in the "starting applications" state. After that I got back in to recovery (TWRP) and did full wipes and installs. They seem to go OK but then the android setup crashes right after the "name your device" part and the launcher wont start (chose Nova). Everything just hangs. I reboot but then it just hangs. I just did my nandroid restore and I am back up and running but not sure what is going wrong. I tried the install a few times with different options but everytime the setup part crashes. So my simple question is now another full blown issue haha.
I love this board tho, everyone is so helpful. One day I hope to be the one giving the advice.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
easyrabbit said:
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
Click to expand...
Click to collapse
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
CYNiCAL2KX said:
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
Click to expand...
Click to collapse
Thank you very much. I have heard back and forth on wiping the system but had never done it till now. I am still not sure what was happening. in my initial installs I allways removed sense and used Nova. The last time I left Sense and most off the apps. I also 're-downloaded the zip. it worked like a charm. soon I will start investigating kernals and updating firmwae and antennas. Will play with the basics for a while first tho. eventually I would like to try my own. However the bar is set high with venomone.
I am now dealing with sense which is ok bit for me Nova is as close to perfect a launcher for me. still investigating battery lifevetc but will probably do another flash removing sense. venomone fixed everything I didnt like about it for the most part but I love to be able to swipe up or down anywhere to get quickbar and app drawer... still testing tho, I have a full life but definitely want to contribute here... my new obsession.
I have a rooted phone with twrp installed. I've never made a firmware backup before, and I am not sure what is the best way to do it.
Ideally I would want an exact copy of the .img file, So if anything happens I could restore my phone to the previous original factory image. But I am not sure if it is possible to make a complete backup like that.
Hi
Altho I don't use TWRP but use CTR/CWM.....they are similar in that these custom recoveries (and others) offer backup of "current" firmware.
You would need to find the Official ROM for your device and flash it......except for the recovery which I assume you want to keep TWRP
Then you can reboot into TWRP and make a backup.
The backup is now a TWRP version of the original firmware.
Does that make it clearer?
2) IMHO because of upgrades, you will be better off just making TWRP backups of your current phone setup.
If you restore a made TWRP official images.....it will take you some time to do all the updates, assuming you use playstore.
good luck
aus9 said:
You would need to find the Official ROM for your device and flash it......
Click to expand...
Click to collapse
problem is, i can't get it. even contacting the company was no help. thats why I was hoping to somehow pull it off my phone first... but seems like that isnt possible?
Hi
I can't see what your phone is, maybe you can add it to your signature or reply.
OK now I understand why you posted....thanks for that.
Lets pretend the only thing you did to this phone was to root it and add apps
then go into either bootloader menu then factory reset......CTR offers factory reset as well .....so hopefully TWRP will as well
otherwise
or direct into factory reset
-----some phones can only do one way.....normally vol down plus power or vol down plus camera button plus power gets some devices into factory reset mode
reset for most devices won't delete all data and root.....you should do this thru your recovery option.
Howerver........please don't do this until you have done a full TWRP backup and made a change and then confirmed you can do a full restore.
Once done.....check "installed" playstore apps and uninstall any still showing......they can be installed later from the "all apps" tab
This is about the closest you will get to official firmware without the official rom......YMMV and try at own risk.
Note that some devices can be a bit touchy in factory reset mode so you may need to redo a wipe function.
good luck
I think I might have found my factory firmware.
According to my phone, my original firmware is 139.4.6.ghost_row.ACG.en.US and one of those files that I got it from here http://motofirmware.com/files/category/9-ghost/ is ACG_XT1050_4.4.2-KXA20.16-1.31_CFC_1FF.xml.zip
But I don't know how to tell for sure if they'll be a match, but its the closes I've been able to find so far.
my model is moto x, xt1050
http://motofirmware.com/files/file/128-acg-xt1050-442-kxa2016-131-cfc-1ffxmlzip/
http://pdadb.net/index.php?m=specs&id=5957&c=motorola_moto_x_xt1050_cdma_motorola_ghost
it looks like 442 refers to your android vesion and matches the spec page
KXA20.16-1.31 could be your build string?
see this post pls
http://forum.xda-developers.com/moto-x/general/index-welcome-to-motorola-moto-x-t2558785
as that user has a lot of info you may wish to post to it?
I am sure OP can offer better advice than me. good luck
Well if you just want a twrp back up of your factory firmware...make a back up of your current configuration of your device (really do this!).
Then factory reset your phone. There are many ways to do this...but it is up to you. Then go back into TWRP and make a back up of the newly reset
device. Once it is done, save that back up on your device and somewhere else...just in case. To get back to your original configuration, just use twrp
to restore the back up you made at the beginning.