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!!!
Related
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.
XDA:DevDB Information
[ROM][7.1.1][Unofficially | LineageOS 14.1 For Huawei Ascend G760], ROM for the Huawei Ascend G7
very very thanks for:
dianlujitao
desalesouche
and others
Contributors
mparus
ROM OS Version: 7.x Nougat
Manifest: https://github.com/mparus/g760_lineageos-14.1
Downloads: https://forum.xda-developers.com/devdb/project/?id=19186#downloads
Mirror: https://androidfilehost.com/user/?w=settings-dev-files&flid=118309
Latest:
Check downloads page.
Previous: https://forum.xda-developers.com/devdb/project/dl/?id=23171 fix wifi reboot problem, fix move to sdcard apps problem, latest LOS commits
https://forum.xda-developers.com/devdb/project/dl/?id=23097 remove Gello browser - more space on /system partition, latest LOS commits, some wifi modifications
https://forum.xda-developers.com/devdb/project/dl/?id=23064 edit2: Please test the rom, maybe my tests were wrong
edit: this build is bad, random reboots often
disable CMUpdate app, update prima wifi driver in kernel (maybe fix random reboot after enable/disable airplane mode), latest LOS updates, please delete /data/misc/wifi/WCNSS_qcom_cfg.ini and /data/misc/wifi/WCNSS_qcom_wlan_cal.bin files or clean install recommended
https://forum.xda-developers.com/devdb/project/dl/?id=22978 fix restart to recovery and bootloader, latest commit from LineageOS
https://forum.xda-developers.com/devdb/project/dl/?id=22956
for root use: https://download.lineageos.org/extras (arm version)
stable twrp: https://www.androidfilehost.com/?fid=24421527759884484
new beta twrp: https://www.androidfilehost.com/?fid=529152257862699744
small google apps: https://github.com/opengapps/opengapps/wiki/Pico-Package
Issues: no gyroscope and USB otg
Version Information
Status: Stable
Created 2017-02-01
Last Updated 2018-02-18
Reserved
Having just issue with gyroscope not working properly so far everything else all good can't use file manager as won't let me access SD card so use root browser and no problem whatsoever
Thank you for your work!
So to continue from the other thread.
Seems large apps can't be moved, while small apps can.
I have 30gb free on the sdcard, but Final Fantasy 7 or 9 can't be moved there, giving the error "insufficient storage". However big files can be moved between location manually.
(Final Fantasy 7 doesn't run at all, and just instantly crashes when open. That game was always sensitive to where it was stored. It did work on your cm13, but not very well, its a bad port of the pc version I think
*Edit that, updated just got pushed by play store. What's changed state it doesn't work in 7.x Android).
Again, I am providing feedback as things happen. Not particularly asking for a solution, although maybe anything I come across can indicate issues to help with development.
Ooh another thing. In the expanded notification panel, pressing the pencil icon in order to rearrange the icon causes the phone to freeze for a minute or two, then brings up the lockscreen. Seems like SystemUI having issues but there is no error messages indicating that (but its that kind of behaviour from older Android versions that makes it seem like the case). It does not happen every time, but happens more than actually opening the rearrange page happens.
Sent from my Huawei Ascend G7 using XDA Labs
@mparus
Please always keep the first post up to date with the link for Latest Stable ROM, Latest Nightly ROM, Known Issues, Latest Recovery, Latest Kernel, etc.
Previous topic was not suitable for a new member or even an old member that didn't follow the topic for couple of days.
SD card working perfect on my G7-L01 in the 131 build.
Everything (so far) works great. Great ROM ?
Does anybody have mtp connection problem on latest build lieage rom ??
wish gapp i have to install ? lineage gapp or whatever??
Sent from my HUAWEI G760-L01 using Tapatalk
Sparko612 said:
Does anybody have mtp connection problem on latest build lieage rom ??
Click to expand...
Click to collapse
I got no problems (SD card not formatted as internal).
Although in some earlier builds when I formatted the SD card as internal storage I couldn't access internal memory from my PC.
So specify your problem a bit please?
NAJI23 said:
wish gapp i have to install ? lineage gapp or whatever??
Sent from my HUAWEI G760-L01 using Tapatalk
Click to expand...
Click to collapse
GApps 7.1 Arm.
NAJI23 said:
wish gapp i have to install ? lineage gapp or whatever??
Click to expand...
Click to collapse
Install 7.1 GAPPS on the ARM platform.
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Sparko612 said:
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Click to expand...
Click to collapse
Plug your phone to your PC. Then when it connects to the PC you'll have to open your status bar and see a notification saying "USB Charging this device". Click on it and you'll get a small menu with 4 options. Click on " Transfer files" (which is the second option) and then your phone will reconnect with your PC automatically and you'll be able to access the internal and SD card data from your PC.
And a feature has been added to Android ever since the 6.0 version where the users can configure the SD card to be able use it as Internal Storage. You can find that in the settings of your device?
Sparko612 said:
Well my SD card is showing on latest ROM but upon connection to PC it doesn't recognise internal or SD only adb connects and not sure what to do now ??
I'm still pretty new to this side of android what you mean SD card formatted as internal sorry for sounding so stupid
Click to expand...
Click to collapse
This is the notification
kamilb365 said:
This is the notification
Click to expand...
Click to collapse
Yes I get the notification but when I select transfer files nothing comes up and don't really know what else to do
How about lis3dh sensor devices? - working properly or have problems with gryro or screen rotation?
Sparko612 said:
Yes I get the notification but when I select transfer files nothing comes up and don't really know what else to do
Click to expand...
Click to collapse
Well what build are you running right now?
And did you clean or dirty install it?
kamilb365 said:
Well what build are you running right now?
And did you clean or dirty install it?
Click to expand...
Click to collapse
Clean install on latest lineage ROM build 131
Sparko612 said:
Clean install on latest lineage ROM build 131
Click to expand...
Click to collapse
This might be able to fix it. Go to developer options, scroll down to "select USB configuration" and change whatever setting you have to MTP. You might wanna switch modes a few times and then connect to PC with MTP active..
The bug has been active since cm13 in some cases and I personally never had the issue so I can't go into full depth of this.
kamilb365 said:
This might be able to fix it. Go to developer options, scroll down to "select USB configuration" and change whatever setting you have to MTP. You might wanna switch modes a few times and then connect to PC with MTP active..
The bug has been active since cm13 in some cases and I personally never had the issue so I can't go into full depth of this.
Click to expand...
Click to collapse
Gonna re download it tomorrow might be bad download anyway ive restored back to stock for now will look into it thank you all your tips
Edit: my model of device is G7 - L01 not sure if that may be the problem why im getting all this atm
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?
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
sometimes FC in camera
LineageOS Builds
3. 20180719: cleanup, update hwui\dalvik settings, add bt codecs (aptx, aptx-HD, ldac) https://drive.google.com/file/d/1EDIZPh5SOa36nUErAvFBREzRAhZCtHGa/view?usp=sharing
2. 20180713: https://drive.google.com/file/d/1sItey9421ml2QSyTNQKn5s1frvjASdCc/view?usp=sharing
1. 20180712: https://drive.google.com/file/d/1FWoBISUpbPozdlqkuJxBh7fdksEg-yP9/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 8.1
Variant: any
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Finally, I had time to check whether it's possible to build a 64bit firmware on the exynos7870. Yes, we have 64bit kernel, but all stock firmwares were 32bit, as result I need a lot of missed 64bit proprietary files.
This is fully 64bit firmware, missed files from a5'17 (it's on exynos7880) - gralloc, gps, ril, gles (mali).
Only own audio\camera still 32bit, but in any case it's working great in 64bit firmware.
I wrote own sensors HAL, because it's very specific for each device, it's still buggy, i'm continue work on it.
Right now I need understand - do we need 64bit at all? I don't see any huge improves.
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
buggy sensors (accelerator and light)
LineageOS Builds
1. 20180712: https://drive.google.com/file/d/1FWoBISUpbPozdlqkuJxBh7fdksEg-yP9/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 8.1
Variant: any
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Click to expand...
Click to collapse
Congrats! I am test it asap!:good::good::good:
new version.
now I can say - it's stable.
sensors - done (back to stock sensors.universal7870.so with prebuild 32bit service for sensors)
flip - done
it's still sometimes fc on camera - I'll check it later
I can confirm it works on SM-T580 (WiFi only) as well. Everything seems to work fine; buttons, WiFi + BT, camera, audio, video (youtube), sensors, smart cover etc.
OpenGApps 8.1 ARM64 installed with no errors.
The only thing I noticed is during first boot screen it says in the top-left corner in red text: 'Kernel is not seandroid enforcing'. Maybe this is on SM-T585 as well.
On the SM-T580 you get unusable sim-card icon in the notification bar and some other places, but that is to be expected.
sanchaz12 said:
I can confirm it works on SM-T580 (WiFi only) as well. Everything seems to work fine; buttons, WiFi + BT, camera, audio, video (youtube), sensors, smart cover etc.
OpenGApps 8.1 ARM64 installed with no errors.
The only thing I noticed is during first boot screen it says in the top-left corner in red text: 'Kernel is not seandroid enforcing'. Maybe this is on SM-T585 as well.
On the SM-T580 you get unusable sim-card icon in the notification bar and some other places, but that is to be expected.
Click to expand...
Click to collapse
Just installing on T585 now, I've flashed the rom and gapps fine.
Problem I have is first there was no keyboard, and now I can't sign in to Google account
It says checking and then screen goes black.
I've wiped cache and davlik but still won't work
Any help would be appreciated
Also, what's a full wipe in twrp?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
Just installing on T585 now, I've flashed the rom and gapps fine.
Problem I have is first there was no keyboard, and now I can't sign in to Google account
It says checking and then screen goes black.
I've wiped cache and davlik but still won't work
Any help would be appreciated
Also, what's a full wipe in twrp?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Those problems may be related to improper wipe, no worries.
Full wipe means in TWRP you go to 'Wipe' -> 'Advanced Wipe' -> Select all partitions except 'Micro SD card' and 'USB OTG'
In my case (SM-T580) that would be;
- Dalvik / ART cache
- System
- Data
- Internal Storage (Optional, but recommended to wipe)
- Cache
Don't forget to first make a backup via TWRP of the 'EFS' partition (on sd-card or USB-stick via OTG cable), just in case the SIM-card functions stop working due to lost IMEI.
Also, some issues may be related to the device still working on stuff when it shows the welcome screen after flashing. In general you should leave the device for around 5 minutes before doing anything after flashing and first boot to let everything finish properly.
sanchaz12 said:
Those problems may be related to improper wipe, no worries.
Full wipe means in TWRP you go to 'Wipe' -> 'Advanced Wipe' -> Select all partitions except 'Micro SD card' and 'USB OTG'
In my case (SM-T580) that would be;
- Dalvik / ART cache
- System
- Data
- Internal Storage (Optional, but recommended to wipe)
- Cache
Don't forget to first make a backup via TWRP of the 'EFS' partition (on sd-card or USB-stick via OTG cable), just in case the SIM-card functions stop working due to lost IMEI.
Also, some issues may be related to the device still working on stuff when it shows the welcome screen after flashing. In general you should leave the device for around 5 minutes before doing anything after flashing and first boot to let everything finish properly.
Click to expand...
Click to collapse
Thanks for that info, that worked brilliant, now fully working.
Thanks sanchaz12
Sent from my SM-T585 using Tapatalk
Rom is running smoothly, only problem I found so far is the camera app, it loads but the soft button only shows a half. It's like the screen is not big enough.
Is there a fix for this?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
Rom is running smoothly, only problem I found so far is the camera app, it loads but the soft button only shows a half. It's like the screen is not big enough.
Is there a fix for this?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Install another good camera. For example i am using Camera FV-5.
It's honestly WORRYING the fact the tablet runs at 10FPS when scrolling through the notification bar. Can't you disable the notification bar background alpha @Valera1978?
Hi. Thanks a lot @Valera1978 . Good job. Even GPS work now.:good:
Great work. I'm new there, i've just buy a T580 and watch your thread for 1 day.
Edit : "Install custom recovery - use my twrp" Where can i find it ? Thanks.
Steelskinz said:
Edit : "Install custom recovery - use my twrp" Where can i find it ? Thanks.
Click to expand...
Click to collapse
This for T585 only. You need install TWRP for T580 official or by @followmsi better from his RR threads.
repey6 said:
Hi. Thanks a lot @Valera1978 . Good job. Even GPS work now.:good:
Click to expand...
Click to collapse
Great! I can confirm that gps gets a fix in gps test app, just as can be seen in the screenshot. Also open camera app can take photos on both cameras and video on back camera. I couldn't record video with front camera, but that doesn't bother me anyway.
repey6 said:
This for T585 only. You need install TWRP for T580 official or by @followmsi better from his RR threads.
Click to expand...
Click to collapse
OK thanks.
Is this rom still OK for T580 ? I read someone flashed it already. Can anyone confirm ? Thanks.
I can't access the SD card in this ROM, maybe there are some leftover files from the previous ROM, that prevent the tablet from accessing it? Anybody has some advice if it's possible to fix that?
mnd123 said:
I can't access the SD card in this ROM, maybe there are some leftover files from the previous ROM, that prevent the tablet from accessing it? Anybody has some advice if it's possible to fix that?
Click to expand...
Click to collapse
External SD card?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
External SD card?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes
mnd123 said:
Yes
Click to expand...
Click to collapse
Did you format it as internal storage on the last romyou had installed, if so it possibly will not work unless it's reformatted on the currently installed rom.
Does it actually show up in file manager?
Sent from my ONEPLUS A5010 using Tapatalk
HAVOC 3.0 ROM V2 2019-12-06
Project ended.
This is BETA version, USE STABLE crDroid or GoogleDroid ROMs.
Your warranty is now void.
There's no guarantee, don't use it if you don't know what you're doing!
Android quota removed. (Easy back 7.x-9.x ROMs)
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery) My TWRP: LINK
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy SD)
Flash Google Apps package (Optional) LINK
Flash Magisk Root (Optional) LINK
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 40 sec to 1 minutes.
Boot time 30 sec.
There are many tiny, unpleasant bugs in Havoc system, NOT recommended for daily use, maybe just for fanatics.
DOWNLOAD V2 ROMDon't need wipe data if upgrade previous Havoc 3.
NEW: FM radio fixer LINK (If not working FM radio, install this fixer in TWRP)
NEW: dt2w fixed : LINK (Install in TWRP.)
V2 Changelog:
Power off (offline) charging bug fixed
Some camera bug fixed
Many system bug fixed
Energy consumption is very good
The Android system seems stable and fast (Havoc Os not so much )
Know bugs: - no double touch wake up (?)
- FM radio
- power off charge
Update: I found some permission issues.
I'm trying to fix it.
The camera app does not save images to the SD card...
Gallery Go does not handle SD card properly...
They don't even ask for permission...
Workaround: USE INTERNAL STORAGE for photography, and sometimes move images to SD.
*
Screenshots: LINK
ROM source xda: LINK
Havoc-OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.x
ROM info: mido OFFICIAL port, Q10 system_root partition
Created 2019-11-26 V0 version
Last Updated 2019-12-06 to V2 version
It looks like I have solved two serious problems.
(dex2oat didn't work and neither did ashmem)
The system boot is twice as fast, etc.
I soon publish the new ROM.
Upgrade Out. More stable, fast.
Reboots into fastboot mode
My device automatically reboots into fastboot mode after I flashed this.
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
I am using pixel experience ROM currently. When I flashed this my device end up in bootloop. Do I have to be in miui for installing this..??
Redminote5a8 said:
My device automatically reboots into fastboot mode after I flashed this.
I am using pixel experience ROM currently. When I flashed this my device end up in bootloop. Do I have to be in miui for installing this..??
Click to expand...
Click to collapse
Thank you your response, ROM V1 fixed, downloadable.
(The system partition on my phone was slightly disintegrated, I had to fix it.)
Pixel E. ROM is on 4PDA, downloadable.
Use a suitable TWRP, pls.
If anybody have downloaded V1, delete it because it is defective.
ROM named *V1fix.img works.
Sorry. I apologize for the inconvenience.
Hahaha, the camera bug very funny: LINK
The camera app save images to folder: sdcard - /Android/data/org.lineageos.snap/files
Thnx ****ing org.lineageos.snap app, and i suck...
offline charging bug
Hafitz Setya said:
offline charging bug
Click to expand...
Click to collapse
Thank you your responde, i know this bug, i will deal with it, i hope soon.
HAVOC 3.0 ROM V2 2019-12-06
V2 out.
I ended this job for the time being here, I don't got much feedback and thnx (respect the exceptions), and a lot of time goes with it. Sry, bye.
that is a great work
hey szanalmas we all on ugglite telegram appreciate your hard and excellent work for bringing stable Q to ugglite
thanks is few for you on Xda beacuse almost ugglite useres are on telegram groupe
they all ask you to join the group on telegram
:good::good::good::good:
szanalmas said:
I ended this job for the time being here, I don't got much feedback and thnx (respect the exceptions), and a lot of time goes with it. Sry, bye.
Click to expand...
Click to collapse
i told u to use telegram, people most activates in therre they report bug in telegram
FM radio fixer out. LINK
Dt2w fixer placed out.
According to Hafitz Setya, he also works with the my dt2w fixer on Havoc OS. Use it gladly: LINK (Install in TWRP.)
Is this rom work in ugg?
szanalmas said:
Dt2w fixer placed out.
According to Hafitz Setya, he also works with the my dt2w fixer on Havoc OS. Use it gladly: LINK (Install in TWRP.)
Click to expand...
Click to collapse
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Manager_of_Gulag said:
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Click to expand...
Click to collapse
Try execute 10goodix & turn on emulate init.d in kernel adiutor and reboot and turn off this
Sent from my Xiaomi Redmi Note 5A using XDA Labs
Manager_of_Gulag said:
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Click to expand...
Click to collapse
1. workaround dt2w: download Ravenge OS (TWRP save) and restore ONLY VENDOR. I integrated dt2w to vendor, but only for PE and subsequent ROMs.
2. workaround (full ROM installer): change the vendor.transfer.list and vendor.new.dat.br files from PixelE to HavocOS (or Arrows, or crDroid) in to the installer zip file. After no need patch for dt2w. Only copy two files to ROM installer zip file.
If you want dt2w, you have to disable the double tap on ambient display because two identical functions cannot be interpreted at the same time.
Dt2w will be good in every new ROM.
I have already stated that Official ROM development is chaotic.
The Havoc bug to this day:
- no flashing LED for missed calls
- Doesn't work with two buttons navigation back sweeping
- there is a problem with the bluetooth call
- applications are chaotic and inconsistent, with each developer trying their own solutions
- etc
- developers do not receive meaningful feedback
The situation is similar for all AOSP-based ROMs, which may be due to the lack of an official Lineage 17.
Google ****ed up sd card permissions.
I don't know when a stable AOSP ROM will be available, just wait now...
Hey.
After flashing the system asks for a password ??
What the hell?
Repixel said:
Hey.
After flashing the system asks for a password ??
What the hell?
Click to expand...
Click to collapse
1. If your phone data was encrypted, you may need to format the data partition. Save all your data first.
2. If a quota was applied to the data partition, it must be removed or formatted.
To remove a quota from TWRP:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
(If you then install a ROM that uses a quota, you will need to uninstall it again to use the quota-free ROM.)
3. Or, put the previous ROM from your backup on your phone and keep using it.