Hi,
i'm rather new with rooting, flashing and all the stuff that comes with it.
Now i have an Oppo Find7 and i managed to install the following:
-TWRP recovery
-OmniRom 5.1 nightly
-Gapps 5.1
I'm pleased everything worked but now i saw OmniRom 6.0 was available, when i tried to flash it with gapps 6.0 i encountered the first problem:
-The install of OmniRom went well but when i try to install Gapps 6.0 stock, it is saying i don't have enough storage? Can i somehow increase or free up this storage to it can fit?
Second question: If the above is possible, is there a way to flash OmniRom 6.0 and Gapps 6.0 without the loss of data? or do i still have to backup and restore with titanium backup?
Thanks in advance
Seriously? no one can answer this?
DDakara said:
Seriously? no one can answer this?
Click to expand...
Click to collapse
Stock gapps are too big, install Pico package
Inviato dal mio Find7 utilizzando Tapatalk
You should start by having ColorOS 2.1.5i installed and storage unified then install TWRP then flash OmniROM 6
Need to start clean.
Why should I reinstall colorOS? I thought once I have TWRP I could just wipe and reinstall a different custom rom.
As for the gapps package, I am using more apps than the Pico one is providing. Can I still install the others from the market?
But so there is no way to somehow open up more space to install the 6.0 omni nightly and gapps? Plus no way to install it without to do the backup and restore with titanium backup? (install so that all the apps stay the same after the update.)
Re-read my post. Unified storage is the key. It's best to do it from ColorOS. OmniROM is not a fat ROM, there should be enough space. It's exactly how I did it, although I did use one of the cut down Gapps versions as I remove a lot of Google bloat anyway.
http://opengapps.org/
Nano version should do the trick.
Well when I still had colorOs I already unified the storage because I couldn't fit more apps on it then I wanted.
It's the reason I came to use omniRom because cyanogenmod doesn't work nice with unified storage and didn't work on my phone.
Could my phone be ununified after flashing cyanogenmod or omni then? Because I never changed it back to Un unified
I have seen all the versions of gapps, although a lot of the smaller/less app packages doesn't have all the apps I am normally using.
Related
Hi All,
I am running CM13 nightly, to be precise 0821, and I see in the release logs they talk a lot about SnapDragon camera. I am not sure why but I don't have it, only the google camera. I ran nightly since they came out with a dirty upgrade each time, every other day or so...not sure what can I do to get the Snapdragon Camera?
You installed the nightly with the "wrong" gapps. You probably used " full" or "stock" version, witch replaces apps with google apps like the camera. Install nightly again with nano and you will have the cm camera. Other google apps you think you need you can just install from google play. Another way is to use "Aroma" version of gapps there you can choose witch apps to replace. I am not sure if you have to wipe the system partition to get the nano version installed, I don't expect it to be necessary
Vriesdejoop said:
You installed the nightly with the "wrong" gapps. You probably used " full" or "stock" version, witch replaces apps with google apps like the camera. Install nightly again with nano and you will have the cm camera. Other google apps you think you need you can just install from google play. Another way is to use "Aroma" version of gapps there you can choose witch apps to replace. I am not sure if you have to wipe the system partition to get the nano version installed, I don't expect it to be necessary
Click to expand...
Click to collapse
Indeed I did, I used FULL gapps. Thanks very much, makes sense now
Hey,
Recently broke my phone and bought a Find 7 as a replacement. Hate the OS so started searching for ROMS etc. Never flashed anything or rooted anything so everything I've done so far - I've just learned.
I basically want to get as close to android 6.0 marshmallow stock as possible. Which ROM is the best for this?
So basically, I've tried to flash CM13 (latest release) which I got directly from their website, all goes well however when the phone boots the screen is blank. Volume rockers work, capacitive buttons work and haptic feed back there but screen is blank. Not sure what the problem is.
ANY help at all is appreciated.
I have the Find 7 QHD version which I think is the 7S? (X9076)
Thanks all!
1) You have to flash CWM or Twrp recovery to your phone. I recommend TWRP 3.0.2. Download it for your OPPO Find 7.
Flash it. Can be done via ADB.
2) You need micro SD card formatted by the phone! Not necessary but recommended.
2) Then download needed ROM( I like crDroid : http://forum.xda-developers.com/showthread.php?t=3171600
but it's developer left it. So no further support planned) to SD card(on PC of course).
3) Put the card into the phone.
4) On the phone: go to recovery mode. Wipe data, system, cache.
5) Install ROM from the micro SD card.
That is all. Enjoy it.
Sent from my X9077 using Tapatalk
You can also check out resurrection remix rom. Find the official thread in xda for find 7. As for your screen being blank it maybe because you have a new lcd panel which the official cm rom does not support. Try flashing omni rom instead. Last nightly is from aug 30. It is very stable and very close to stock android.
Sent from my Find7 using Tapatalk
bailfire said:
Hey,
Recently broke my phone and bought a Find 7 as a replacement. Hate the OS so started searching for ROMS etc. Never flashed anything or rooted anything so everything I've done so far - I've just learned.
I basically want to get as close to android 6.0 marshmallow stock as possible. Which ROM is the best for this?
So basically, I've tried to flash CM13 (latest release) which I got directly from their website, all goes well however when the phone boots the screen is blank. Volume rockers work, capacitive buttons work and haptic feed back there but screen is blank. Not sure what the problem is.
ANY help at all is appreciated.
I have the Find 7 QHD version which I think is the 7S? (X9076)
Thanks all!
Click to expand...
Click to collapse
Also check this post http://forum.xda-developers.com/showthread.php?p=68662397
Looks like you can use rr rom wuth patch.
Sent from my Find7 using Tapatalk
Andrew111 said:
1) You have to flash CWM or Twrp recovery to your phone. I recommend TWRP 3.0.2. Download it for your OPPO Find 7.
Flash it. Can be done via ADB.
2) You need micro SD card formatted by the phone! Not necessary but recommended.
2) Then download needed ROM( I like crDroid : http://forum.xda-developers.com/showthread.php?t=3171600
but it's developer left it. So no further support planned) to SD card(on PC of course).
3) Put the card into the phone.
4) On the phone: go to recovery mode. Wipe data, system, cache.
5) Install ROM from the micro SD card.
That is all. Enjoy it.
Sent from my X9077 using Tapatalk
Click to expand...
Click to collapse
DroidSK said:
You can also check out resurrection remix rom. Find the official thread in xda for find 7. As for your screen being blank it maybe because you have a new lcd panel which the official cm rom does not support. Try flashing omni rom instead. Last nightly is from aug 30. It is very stable and very close to stock android.
Sent from my Find7 using Tapatalk
Click to expand...
Click to collapse
Hey guys,
Many thanks for those tips (especially for the LCD patch - I'll have to try that).
So CM seems to be the best for Find7 at the moment but doesn't support unified storage? Does this mean I'll have this silly app storage limit? Anyway around it using CM?
As for the rest which is best (close to stock, stable, no bugs) -
RR
Omni
Nameless
Thanks
Omni is close to stock and very stable. RR and possibly nameless are both cm based.
Used omni for a couple of months and now using rr for the last couple of days. I would choose rr because of all the additional features.
Both are great daily drivers. Both support lvm so you can unify your storage in coloros and then flash either rom.
Sent from my Find7 using Tapatalk
DroidSK said:
Omni is close to stock and very stable. RR and possibly nameless are both cm based.
Used omni for a couple of months and now using rr for the last couple of days. I would choose rr because of all the additional features.
Both are great daily drivers. Both support lvm so you can unify your storage in coloros and then flash either rom.
Sent from my Find7 using Tapatalk
Click to expand...
Click to collapse
Hmmm,
CM thread has loads of additional things like installing some of the default apps like camera etc and how to get rid of all the bloatware.
I'll probably try nameless first since it seems to be the most popular next to CM. Its hard choosing one since theres so many! Out of Omni and RR which do you think is faster? What features does RR have that made you switch over to it?
If you truly want a stock like experience without too many features and full stability in your software then I would recommend Omni for you.
RR and DU have a lot of extra features relating to various visual effects that can be tweaked to your liking which can make your software look pretty, if you are interested in that sort of thing.
Cm is also stock like experience with some bugs here and there, nothing too big.
Nameless is based on cm with a few extra features but personally that Rom gives me bad battery life. (can be different for you)
Exodus, Mokee and Crdroid are just better alternatives to CM regarding features.
Edit: There are Roms that provide you with the option of LVM and there are those which only support stock partition. (Lvm is a way to enhance storage capacity).
Cm and a few other Cm based Roms that do not support lvm can be used with the chinese partition instead which also increases storage. But that is a bit lengthy process and for someone new like you I would recommend you to stay with a Rom like Omni which does support LVM.
Hope all this helped somehow
When will have official support?
I wanna know too!
No reason to expect official support for bleeding-edge android software on old (budget) devices. Sorry to be the one to tell you :/
Swift will get official cm14.1 support dont worry guys... Even moto g got why the swift dont. Developers stated that at least 70% of the actual devices will get it. And if u dont get it for swift seed will get it soon and u can use it on swift like i use crackling on gm4g
[email protected] said:
Swift will get official cm14.1 support dont worry guys... Even moto g got why the swift dont. Developers stated that at least 70% of the actual devices will get it. And if u dont get it for swift seed will get it soon and u can use it on swift like i use crackling on gm4g
Click to expand...
Click to collapse
My phone is a gm 4g but i have always treated it as a swift
It has also stopped CM13 support?The latest nightly is on 18 November.
They have not stoped cm13 support but updates it more rarely because the build only when major changes are there. And second they are working on cm14.1 and are focused more on new cm version...
Guys I'll be building an unofficial CM14.1 for the swift tonight, I'll post when it's here
Why dont. Build rr remix N 5.8.0 64bit so we can use it with foxy kernel...
[email protected] said:
Swift will get official cm14.1 support dont worry guys... Even moto g got why the swift dont. Developers stated that at least 70% of the actual devices will get it. And if u dont get it for swift seed will get it soon and u can use it on swift like i use crackling on gm4g
Click to expand...
Click to collapse
Do you have a source for these claims?
The cm13 nightlies have all moved to weeklies unless some urgent bug is found,
As a reference
https://github.com/CyanogenMod/hudson/commit/5f49ecc49fcf22358ca2a87190df20ed9bad6da3
VivaLaVent said:
Guys I'll be building an unofficial CM14.1 for the swift tonight, I'll post when it's here
Click to expand...
Click to collapse
Any news ? I also planned to build CM14.1 too but in the crackling repo there is no branch called cm-14.1
Math314 said:
Any news ? I also planned to build CM14.1 too but in the crackling repo there is no branch called cm-14.1
Click to expand...
Click to collapse
Yeah I stumbled on that problem too and gave up.
Ok, so we have to wait for an official release of CM14.1 for the swift.
Math314 said:
Ok, so we have to wait for an official release of CM14.1 for the swift.
Click to expand...
Click to collapse
I found out that you can install official CM14.1 for seed on WileyFox Swift. First flash stock General Mobile 4G ROM using fastboot, then flash TWRP for seed and CM14.1 for seed.
I'll send detailed instructions if you'd like.
VivaLaVent said:
I'll send detailed instructions if you'd like.
Click to expand...
Click to collapse
Yeah I'd be very interested. I have some time to try it during the Christmas holiday.
Math314 said:
Yeah I'd be very interested. I have some time to try it during the Christmas holiday.
Click to expand...
Click to collapse
Okay so here is what I did and I am now running official CM14.1 arm (so no 64 bit). From my experience it is very fast, very battery friendly and most importantly: very stable.
WHAT YOU'LL NEED:
TWRP for WileyFox Swift (crackling)
General Mobile 4G (seed) stock rom
TWRP for Android One 2nd gen (seed)
CyanogenMod 14.1 for Android One 2nd gen (seed)
Optional, but I strongly recommend these:
Open GApps (ARM, 7.1, pico variant)
Google Pixel Bootlogo and Bootanimation
INSTRUCTIONS:
First, I suggest making a backup using TWRP for WileyFox Swift (crackling). I strongly suggest that you backup everything, in case something goes wrong or you aren't satisfied with CM14.1.
Now for effectively installing CM14.1 on the device:
YOU WILL LOSE ALL DATA AND INTERNAL STORAGE PAST THIS POINT UNLESS YOU BACKUP!
Download the General Mobile 4G (seed) stock rom. We need this in order to make sure the device identifies as an Android One Second Generation device (seed) instead of WileyFox Swift (crackling). The devices are clones and are essentially the same hardware. Once you've downloaded the stock rom, unzip it. Then put your device in fastboot mode and execute "INSTALL_MOB30Z.exe". Choose "A. INSTALL STOCK ROM" and wait for it to complete.
Now install TWRP for Android One 2nd gen (seed).
Now boot into TWRP recovery and got to Wipe > Advanced Wipe. Check Dalvik / ART Cache, System, Data, Internal Storage and Cache.
When the wipe is complete, go to Reboot > Recovery to reboot into recovery again. Now install CyanogenMod 14.1 for Android One 2nd gen (seed).
If desired, install Open GApps (ARM, 7.1, pico variant). To replace the "General Mobile" boot image with the Google logo, also flash Google Pixel Bootlogo and Bootanimation.
Let me know if you need help. Happy holidays! :fingers-crossed:
arvinquilao said:
IMPORTANT: Please note that the latest official TWRP for seed is not yet updated to handle CM's updater app. If users want to update to latest nightly, they need to download the zip and flash normally using TWRP. CM updater app is not recommended until the patched official TWRP is released.
Click to expand...
Click to collapse
Currently I have unofficial LOS 17.0 and I would like to install oficial LOS 17.1.
Which options from TWRP should I use to preserve data,sms, phone history and apps?
Are there any drawbacks or it is better to install fresh out of the box new LOS? If there are any pitfalls that I shoud avoid?
First place to search for an answer is in the device forum. Is there no lineagOS 17 thread?
You can always try to wipe system only, and GApps, if they have been installed before.
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Can you share the link of the other builds please?
RezaUllah__ said:
Can you share the link of the other builds please?
Click to expand...
Click to collapse
Havoc: https://download.havoc-os.com/?dir=arm64-aonly
CrDroid R Mod: https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
AOSP: https://forum.xda-developers.com/t/aosp-9-0-2019-08-25-phh-treble.3831915/
Ressurection: https://forum.xda-developers.com/t/resurrection-remix-unofficial-2018-06-28-phh-treble.3767688/
Good blog! I truly love how it is simple on my eyes and the data are well written. I’m wondering how I could be notified when a new post has been made. I have subscribed to your feed which must do the trick! Have a great day!
meta trader 4
IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
The 2nd link is twrp ryt?
RezaUllah__ said:
The 2nd link is twrp ryt?
Click to expand...
Click to collapse
3rd link
It’s nearly impossible to find knowledgeable folks on this topic, however, you appear to be there’s more you are talking about! Thanks
Monoprice 110010
IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
Bro it shows this...why?
IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
Ok it I flashed it ...but it shows that I can't wipe data ..shows error
RezaUllah__ said:
Ok it I flashed it ...but it shows that I can't wipe data ..shows error
Click to expand...
Click to collapse
Data is encrypted. You can't just wipe it. Before you enter advanced vipe, theres an option "format data". Enter it, type "yes" (it's just a confirmation) and ur data is formated
If you then run MIUI or flash lineage and run it, it will again encrypt data
IpyZ said:
Data is encrypted. You can't just wipe it. Before you enter advanced vipe, theres an option "format data". Enter it, type "yes" (it's just a confirmation) and ur data is formated
If you then run MIUI or flash lineage and run it, it will again encrypt data
Click to expand...
Click to collapse
So if I just use format data ...I am good to go?
RezaUllah__ said:
So if I just use format data ...I am good to go?
Click to expand...
Click to collapse
Yeah. Format data just reformat partition. It clears every encryption, or any other things that can possibly block you from wiping it.
IpyZ said:
Yeah. Format data just reformat partition. It clears every encryption, or any other things that can possibly block you from wiping it
Click to expand...
Click to collapse
Reformat partition? How do you do that?
RezaUllah__ said:
Reformat partition? How do you do that?
Click to expand...
Click to collapse
I mean, option "format data" is doing it for you
IpyZ said:
I mean, option "format data" is doing it for you
Click to expand...
Click to collapse
Ohhh ok
So I go to wipe , format data , type yes , after that go to install ...then flash the ROM ? Like this ?
RezaUllah__ said:
Ohhh ok
So I go to wipe , format data , type yes , after that go to install ...then flash the ROM ? Like this ?
Click to expand...
Click to collapse
Yeah that should work.
Please remember that all your personal data like photos or documents will be gone so, make sure u made a backup
You produced some decent points there. I looked on the internet with the problem and discovered most individuals go in addition to along with your website.
Internet Plans and Offers
how stable is the rom?
Well, many apps just don't works, because they are thinking that the device is rooted. In some way it's true.
There are some strange behaviours of fingerprint detector.
But overall the ROM is not crushing
I haven't noticed any other bugs or I do not remember them. But that was mine main pain about this rom
alcatel4010x said:
how stable is the rom?
Click to expand...
Click to collapse