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
Q&A for [ROM] [5.1.0] [AOSP Grogg's Way]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.1.0] [AOSP Grogg's Way]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I also made the plunge after CleanRom support was discontinued. Everything works great so far, awesome rom!!
TXJim said:
I also made the plunge after CleanRom support was discontinued. Everything works great so far, awesome rom!!
Click to expand...
Click to collapse
Same here. Running smoothly so far. Just got everything installed!
Is this ROM actually 5.1 ... cause google haven't released the factory image's yet...?
obsidianuk said:
Is this ROM actually 5.1 ... cause google haven't released the factory image's yet...?
Click to expand...
Click to collapse
I assure you, this is 5.1.0. It is not a modified factory image. Its AOSP compiled from source.
GROGG88 said:
I assure you, this is 5.1.0. It is not a modified factory image. Its AOSP compiled from source.
Click to expand...
Click to collapse
That miscellaneous category is in my battery stats again. Anyone else have it too? Doesn't seem to be draining battery, so I don't know what to make of it.
LucentBirch said:
That miscellaneous category is in my battery stats again. Anyone else have it too? Doesn't seem to be draining battery, so I don't know what to make of it.
Click to expand...
Click to collapse
Previous build had an option in dev settings that was added to remove unaccounted and overcounted stats from showing up. For some reason google only chooses to apply the changes to release builds. I removed that code to get a look at it, but you're right it is still there. I have re-committed the changes and have builds uploading in a bit.
GROGG88 said:
I assure you, this is 5.1.0. It is not a modified factory image. Its AOSP compiled from source.
Click to expand...
Click to collapse
Are you going to build again when the n7 2013 factory image is posted by google - or is there no point (I guess the real question is will there be specific changes for our device when the image is officially out?)
I'm trying to decided to flash now or wait... ☺
obsidianuk said:
Are you going to build again when the n7 2013 factory image is posted by google - or is there no point (I guess the real question is well there be specific changes for our device when the image is officially out?)
I'm trying to decided to flash now or wait...
Click to expand...
Click to collapse
Yes, I'll be building with new binaries and with whatever other changes may be implemented at that time...
obsidianuk said:
Are you going to build again when the n7 2013 factory image is posted by google - or is there no point (I guess the real question is will there be specific changes for our device when the image is officially out?)
I'm trying to decided to flash now or wait... ☺
Click to expand...
Click to collapse
My 2¢: flash now & start enjoying this incredibly smooth & fast ROM.
just a simple question: whenever u update this ROM, is it necessary/recommended to wipe the device again? or is the first wipe good enough?
and if its necessary, will the backup of all apps and system settings affect the performance after updating?
lucass001 said:
just a simple question: whenever u update this ROM, is it necessary/recommended to wipe the device again? or is the first wipe good enough?
and if its necessary, will the backup of all apps and system settings affect the performance after updating?
Click to expand...
Click to collapse
That really depends on the update.
@GROGG88 you say you're using elementalx kernel, right? Have you, or anyone else for that matter, had random reboots? I have at least 2 every day, if not more...
LucentBirch said:
@GROGG88 you say you're using elementalx kernel, right? Have you, or anyone else for that matter, had random reboots? I have at least 2 every day, if not more...
Click to expand...
Click to collapse
No random reboots on my N7
LucentBirch said:
@GROGG88 you say you're using elementalx kernel, right? Have you, or anyone else for that matter, had random reboots? I have at least 2 every day, if not more...
Click to expand...
Click to collapse
I have in the past, but currently I'm running my included kernel. Zero reboots...
USB OTG Support?
Does this have the ability to have dual charging and reading from a usb hub? I read the features and it didn't state that it did.
[email protected] said:
Does this have the ability to have dual charging and reading from a usb hub? I read the features and it didn't state that it did.
Click to expand...
Click to collapse
Then you have answered your own question. I do not hide features just so people are forced to question about them.
Hi thanks for the Rom works great.
One question is there a reason I lose all my none google email accounts in gmail when I upgrade to a new version?
nawo69 said:
Hi thanks for the Rom works great.
One question is there a reason I lose all my none google email accounts in gmail when I upgrade to a new version?
Click to expand...
Click to collapse
I'm not sure. I don't have non google contacts. Those should be stored in your data partition. Unless you're doing a wipe they should remain...
backup
I noticed you mentioned using backup apps with a clean install negates the wiping done. Is the same true for ADB and TWRP backups too?
Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0
Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.
good luck you guys
i have really nothing to offer ..
but please make this happen ..
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:
It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont
Cm we want... thank you for your interest!! ?
Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1
why is there not one custom rom for this device?
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.
Yes we can! Yes we can! Yes we can!
Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.
No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.
Hello. First of all , I'd like to apologize if my question is dumb and has already been answered... But I'm running out of ideas , i would like to install the Pure Nexus Rom because I'm on Cyanogen but the last build completely messed up my phone... And I don't know what Vendor image I should download ... I don't even know what that is... Thanks a lot for your future answers!
Rozalina340 said:
Hello. First of all , I'd like to apologize if my question is dumb and has already been answered... But I'm running out of ideas , i would like to install the Pure Nexus Rom because I'm on Cyanogen but the last build completely messed up my phone... And I don't know what Vendor image I should download ... I don't even what that is... Thanks a lot for your future answers!
Click to expand...
Click to collapse
Either use fastboot or TWRP 3.0 to flash the MMB29Q vendor before flashing the February OTA based Pure Nexus build. Check a rom's changelog to see which OTA it is based on, then flash that vendor image if need be. I must also add, several roms are based on the latest February AOSP branch which is MMB29U, the 5X MMB29Q vendor is what still needs to be installed. This is not a stupid question, you want to ask things like this to be sure you are in the know.
SlimSnoopOS said:
Either use fastboot or TWRP 3.0 to flash the MMB29Q vendor before flashing the February OTA based Pure Nexus build. Check a rom's changelog to see which OTA it is based on, then flash that vendor image if need be. I must also add, several roms are based on the latest February AOSP branch which is MMB29U, the 5X MMB29Q vendor is what still needs to be installed. This is not a stupid question, you want to ask things like this to be sure you are in the know.
Click to expand...
Click to collapse
Thank you so much for your answer ! I'm going to try that! Thank you again , I was so lost and desperate
Rozalina340 said:
Thank you so much for your answer ! I'm going to try that! Thank you again , I was so lost and desperate
Click to expand...
Click to collapse
Not problem, that's why this forum exists!
Sent from my Nexus 5X using Tapatalk
So what exactly does the vendor image do? Why do we need to update to update the ROM after a new android version is released?
am2012 said:
So what exactly does the vendor image do? Why do we need to update to update the ROM after a new android version is released?
Click to expand...
Click to collapse
From what I understand it's the drivers specific for that device, created by the device manufacturer. What I can't figure out is whether I should download those from this site of if they should be provided by the manufacturer somewhere? Like on lg.com?
macdabby said:
From what I understand it's the drivers specific for that device, created by the device manufacturer. What I can't figure out is whether I should download those from this site of if they should be provided by the manufacturer somewhere? Like on lg.com?
Click to expand...
Click to collapse
I've never used LG's website, but the vendor image is included in each 5X factory image:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Dior DNA said:
Good question.
At least one would need to repartition internal card, if I understood. This alone is not impossible but a bit hard and not without risk.
That said often I wonder if it could be possible to boot, say, TWRP (or any other Linux) from USB and take full dd backup of internal card for all certainty (and then repartition). This is how many Android TV boxes can be backed up (they use u-boot infrastructure). So why not phones?
Click to expand...
Click to collapse
indeed and that is what made me think, because aftervall, android is build upon lnnux
Mikxx said:
As we all know our 1+5T doesn't support project treble,
so my question is,
is this hardware or software dependent?
In other words,
is it possible for devs to find a way to implement it in future custom roms or in a kernel for our dumpling?
Or would this just be impossible?
Thanks in advance
Click to expand...
Click to collapse
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
the Doctor said:
[...]Also, it gives literally zero benefit to a custom ROM.[...]
Click to expand...
Click to collapse
I mark these words. Have a nice day.
update
Perhaps there is no functional benefit. But porting seems easier for some devices:
What about :
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
This is the Samsung Galaxy S9 running on AOSP Android Oreo thanks to Project Treble
the Doctor said:
This question has been discussed lots before.
https://forum.xda-developers.com/oneplus-5t/how-to/change-org-project-treble-op5t-t3709841
Implementing Project Treble would require repartitioning storage. Also, it gives literally zero benefit to a custom ROM.
TL;DR: It's never going to happen.
Click to expand...
Click to collapse
But it happened ?
cubandanger05 said:
But it happened ?
Click to expand...
Click to collapse
Yup, somebody saw a mountain and decided to climb it. We'll see what comes of it.
Yeah mokee ROM has treble working on the OnePlus One 5T. There's an unused partition that can be created without re-partition in the device and if you install a regular ROM it doesn't see it you install a treble ready ROM and you previously had mokee installed according to the mokee dev it works. It uses the ab style of treble. There is an "a" and "ab" and "a/b" versions from what I read. Mokee is releasing nightlies of their ROM
Haven't tried it on mine pretty happy with the aicp Oreo that I'm running so I can't tell you what bugs it has. Google it XDA has a discussion on mokee and treble with OnePlus 5t