Related
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1
I just received a used Samsung Galaxy Tab Pro 8.4 (SM-T320) - and discovered (not known to me before purchase) it is Rooted.
When I went to do an Update via standard Settings>about Device - it refused returning tablet modified.
also it had the App SuperSU (free) installed) which asked about permission on a couple of Apps I used.
I have absolutely no experience of Rooted tablets,
and currently have no idea how the tablet was rooted, and what with.
So I am seeking your patience and some advice about this, please.
Is there a way to return to the Stock installation?
If so, how to I check that this is possible?
Or should I keep the Root?
If so, how do I update the tablet?
eg: how do I check what, or if any, custom ROM has been installed?
or
which custom ROM do people advise I install?
Thanks for any advice.
Vincent
Just back up your valuable data and storage contents and flash stock via Odin. And I believe at this time point the updates are not of much importance, so if you're on KitKat you might as well ignore that if you can't spare time for backups.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
Just back up your valuable data and storage contents and flash stock via Odin. And I believe at this time point the updates are not of much importance, so if you're on KitKat you might as well ignore that if you can't spare time for backups.
Thanks for the reply.
Funny that was starting to be my take too.
Either leave it rooted as is - since it really is just KitKat 4.4.2 - but with more ability.
Or later when the spirit moves perhaps upgrade via a custom rom.
Thank you.
Vincent
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@vincent. I have the same tablet as you and I prefer to run the latest OS which is Marshmallow. As you state you are already rooted so you might as well try out a custom ROM. I recommend Resurrection Remix ROM by Vasumit and the XDA thread can be found here. Latest update to ROM is here. You will also need to install gapps. I recommend Banks Dynamic Gapps 6.X.X found here. Give it a try, I'm sure you will like it. ROM is buttery smooth and Vasumit updates it often. :good::good:
DowntownRDB said:
@vincent. I have the same tablet as you and I prefer to run the latest OS which is Marshmallow. As you state you are already rooted so you might as well try out a custom ROM. I recommend Resurrection Remix ROM by Vasumit and the XDA thread can be found here. Latest update to ROM is here. You will also need to install gapps. I recommend Banks Dynamic Gapps 6.X.X found here. Give it a try, I'm sure you will like it. ROM is buttery smooth and Vasumit updates it often. :good::good:
Click to expand...
Click to collapse
DowntownRDB
Thank you so much for your encouragement and suggestion.
Even though I have used Android on tablets and phones for years -
I am still a n00b when it comes to Root and Custom ROMs
I have heard of the more famous ROMs like CyanogenMod etc -
what makes Resurrection Remix ROM by Vasumit better than CyanogenMod
in terms of features and/or support please?
How easy (or not) are custom ROMs to undo?
Many thanks,
UnknownVT said:
I have heard of the more famous ROMs like CyanogenMod etc -
what makes Resurrection Remix ROM by Vasumit better than CyanogenMod
in terms of features and/or support please?
Click to expand...
Click to collapse
Personal opinion below: most AOSP-based ROMs have equal or slightly better support than CM because the team behind them is much smaller, but they might die out one day because of the same reason. CM maintains a huge number of devices and is the basis of many, so it's not likely to disappear soon. Also, CM is usually among the quickest to get to a new Android version while others usually sync from CM and start from there.
As of features, others are guaranteed to have more than CM. CM doesn't like adding features these days.
How easy (or not) are custom ROMs to undo?
Click to expand...
Click to collapse
Do: Flash TWRP, make a full backup of your stock ROM, full wipe and flash the new one.
Undo: Full wipe and restore the old backup, or if you decide you don't want your data, use Odin.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
Personal opinion below: most AOSP-based ROMs have equal or slightly better support than CM because the team behind them is much smaller, but they might die out one day because of the same reason. CM maintains a huge number of devices and is the basis of many, so it's not likely to disappear soon. Also, CM is usually among the quickest to get to a new Android version while others usually sync from CM and start from there.
As of features, others are guaranteed to have more than CM. CM doesn't like adding features these days.
Do: Flash TWRP, make a full backup of your stock ROM, full wipe and flash the new one.
Undo: Full wipe and restore the old backup, or if you decide you don't want your data, use Odin.
Click to expand...
Click to collapse
Thank you very much for the very helpful reply -
this was about as good as I was hoping for -
really appreciate all the help I am getting here, thank you.
It will take a bit of time for me to get my head around the information - as it is all new to me -
and I want to proceed with care/caution so I don't end up bricking my tablet.
Gratefully and thanks,
UnknownVT said:
Thank you very much for the very helpful reply -
this was about as good as I was hoping for -
really appreciate all the help I am getting here, thank you.
It will take a bit of time for me to get my head around the information - as it is all new to me -
and I want to proceed with care/caution so I don't end up bricking my tablet.
Gratefully and thanks,
Click to expand...
Click to collapse
Hey!
you could look at it this way, most of the people here have a hard time just ulocking the device and rooting it, not that yours is already done, might as well right. along with the proper research, your device could be one hundred times better, the stock OS of the tablet isn't that good (lets face it.) and with the current technology, it will have a hard time keeping up because the OS for this device is not that efficient (personal opinion). Anyways, it's still up to you to do it or not. Cyanogenmod has released the nightly version of Marshmallow 6.0 for this device. maybe you could check it out!! ^_^
kurogane_tw said:
Hey!
you could look at it this way, most of the people here have a hard time just ulocking the device and rooting it, not that yours is already done, might as well right. along with the proper research, your device could be one hundred times better, the stock OS of the tablet isn't that good (lets face it.) and with the current technology, it will have a hard time keeping up because the OS for this device is not that efficient (personal opinion). Anyways, it's still up to you to do it or not. Cyanogenmod has released the nightly version of Marshmallow 6.0 for this device. maybe you could check it out!! ^_^
Click to expand...
Click to collapse
Yes, thanks for the encouragement.
Seems ironic that I had done lots of look-sees (not quite research, but close) about rooting devices - and I actually now have one
(it was just unexpected on this Samsung Galaxy Tab Pro 8.4 (SM-T320)).
As you see I've decided to keep it rooted and am actively looking at which ROM to flash -
currently I am leaning toward the more conservative approach of doing the CM (CyanogenMod)
and rather than deciding between the snapshot CM-12.1 or the nightly CM-13.0....
perhaps I should just wait for a snapshot CM-13.0
(" and we’ll have a quality approved SNAPSHOT for CM13 sometime Jan." of course it is now Feb - so maybe soon?)
Thanks,
UnknownVT said:
perhaps I should just wait for a snapshot CM-13.0
(" and we’ll have a quality approved SNAPSHOT for CM13 sometime Jan." of course it is now Feb - so maybe soon?)
Click to expand...
Click to collapse
Don't wait for snapshots - they are just forked from nightlies at a certain timepoint and aren't more stable than nightlies. Just backup and flash a nightly, and if anything you feel unstable, restore the backup and/or wait for that to get resolved. I personally don't see anything disturbing aside from wonky external SD support (which is a universal bug across all 6.0+ ROMs).
P.S. The "Thanks" button is there - use it
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
AndyYan said:
Don't wait for snapshots - they are just forked from nightlies at a certain timepoint and aren't more stable than nightlies. Just backup and flash a nightly, and if anything you feel unstable, restore the backup and/or wait for that to get resolved. I personally don't see anything disturbing aside from wonky external SD support (which is a universal bug across all 6.0+ ROMs).
Click to expand...
Click to collapse
Thanks again, and thanks for pointing out the ext SD card issue with 6.0+ ROMs
Does this work?
How to Use SD Card as Internal Storage on Marshmallow ...
Thanks.
UnknownVT said:
Thanks again, and thanks for pointing out the ext SD card issue with 6.0+ ROMs
Does this work?
How to Use SD Card as Internal Storage on Marshmallow ...
Thanks.
Click to expand...
Click to collapse
The issue is mainly with how to use SD card as external storage (as on older Android versions), not with the new "adoptable storage" feature. That we don't have a definitive solution yet.
You might want to read through the last pages of the CM13 discussion thread in Development subforum if you're determined to get it working.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk
cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.
Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!
SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...
Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.
Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Man, you are the best! And what about sensors?
And where did you find this solution?
hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.
How to make this logs? i know nothing in programming (
CM-14.0 UNOFFICIAL for Find7 by Wuxianlin
This is only for chinese storage unification(havent test yet in other storage layout)
FLASH IN YOUR OWN RISK IM NOT RESPONSIBLE FOR YOU ALL GONNA DO...!!!!
Builds being update in the second post...
Chinese unification, nice tutorial made by @alexander Tashi -> here
This is for Find7a but work on Find7s to
This is for chinese storage partition(Only test in this layout), and i dont know if it work on other layouts like Stock/LVM/Coldbird, you all have to test it for yourselfs
The daily base work
GPS
WIFI
4G/LTE
COMPASS
and others...
BLUETOOTH can detect and connect but the sound is yet came out from the phone...
I have flash oppocamera work less the HDcamera
Flash the A.R.I.S.E. AUDITORY RESEARCH IN SOUND ENHANCEMENT work(havent test yet maxxaudio)
You can use has daily driver...
Ps.: since this use CM kernel is possible that you may have reboots... :\
New build:
cm-14.1-20161127-UNOFFICIAL-find7 / MIRROR
cm-14.1-20161201-UNOFFICIAL-find7
please correct link to chinese storage partition guide
and the mega links in initial post (they do not work!)
der_Kief said:
please correct link to chinese storage partition guide
and the mega links in initial post (they do not work!)
Click to expand...
Click to collapse
Working now....
Awesome! I'm trying
Ok so I tried this rom finally! Here's my feedback:
First of all I'm a bit confused why is this called cyanogenmod 14, because its not cm. It looks like the vanilla aosp from a one plus device or maybe nexus. It has no cm features.
Secondly like stated in the op this is indeed for chinese storage. I can confirm lvm does not work.
Stock gallery does not show all the picture folders. However quickpic from playstore works fine.
Music players can't detect songs on my sd card. But I can play them from file explorer.
I didn't test bluetooth for now.
Other than these things, this is really smooth and stable for an initial test build. So kudos to the dev for bringing N so quickly for our devices! You can use this as a daily driver
DemonDroid_97 said:
You can use this as a daily driver
Click to expand...
Click to collapse
you should be carefully with such a statement
DemonDroid_97 said:
...
First of all I'm a bit confused why is this called cyanogenmod 14, because its not cm. It looks like the vanilla aosp from a one plus device or maybe nexus. It has no cm features. ...
Click to expand...
Click to collapse
This this builds are made with cm kernel and little by little they start to have the CM features heheheheh
der_Kief said:
you should be carefully with such a statement
Click to expand...
Click to collapse
For me has daily driver or minimum requirements for use phone at least they need to have GPS/LTE/WIFI and that 3 thinks are working and im using for 3 days
New build is UP for download in the 2nd post
cm-14.0-20160905-UNOFFICIAL-find7.zip
EDIT: It seems the dev add camera, music player and audiofx to this build
Is supported new LCD?
Injected said:
This this builds are made with cm kernel and little by little they start to have the CM features heheheheh
Click to expand...
Click to collapse
A question about chinese unification: after installing the ROM, do I need to install the unified partition patch for CM based ROM's?
Thanks for your help.
javier.pc said:
A question about chinese unification: after installing the ROM, do I need to install the unified partition patch for CM based ROM's?
Thanks for your help.
Click to expand...
Click to collapse
NO, you dont need, beucase this rom already made for chinese partition
other than mega?
harsaad said:
other than mega?
Click to expand...
Click to collapse
I can try put google drive....
im from omni.. with LVM... this rom not supported LVM?
eureka9092000 said:
im from omni.. with LVM... this rom not supported LVM?
Click to expand...
Click to collapse
No.... This only for chinese storage partition
How can the phone be formatted for the chinese storage partition? I've tried to follow the guide however there are dead links for the tools required
mada360 said:
How can the phone be formatted for the chinese storage partition? I've tried to follow the guide however there are dead links for the tools required
Click to expand...
Click to collapse
All links working fine from here
http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
DemonDroid_97 said:
All links working fine from here
http://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
Click to expand...
Click to collapse
Looks like the Russian one is working for me, hopefully it doesn't stop mid download! Thanks for your help
Just to confirm process from RR with LVM would be;
1) Use tools to perform chinese unify (Should wipe entire device)
2) Flash TWRP
3) Flash the new CM14 Rom, gapps and all that good stuff
4) Profit???
Ok well I'm flashing the rom now and everything has gone through without issue! the tool only took about 2:50 for me.
For anyone trying to get English in twrp, second from bottom on the right and then select the globe icon at the top
Please, can someone explain the difference between chinese storage partition and LVM? Not technically, of course. I want to know about partitions and their sizes.
Thanks again.
javier.pc said:
Please, can someone explain the difference between chinese storage partition and LVM? Not technically, of course. I want to know about partitions and their sizes.
Thanks again.
Click to expand...
Click to collapse
From what I can tell the LVM method is a linux storage method that allows data to be stored in a varying sized partition by allowing on the fly resizing. The chinese method of dealing with the sotorage partition looks pretty much the same, if you look at the free app storage space it will be only around 100mb or less, but as you install more apps more space is allocated so it appears there is the entire device storage available.
I would assume the only difference would be in the way the Rom sees and interacts with the device storage. But on the most part there doesn't seem to be any real world issues, everything seems to work great and I wouldn't know it wasn't running on the LVM partition.
I recently purchased an tab S4 just an update from my previous Samsung tablet. I was wondering is there more ROMs for this tablet or ROMs currently in development? I noticed theres like 2 ROMs for this tablet. I have a note 8 and I'm currently running deluxerom on and it, and I really enjoy the tweaks and customization I'm able to do. I was looking for a same kind of feature for my tablet. Would greatly appreciate the answers I'm looking for. Thanks!
Mkami said:
I recently purchased an tab S4 just an update from my previous Samsung tablet. I was wondering is there more ROMs for this tablet or ROMs currently in development? I noticed theres like 2 ROMs for this tablet. I have a note 8 and I'm currently running deluxerom on and it, and I really enjoy the tweaks and customization I'm able to do. I was looking for a same kind of feature for my tablet. Would greatly appreciate the answers I'm looking for. Thanks!
Click to expand...
Click to collapse
Pretty much zero support. You can get a few 9.0 GSI ROMs to boot, but they all have issues. Mine has been sitting around since it was purchased while still using my old 2014 model.
veekay said:
Pretty much zero support. You can get a few 9.0 GSI ROMs to boot, but they all have issues. Mine has been sitting around since it was purchased while still using my old 2014 model.
Click to expand...
Click to collapse
Aww no way!? Really? I excitingly got this tablet cause of the features and thought perhaps there would be amazing ROMs for this particular tablet, but I guess not xD What are GSI ROMs? Also as a desperate attempt would other tablet ROMs work on this s4? Thanks mate!
Mkami said:
Aww no way!? Really? I excitingly got this tablet cause of the features and thought perhaps there would be amazing ROMs for this particular tablet, but I guess not xD What are GSI ROMs? Also as a desperate attempt would other tablet ROMs work on this s4? Thanks mate!
Click to expand...
Click to collapse
I had thought the same thing, but it seems the S3 is the last tablet to get real support.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Some of the ones for 9 will work, but most features won't work too well, if at all.
You might be able to get another rom to work, I know I had no luck. Even trying ones with similar hardware, they all failed to even flash since the booting numbers are different.
Kind of have to be satisfied with Samsung, half baked custom roms or sell the thing.
Mkami said:
Aww no way!? Really? I excitingly got this tablet cause of the features and thought perhaps there would be amazing ROMs for this particular tablet, but I guess not xD What are GSI ROMs? Also as a desperate attempt would other tablet ROMs work on this s4? Thanks mate!
Click to expand...
Click to collapse
First,download "Treble Check" app from playstore & read for your device...
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
(Some GSIs roms are not compatible with some devices!)
veekay said:
I had thought the same thing, but it seems the S3 is the last tablet to get real support.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Some of the ones for 9 will work, but most features won't work too well, if at all.
You might be able to get another rom to work, I know I had no luck. Even trying ones with similar hardware, they all failed to even flash since the booting numbers are different.
Kind of have to be satisfied with Samsung, half baked custom roms or sell the thing.
Click to expand...
Click to collapse
Hey Veekay I tried it and you're right unfortunately I came across the same issue as you brother
Now I'm stuck and I need help sorting my device out, was wondering if you knew this issue or could help?
When I got the stock firmware back and then when I flash TWRP with odin after going into TWRP I get 0mb as internal
so when I format and then go back into my load up the screen after SAMSUNG says "verification failed" and then reset
on the bottom. I tried other options as well. Without even wiping on TWRP the devices boots up into the setup wizard for the firmware fine
but after I wipe TWRP so I can get access to my internal drive my samsung boots into that verification reset screen. Got any clue as to how I can
resolve this issue? Thanks a bunch!
daitalos said:
First,download "Treble Check" app from playstore & read for your device...
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
(Some GSIs roms are not compatible with some devices!)
Click to expand...
Click to collapse
Hey! Thanks for your reply, will this work for PIE? I can't downgrade from PIE to OREO
and I don't know if GSI even works properly on my device
Mkami said:
Hey Veekay I tried it and you're right unfortunately I came across the same issue as you brother
Now I'm stuck and I need help sorting my device out, was wondering if you knew this issue or could help?
When I got the stock firmware back and then when I flash TWRP with odin after going into TWRP I get 0mb as internal
so when I format and then go back into my load up the screen after SAMSUNG says "verification failed" and then reset
on the bottom. I tried other options as well. Without even wiping on TWRP the devices boots up into the setup wizard for the firmware fine
but after I wipe TWRP so I can get access to my internal drive my samsung boots into that verification reset screen. Got any clue as to how I can
resolve this issue? Thanks a bunch!
Click to expand...
Click to collapse
Have you tried just reloading the latest stock firmware from scratch?
Yup, its unfortunate that there isn't much community support for this device. The Tab S4 is Project Treble supported and a few GSI ROMS do work. But as others have said they are unstable and not for use as a daily driver. We have a few discussion threads here talking about them.
veekay said:
Have you tried just reloading the latest stock firmware from scratch?
Click to expand...
Click to collapse
Would that work? If I did that I would still be able to download and install TWRP and have a root? Because of it being PIE
UndeadAnarchy said:
Yup, its unfortunate that there isn't much community support for this device. The Tab S4 is Project Treble supported and a few GSI ROMS do work. But as others have said they are unstable and not for use as a daily driver. We have a few discussion threads here talking about them.
Click to expand...
Click to collapse
I am going to do more research on these projects because I really wish there was more ROMs its quite an amazing tablet but the potential with the stock ROM lacks a lot
Mkami said:
Hey! Thanks for your reply, will this work for PIE? I can't downgrade from PIE to OREO
and I don't know if GSI even works properly on my device
Click to expand...
Click to collapse
Generic System Image (GSI) list :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
you can try only "Android 9 Pie" official or unofficial gsi roms..
and remember ! Some GSIs roms maybe are not compatible with some devices! you can ask for your device on each thread
(for example look here): https://github.com/phhusson/treble_experimentations/issues/777
(usually this Gsi aosp 9 phh, generally works on most devices...BUT! ask first,and discuss it in the thread)
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
daitalos said:
Generic System Image (GSI) list :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
you can try only "Android 9 Pie" official or unofficial gsi roms..
and remember ! Some GSIs roms maybe are not compatible with some devices! you can ask for your device on each thread
(for example look here): https://github.com/phhusson/treble_experimentations/issues/777
(usually this Gsi aosp 9 phh, generally works on most devices...BUT! ask first,and discuss it in the thread)
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
Click to expand...
Click to collapse
Can I do this without stock ROM and only TWRP? Because having the stock ROM is disabling my twrp to function without wiping and if I wipe than my stock ROM doesn't work
Thanks!
Mkami said:
Can I do this without stock ROM and only TWRP? Because having the stock ROM is disabling my twrp to function without wiping and if I wipe than my stock ROM doesn't work
Thanks!
Click to expand...
Click to collapse
Sorry,but I don't understand what do you mean " without stock rom and only twrp"...
you can install a Gsi rom, with two ways
Via TWRP, or Via Fastboot : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ (Tab S4 is a-only arm64)
for any other question, it is better to ask in the thread : https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
(read carefully in OP & you can post,every single question there for your device,and you will get certainly help from the developer or from any other user..)
Mkami said:
Can I do this without stock ROM and only TWRP? Because having the stock ROM is disabling my twrp to function without wiping and if I wipe than my stock ROM doesn't work
Thanks!
Click to expand...
Click to collapse
You are going to have to just wipe it and start over from square one, unless you made a TWRP backup before starting all of this.
Download and flash the latest stock rom from recovery and then you can load twrp again.
I was looking at the possibility of using GSI's on some devices, and while they can offer new life to older devices, they're not entirely stable all the time unless you're willing to make your own changes. I know Lineage has made some excellent progress, but it's not fullproof yet and I wouldn't try it unless you're willing to not use your device as a daily use device.
I had an extra T-Mobile Revvlry which is basically a rebranded Moto g7 Play that I installed the Lineage GSI image and it works fairly well. However, this is more the exception to the rule and Moto devices, I feel, are far simpler in design vs certain Samsung devices. It also had a ton of trial and error involved for me to get it up and running properly.
Is it possible as the s4 becomes older, more people buy it and Samsung stops releasing official updates that someone will come along and create a ROM for it? Or is it more like Samsung locked the bootloaders and its close to impossible to write a ROM for it? Is it still possible to root the s4?
slipnslider said:
Is it possible as the s4 becomes older, more people buy it and Samsung stops releasing official updates that someone will come along and create a ROM for it? Or is it more like Samsung locked the bootloaders and its close to impossible to write a ROM for it? Is it still possible to root the s4?
Click to expand...
Click to collapse
Read very carefully without rush ! for " WETA Kernel + Encryption disabler " etc
especially, read the user comments carefully, and ask on the thread for any questions you have..
https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278 (Pie version)
https://forum.xda-developers.com/showpost.php?p=79483624&postcount=2
https://forum.xda-developers.com/galaxy-tab-s4/how-to/guide-sm-t83x-twrp-magisk-t4059227
( Newest Odin v3.14.4 is there : https://dl2018.sammobile.com/Odin3-v3.14.4.zip )
Thanks. I took a quick peak at the roms and kernels in the roms and kernels forum and they are pretty much all abandoned.
Someone did mention that the LOS 16.0 and ArrowOS GSI's work alright but are a bit buggy.
slipnslider said:
Thanks. I took a quick peak at the roms and kernels in the roms and kernels forum and they are pretty much all abandoned.
Someone did mention that the LOS 16.0 and ArrowOS GSI's work alright but are a bit buggy.
Click to expand...
Click to collapse
samsung,maybe at the end of july to give the upgrade to android 10....it is very likely to happen I think
yes,all Gsi Roms still have various problems unfortunately...
my opinion is: stay to stock rom for now....you can "uninstall" many applications if you want & without root, via "samsung package disabler"(paid) from playstore, or with this way:
https://beebom.com/how-remove-bloatware-android-without-root/
also,you can Install "NiceLock Downloader Companion App" ,to add some features on your device : https://forum.xda-developers.com/galaxy-note-9/themes/nicelock-module-download-links-module-t3923844
with this way I operate my device until now..