Cyanogenmod 12.1 lenovo tab 3 710f [unofficial] - Android Q&A, Help & Troubleshooting

Hi there, I "ported" Cyanogenmod 12.1 rom from Lenovo Tab 2 a7-20 (from this link: https://drive.google.com/drive/folders/0Bxd-XcN0S63qWjJoTVlkRXlrams which I found on this russian website: http://4pda.ru/forum/index.php?showtopic=711492&st=1100#entry63268934) to our Lenovo Tab 3 710f with Cygwin and kitchen, succesfully installed it on the device with no flashing errors through Tzul's TWRP (see: https://androidfilehost.com/?fid=673368273298949373) and then flashed the patch for the rom which I previously ported as well, then proceeded to install Gapps 5.1 pico, succesfully too.
Now the problem begins..., whenever I try to boot into the rom, it loads a little while on Lenovo splash screen just to go back to TWRP recovery menu, and it always does that. I referred to Android's Kitchen FAQ (see: https://forum.xda-developers.com/showthread.php?t=633246) but I have no good knowledge nor adequate time to setup Android SDK and debug the issue with logcat, or in any other way that I know of, so I ask for somebody to help me sort out this problem and hopefully fix it so the rom may be bootable and usable, then the community may have the FIRST EVER ACTUAL CUSTOM ROM for this device, furthermore, making it stable. YOU WILL GET ALL THE CREDIT. (well, 99.9 of it)
Here are the PORTED files.
https://drive.google.com/drive/folders/14MJTWPRnp0xeFa0O2TKNID5SGj7JW688

HI.
Im also a 710F owner. Did you get anywhere with this. Did you get your rom to boot. I'm greatly in need of a custom rom for the 710f.
Kind Regards

Any update on this? What exactly happens in the TWRP?

Custom ROM at last
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
https://drive.google.com/drive/u/0/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJ
Greetings,
David.
Updated link:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ

ChinmayDalal said:
The link returns 404, can you please reupload the file?
Click to expand...
Click to collapse
Here:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Just follow my instructions and install the July 2 rom.

Hey man, thanks for finding this. However, when I try and flash the ROM I get Error: 7 although I have the 710F version.

Error 7 means wrong ROM.
David uploaded 2 roms, for the Tab2A710F and the TB3-710F.
I flashed the TB3-710F and it works.
Works very nicely.
MicroG works too, no need for Google Apps.

...
Sorry. There are Two Little Bugs. YouTube only has up to 360p. When the screen is locked, it rotates.

DavidRGX said:
Here:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Just follow my instructions and install the July 2 rom.
Click to expand...
Click to collapse
Thankyou for finding this rom

Getting Error 7 with both the firmwares.
Edited the updater-script and then got "incompatible data, can't flash" in TWRP.
Edit: Managed to flash the ROM by formatting the cache to ext4, but now I'm facing the storage bug, it's showing 5GB instead of 8GB.

DavidRGX said:
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
https://drive.google.com/drive/u/0/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJ
Greetings,
David.
Updated link:
https://drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Click to expand...
Click to collapse
Finally after a long time ... We atleast have a working rom .. i totally appreciate it .. the rom is good but the only problem is system is taking 500+ ram ... Is there any way to make this rom lite ?

how to activate hd in cyanogen 12.1 tb3-710f

Patche v1.0
DavidRGX said:
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
drive.google.com/drive/u/0/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJ
Greetings,
David.
Updated link:
drive.google.com/drive/mobile/folders/12e6dbeMhy0GzAdj_TrkCN6Ql_qxXhXJJ
Click to expand...
Click to collapse
Hello!. Here is my contribution for this Rom.
Optimization Patch:
Programmers: For those who want to continue helping.
-It includes.
.Build.prop.
. Bootanimation. (Unmodified)
.Apps:
Es-Explorer Pro
Kernel Adiutor.
BuildProp Editor.
Root Booster.
RAR.
Terminal.
User: For Normal Users.
-It includes.
.Build.prop.
.Apps:
CPU-Z.
Root Booster.
Fix Lollipop Memory Leak. (Xposed)
-Install TWRP to flash.
-Clean Cache and Dalvik / ART Cache.
Any contribution is written to me by INBOX, or by DavidRGX.
Downloads:
drive.google.com/open?id=19V9mr9xMh1JUI4URxRYTYwtXxSyEFP7G
PDT: I speak Spanish.

Hola, necesitaria que pusieras un tutorial de como instalar paso a paso Cyanogenmod 12.1 en mi tabletlenovo tab 3 710f, ya que no encuentro la manera de hacerlo.
Gracias!!!

Hey thanks for it. I just wanna know how can I remove some apps before flashing it like File Manager, Email, Browser??
One bug I am encountering related to MAC address of the device, The MAC is changing on every on/off of WIFI radio?? How to fix it as my router can only connect limited number of devices??

...

Thank you!
Thanx a lot man!
You really saved my day, that others did mess up!
I rooted my device + wanted use custom roms.
It was an another website that had information and it was to "Tab 3 710F, but that fxxxxxg website only had roms to "tab3 710I".
I really messed up my pad.
Anyway I have some questions, the partition in my pad is only 5GB, do you know why?
Is the original Stock rom spooking around in some partition of 3GB?....as the internal memory in the pad is 8GB total...
Since this Cyanogen is based on Android 5 it dont support Adoptect storage on the fly.
I wanted originally to install Android 6 to this pad, Lenovo dont want to give it to me and thats the main reason why I rooted.
Is it possible to move whole applications to SD card and run from there?
Since the internal memory is so bad in this pad I really would like to use this feature!!!
Anyway I like this rom since unnesserary bloatware are gone and its good there is no playstore or gmail, since this pad is to one of my children and they dont really need these
DavidRGX said:
UpdatedHello there, I successfully found the work of a developer who tried to do what I did, but with success, just flash the latest july rom after formatting system, dalvik, data, (not internal storage) etc..., After it installs I advice you to immediately install gapps nano, and then reboot.
Here:
Greetings,
David.
Updated link:
Click to expand...
Click to collapse

freaking awesome man! Three bugs
1 - YouTube is only at 360p
2 - Camera is just at 1.5 (or something like that pixels)
3 - Doesn't recognize the device when I plug on the PC

Just to thank all of you for saving my kids tablet back to life!!!
It's sad that youtube is limited at 360p, but they will live with that.
Thanks!

You only hear the sound on live YouTube programs.
Is there any solution?

Related

(Mod) DUAL BOOT N910w8 (Stock and Cm)

Hello I have made a very detailed video showing how to get Stock Samsung Lollipop (5.0.1) and CyanogenMod 12.1 (5.1.1) on the same phone [n910w8] dual booting.
THIS IS DONE AT YOUR OWN DESCRETION and I am not responsible if something goes wrong or you do something wrong. I have repeated the process at least 10 times to see how it works. Even did it on a Samsung Galaxy S4 with no issues.
This video is demonstrating the installation process for the Galaxy Note 4 n910w8 (Canadian snapdragon version used in video)
PLEASE TAKE YOUR TIME even watch the video a few times before you give it a try. In the end you can always flash stock Samsung Rom and do a factory reset.
I really enjoy using this feature and having the choice between two different roms on the same phone.
You can share apps from your stock Samsung Rom to your Cyanogenmod Rom without having to reinstall most of your apps. Saving lots of space.
I hope you enjoy.
Like.
Subscribe.
Click an add or two.
Thanks and a wonderful day.
Happy dual booting.
VIDEO LINK:
Samsung Galaxy Note 4 Dual Boot/multi Rom support:
https://youtu.be/CpegzNc4ZH0
Download Link Dual Boot Patcher:
https://snapshots.noobdev.io/
Download Link CM 12.1 (trltetmo) WORKING ON N910w8:
https://download.cyanogenmod.org/?device=trltetmo
Download Link Cyanogenmod Google Apps:
http://wiki.cyanogenmod.org/w/Google_Apps
Thanks:
chenxiaolong
Working on getting support brought to the Samsung Galaxy Tab S 8.4 also. Awaiting conformation, working with the developer. No garinties but fingers crossed that another top device gets dual boot compatibility.
Does anyone have a link to this build????
cm-12-20150413-NIGHTLY-trltetmo.zip
i keep trying on cyanogenmod website but the link is down.
If anyone could help it would be greatly appreciated.
It would really help with Google cardboar/vr testing. Native sbs is reported working on the rom I am looking for and it would be worth a try.
Nice mate
So by using FolderMount I am able to save so far 3gb of space on my data folder. I transfer app data to external SD card. Link the app data on external SD card with FolderMount which tricks the app into thinking it is installed on internal data.
Then I created a backup in FolderMount. Switch roms load FolderMount. Restore backup for FolderMount. Restore link app data locations because cm and touchwiz see external SD card different and FolderMount corrects this thankfully.
Click the green linking tab a few times and FolderMount will recognize the data.
As I said I have saved 3gb of room on my internal data having app data on external SD card.
If something like this was built into our dualboot patcher it would make things easier. Maybe if we spoke to the developer of FolderMount. If not using both FolderMount and Dual boot patcher I now have 3 roms on my Note 4 and almost 4gb free space on internal data between all 3 roms. Look at the pics of before in my previous comment and this one to see.
Just finding ways of maybe booting 4 roms on one phone.
Will report back.
Think I am on to something, let me know what you think. Give it a try possibly. I will be making a youtube video to help better demonstrate.
Before and after of data saved
My current Tri Boot state on my Note 4
Currently running Touchwiz stock lollipop 5.0.1 (primary partition), cm12.1(secondary partition) and cm12(data partition) all on the same phone.
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
samurai_vara said:
Hey,
Thanks for the video. I think I made a mistake. I opened the app sharing from the main rom and updated the ramdisk. Now in CM12 I am not able to tick the share applications option. Any suggestions?
Click to expand...
Click to collapse
Try reinstalling cm12 and sharing again once you boot up.
Leonidas87 said:
Try reinstalling cm12 and sharing again once you boot up.
Click to expand...
Click to collapse
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
samurai_vara said:
I am a bit confused. The way I understand:
1. Patch the CM12 ROM and gapps.
2. Flash the patched ROM and gapps.
3. Then in the secondary rom (CM12) share apps.
So I don't need to share apps from the main ROM. It means I have to install apps on the secondary rom which will be shared to the primary rom. Is this right?
Click to expand...
Click to collapse
Once you do those 3 steps all apps should share between both the primary and secondary Rom once you do a quick reboot after enabling the app sharing. Whenever you install a new app on one or the other Rom and then boot in to one of the roms you will usually see android upgrading or upgrading apps something like that during boot up. But yea you only need to enable app sharing in the second Rom not primary. Everything from the secondary Rom seems to share with the primary Rom. Overall it is a great system. Complicated in thought but it works. Once you get a feel for it you will be impressed.
Nice. I will try this when I get home. Been wanting to run CM but gear vr has me stuck on touch jizz. Will report how it works.
Sent from my SM-N910T using Tapatalk
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
chrisa887 said:
getting ready to try on my tmobile note 4 n910t will work right? , now after i patch the cm12 file that i want, do i have to patch the gapps also or can i just got into recovery and flash the gapps once i am on cm12 rom?
Click to expand...
Click to collapse
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Leonidas87 said:
Yes it should work. The cm12.1 download link is specific for T-mobile but also works for other models such as the 910w8 (Canadian version)
As for Google apps, patch the file as you did with the cm12.1 Rom then install. If you do not patch it first it will install on your primary rom. Anything you want flashed specifically for a specific rom/location you must patch to match. For example if you install cm12.1 on secondary partition Google apps must be patched for secondary partition also or whatever partition you are using. Currently I have been installing my roms on data partition.
Click to expand...
Click to collapse
I see, I want the cm12 as my secondary rom so I patch it first then install it then I patch the gapps then install them then I can reboot to secondary rom and set everything up right?
Sent from my SM-N910T using Tapatalk
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Leonidas87 said:
I always patch my Rom and Google apps before flashing the Rom in recovery. I also flash/install my secondary Rom and then patched Google apps one after the other and then just boot into my secondary Rom, enable app sharing between my two roms, reboot and good to go.
I have had no problems installing patched Rom and apps in recovery and then booting in to the newly installed Rom. I personally like to make sure all my Google apps show up on first boot of the Rom. Saves me the hassle of errors in way. Sometimes flashing secondary Rom, then rebooting out of secondary Rom has caused me an issue that is why I install Rom and Google apps one right after the other.
Click to expand...
Click to collapse
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Great job, thank you dev.
I have question about App Sharing. Should I install Gapps on both roms or only on Primary and share them?
chrisa887 said:
When a update gets release have to patch then install on secondary right?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yes patch then install. No need to reinstall Google apps all that will still be there.

Fix error 70 install Gapps on TWRP(marshmallow)

Hi, today I'm bringing you a fix for the error 70 that will come up after installing google apps in TWRP because of system partition space problems.
You will have to follow this steps:
- Go to the recovery menu and do a factory reset.
- Search the ROM and install it.
- (This is a very important step for it to work). Go to TWRP recovery and select wipe.
- Then go to Advanced Wipe.
- Once you are there, select System partition and click repair or change file system.
- Some options will come up, and select Resize File System.
- Once you have followed all these steps you can nos install all google apps without problem.
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!
Credits: @javiblader17 (Ak as JAVIX)
Fix Error 70 Gapps in TWRP (Marshmallow)
Hi, today I'm bringing you a fix for the error 70 that will come up after installing google apps in TWRP because of system partition space problems.
You will have to follow this steps:
- Go to the recovery menu and do a factory reset.
- Search the ROM and install it.
- (This is a very important step for it to work). Go to TWRP recovery and select wipe.
- Then go to Advanced Wipe.
- Once you are there, select System partition and click repair or change file system.
- Some options will come up, and select Resize File System.
- Once you have followed all these steps you can nos install all google apps without problem.
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!:good:
Credits: @javiblader17 (Ak as JAVIX)[/QUOTE]
Thank you, good job.
Enviado desde mi XT1543 mediante Tapatalk
Thanks I had this problem with a friend's device. I installed pico gaaps and also It worked
thanks
This is muy video for fix error 70 TWRP
Link:http://www.dailymotion.com/video/x3sit55
Thanks a lot
It won't increase the size,
javiblader17 said:
Hi, today I'm bringing you a fix for the error 70 that will come up after installing google apps in TWRP because of system partition space problems.
You will have to follow this steps:
- Go to the recovery menu and do a factory reset.
- Search the ROM and install it.
- (This is a very important step for it to work). Go to TWRP recovery and select wipe.
- Then go to Advanced Wipe.
- Once you are there, select System partition and click repair or change file system.
- Some options will come up, and select Resize File System.
- Once you have followed all these steps you can nos install all google apps without problem.
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!
Credits: @javiblader17 (Ak as JAVIX)
Click to expand...
Click to collapse
thnx . it worked now ...
thanku very much
Doesn't work for me, trying to update this phone for my girl. Followed your instructions, and the video. Still insufficient storage...
Hello
@javiblader17
I am using Xiaomi Redmi 1s (Armani) on Ressurection Remix.
When i am trying to install Mokee Rom (Marshmallow) the gapps (Pico version) fails saying error code 70.
I tried you method too..i get 31 mb left in the system partition after flashing just the mokee rom..Resizing doesn't work...plz help!!
nimesh.batra93 said:
@javiblader17
I am using Xiaomi Redmi 1s (Armani) on Ressurection Remix.
When i am trying to install Mokee Rom (Marshmallow) the gapps (Pico version) fails saying error code 70.
I tried you method too..i get 31 mb left in the system partition after flashing just the mokee rom..Resizing doesn't work...plz help!!
Click to expand...
Click to collapse
Even i am getting same problem installed Mokee and now cant even install pico gapps. error 70 tried the instructions in the video but no solution please help.
pkgoyal said:
Even i am getting same problem installed Mokee and now cant even install pico gapps. error 70 tried the instructions in the video but no solution please help.
Click to expand...
Click to collapse
i am searching for the solution..i will update this thread if i find one..
there is a way to increase system partition but its too complicated..
nimesh.batra93 said:
i am searching for the solution..i will update this thread if i find one..
there is a way to increase system partition but its too complicated..
Click to expand...
Click to collapse
Hi i have installed the latest nightly build of Mokee and Gapps Pico and it worked. Only the issue is batter is draining faster because of media server. downloaded the mediaserver killer app and it worked
Installed nightly today only..have you tried updating via OTA zip file?
Edit: it doesn't work!
nimesh.batra93 said:
Installed nightly today only..have you tried updating via OTA zip file?
Edit: it doesn't work!
Click to expand...
Click to collapse
installed mokee Marshmallow MK60.1-armani-160726-RELEASE and can't install gapps (redmi 1s 31MB free space)... it seems the developer didn't tested it before release.... Or we don't know how they can install it on their device LOL
joe200 said:
installed mokee Marshmallow MK60.1-armani-160726-RELEASE and can't install gapps (redmi 1s 31MB free space)... it seems the developer didn't tested it before release.... Or we don't know how they can install it on their device LOL
Click to expand...
Click to collapse
Thats what i was thinking too..we have the same device..same fioe to download.. but only few came up with this issue..
Too confused about it...eager to know the solution too
@javiblader17: thank you so much!! I did not know which way to turn, many thanks!
joe200 said:
installed mokee Marshmallow MK60.1-armani-160726-RELEASE and can't install gapps (redmi 1s 31MB free space)... it seems the developer didn't tested it before release.... Or we don't know how they can install it on their device LOL
Click to expand...
Click to collapse
I repartitioned System, Cache, Use data..increased system partition..the thing is you have to use twrp 2.8.7.0
http://en.miui.com/forum.php?mod=viewthread&tid=183258&extra=page=1&page=1&mobile=2
javiblader17 said:
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!:good:
Credits: @javiblader17 (Ak as JAVIX)
Click to expand...
Click to collapse
[/QUOTE]
Hi i have really n issue to get the Problem solved.
When i try to resize my system memory nothing changes -.-' ist there another way to change it??

Android 6 for LG-P712?

Hello, community! I was wondering if there's any Android 6 rom for LG Optimus L7 II (P712). I was told that CyanogenMod supports through CM13 a lot of LG devices but P712. But I decided to give it a shot anyway and I will share my experience with you.
I took the risk yesterday and I installed CM13 on my cel phone. The installation process was perfect (I used ClockworkMod Recovery), I also installed Gapps perfectly. I rebooted my device and it loaded and updated all the apps (it took like 10 minutes). After that, I had to setup my wifi network, google account, etc. Everything was good so far, but then, when the menues loaded my camera and radio fm weren't shown. The rest of the apps were right there and it recognized my wifi and mobile service provider like a charm (I called and texted myself from another phone). But... after a couple of minutes a pop-up started to show up saying "Unfortunately, Android keyboard (AOSP) has stopped" and since there, it was a nightmare haha. I couldn't access to my keyboard at all. I understand it's an issue with CyanogenMod and they are trying to fix it.
But after that situation, I decided to flash my device using "Flash Tools 2014" and Android 4.4. If any of you know about another rom with android 6, please let me know. Thanks in advance!
What gapps was used,and which cm13 build?Seems P712 is all like my P713,and on mine i got no lags(excepting camera app,just needs to install another camera and delete stock one).
DS_katauri said:
What gapps was used,and which cm13 build?Seems P712 is all like my P713,and on mine i got no lags(excepting camera app,just needs to install another camera and delete stock one).
Click to expand...
Click to collapse
Hi DS_katauri, thanks for your reply. About gapps, I tried to install different packages (mini, full, nano, stock), I downloaded them from opengapps. But it seems many people are reporting issues like the one I had. Btw, the rom I used was the "cm-13.0-20160330-UNOFFICIAL-vee7-RC2" (I'm a new user so I can't attach links... I downloaded it from androidfilehost, the user who uploaded it has useful things there). Thanks again, for your reply!!
dafaher said:
the rom I used was the "cm-13.0-20160330-UNOFFICIAL-vee7-RC2" !
Click to expand...
Click to collapse
Yep,Neutrondev made a lot of pretty things for our LG.
About ROM,try this one(latest build from Weritos) ,use version for 713 and gapps provided.IDK will CWM work,if no use Neutrondev's TWRP 3.020.Also,gapps should be installed after ROM but before 1st start.Lags are - built-in camera(use snap hdr and delete stock camera and gallery via root),wifi(sometimes connects only manual),no function on qmemo button(not critical at all)...And a specific feature - no internal card only SDcard I'm using it now(actually writing from it).Only three apps make me angry,katemobile(russian vk.com social network alternative client) - can stuck phone(idk why),viber v5x or v6x(both can FC in unknown reason,v4x all okay),and Opera4android(chinese idiots forget the "clean cache" button).
Oh,and launcher,Nova still remains the best.
Good luck and don't forget to backup your current ROM to SD.
Hi DS_katauri, thanks for your reply and all the info you shared with me. Unfortunately, it didn't work on my smartphone. Yesterday, I installed the rom and gapps by Weritos but the camera didn't work at all, it kept asking me for my sd-card (even after I formatted it). For the same reason, I couldn't download photos, take screenshots or anything. And I couldn't install whatsapp because it wasn't compatible with my device anymore, so I had to give up. Thanks anyway for all your help!!
dafaher said:
Hi DS_katauri, thanks for your reply and all the info you shared with me. Unfortunately, it didn't work on my smartphone. Yesterday, I installed the rom and gapps by Weritos but the camera didn't work at all, it kept asking me for my sd-card (even after I formatted it). For the same reason, I couldn't download photos, take screenshots or anything. And I couldn't install whatsapp because it wasn't compatible with my device anymore, so I had to give up. Thanks anyway for all your help!!
Click to expand...
Click to collapse
I told U to try snap camera,then play with settings to allow writing on sd(this stuff makes me mad too)Also,opencamera and first version of CyanogenCamera should work too.And,whatsapp,install it not from market.
Will look on new release of Weritos CM13 soon,probably it will help

[ROM][Android 7.1.1]Unofficial Okeys Builds[LineageOS 14.1][OMS7]

Heyo, guys. I wanna show u my own ROM based on LineageOS 14.1.
Flash it as u flash another ROMs:
Wipe System, data, caches
Flash ROM
Flash Gapps
Flash SuperSu if u want
For update just do dirty flash.
Hope that u'll like this ROM.
Download link:
AFH
Big thanks to @romilparh who was the first man who helped me with beginning things.
Thanks to @jhalayashraj who taught me some things
Thanks to @amardeep434 who also helped me a lot
Thanks to @danieldmm who also helped me with a lot of things
Also thanks to @TechExhibeo my sensei who can help with ton of problems and advise smth
And thanks @jgcaap for some interesting things on github.
LineageOS
Kernel
Device
Have a good use and thanks
umm.. First?
EDIT: Hey Oleg, nice to see your CM. Will download asap.
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
thank u very much for this awesome rom.
Wow this ROM is awesome! I just saw LineageOS 14.1 for the OnePlus One yesterday. No bugs so far, It seems really stable and a great and probably the best daily driver ROM.
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
i'm not facing any problem with AdAway and viper in 20170109 build.
NeolWhyt said:
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
Click to expand...
Click to collapse
Probably u're doing smth wrong...
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
Doesn't have any problem. All is ok.
Okeys said:
Doesn't have any problem. All is ok.
Click to expand...
Click to collapse
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Sent from my A0001 using Tapatalk
nolsen311 said:
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Click to expand...
Click to collapse
Viper is still included. Just change SELinux mode. I'll change on needed later.
Have a good use
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
f2sf it's supported?
hyper_davide said:
f2sf it's supported?
Click to expand...
Click to collapse
Now not.
ppp99 said:
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
Click to expand...
Click to collapse
All in ext4?
Okeys said:
All in ext4?
Click to expand...
Click to collapse
Just checked, YES.
https://www.androidfilehost.com/?w=files&flid=132556
Thanks so much Okeys! this is the best ROM I could find so far, it works so perfectly!!
Summary of my attempts:
(1)I tried "lineage-14.1-20170130-nightly-bacon-signed.zip" from lineageos
* lower kernel: 3.4.112
* not support system root, need install supersu.
* System APP: "SoundRecorder" and "Screencast" were merged and replaced with "Recorder", I don't like the new "Recorder", the recorder file is much bigger than "SoundRecorder"
(2)I tried "RR-N-v5.8.1-20170131-bacon-Official.zip" from remix
* Same as lineage above
* Support system root option, not need supersu
(3)lineage-14.1-20170126-Okeys-bacon.zip
* new kernel: 3.4.113
* not support system root, need install supersu.
* keep the original "SoundRecorder" and "Screencast"
* The only problem I met is "Left Wipe" doesn't switch to "Google" with Pixel Launcher for Andriod 7.1, but I find a solution and fixed it.
** see my post: https://forum.xda-developers.com/oneplus-one/help/fix-left-wipe-doesnt-switch-to-google-t3549497
Please change to coloros blobs dude
20170202 Bacon Gesture Settings
lineage-14.1-20170202-Okeys-bacon flashed a few minutes ago. Noticed that the Gestures settings no longer allows control over music and camera gestures. They are on by default, and I guess can no longer be turned off.
Hope this helps,
E.

There is an internal problem in your device. Please contact your manufacturer.

Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
MyNameIsRage said:
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
Click to expand...
Click to collapse
Umm okay, so what should I do now? By the way, thanks...
Shoury_Jain55 said:
Umm okay, so what should I do now? By the way, thanks...
Click to expand...
Click to collapse
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Wow. Thanks, I would definitely try those...
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Shoury_Jain55 said:
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Click to expand...
Click to collapse
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
greenys' said:
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
Click to expand...
Click to collapse
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
I would say get Orangefox or Redwolf recovery if you dont have them already. Try flashing any rom and see if your problem persists,if not flash magisk and custom kernels. With the process of elimination you should know the source of the problem which i think is francokernel as it was mentioned.
greenys' said:
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
Click to expand...
Click to collapse
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help! ?
Shoury_Jain55 said:
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help!
Click to expand...
Click to collapse
Oh, well. Perhaps you're right. I do this every week and works. I'm sorry I couldn't help you.
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
Wrong forum.
Go to DotOs forum, and ask your question.
Mybe your rom not compatible for mido.
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Probably Cpu throttling service asks for increase in cpu frequency due to the requirement , but when the cpu frequency is scaled up high , but due to some internal problem (temperature sensor failure or faulty processor etc...) the temperature detected is too high that the phone reboots.
TBH I have no idea about how android devices work but this happens on PS4 due to burnt capacitors , this can be fixed sometimes.
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
rc chanu said:
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
Click to expand...
Click to collapse
Thank you bro, works for me.
Very nice!!!

Categories

Resources