Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/data wipe from other MTD roms #17

Open
fbis251 opened this issue Jun 25, 2012 · 3 comments
Open

/data wipe from other MTD roms #17

fbis251 opened this issue Jun 25, 2012 · 3 comments

Comments

@fbis251
Copy link
Member

fbis251 commented Jun 25, 2012

We need to figure out a way to check which MTD rom we're flashing from. If it's a non-upgrade rom (CM7 -> CM7 or CM9 -> CM9) we also need a /data wipe in updater.sh

@jt1134
Copy link

jt1134 commented Jun 25, 2012

Would be easy enough to check for a CM specific app or something, and wipe if not found.

If it is found and it was really a different ROM, then that's that person's fault and they need to quit kanging so hard :p

Or maybe just stick a flag somewhere, /data/.cm or something

@Fluidification
Copy link

the problem is TWRP doesn't seem to let you read the build.prop even when you have system mounted.

It works fine in CWM. So it'd work for those on CWM, but not on TWRP.

@fbis251
Copy link
Member Author

fbis251 commented May 22, 2013

I hadn't looked into this for a while (11 months...) but I think jt's suggestion would be the easiest to get working. It wouldn't be that hard to just check for the following supported roms:
/data/.cm9
/data/.cm7
/data/.aokp_ics

etc etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants