Introduction
Sailfish OS is a mobile operating system combining the Linux kernel for a particular hardware platform use, the open-source Mer core middleware, a proprietary UI contributed by Jolla, and other third-party components.
Click to expand...
Click to collapse
This is a port of Sailfish OS to cancro (Xiaomi Mi3/Mi4), based on CyanogenMod 12.1.
What Works: https://wiki.merproject.org/wiki/Adaptations/libhybris#Smartphones (Check Xiaomi Mi3)
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Whats new:
Updated to Sailfish 2.1.3.7
Click to expand...
Click to collapse
Known issues:
1) Wifi mac address not detected properly
Click to expand...
Click to collapse
Current TODOs: Sailfish OS on cancro's Trello Board
Download links:
Cyanogenmod 12.1 base: https://www.androidfilehost.com/?fid=529152257862691291 (Mirroring this, as CM servers are shutting down)
Sailfish OS rootfs: https://www.androidfilehost.com/?fid=817906626617953262
Click to expand...
Click to collapse
Installation Instructions:
NOTE: This release is also available as an OTA to existing users.
1) Make sure your device has the new partition layout needed for Android M and a custom recovery. Boot to Recovery, wipe cache, dalvik-cache, system and data. ( https://jrizzoli.github.io/dotfiles/ )
2) First install cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-cancro.zip As your base ROM, and make sure it works well.
3) Then Install sailfishos-cancro-release-2.1.3.7-beta.zip on top of it. This will replace your boot image with sailfish boot image, and installs sailfish os to /data/.stowaways/sailfishos . The installation can take a little while, so be patient.
If you are already running, CM12.1 YOG7D/already have SailfishOS installed, you can simply flash the Sailfish OS without wiping flash/partition.
Click to expand...
Click to collapse
Big kudos to @mixmoto and Nokius, for patiently testing this release over and over.
P.S Thank you all for your support. I really really appreciate it - and it's what motivated me to make some time in my busy days to create this release. Wish you all Happy Holidays!
XDA:DevDB Information
Sailfish OS for cancro, ROM for the Xiaomi Mi 3
Contributors
saidinesh5, Ar4er, Folks at #sailfishos-porters, especially @mal-
Source Code: https://github.com/CancroSailors
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Must have CM12.1-YOG7D
Based On: CyanogenMod 12.1-YOG7D
Version Information
Status: Alpha
Created 2016-09-15
Last Updated 2018-01-07
Hey Dinesh,
Thanks for your work,
does this have sfdroid support?
Ekril said:
Hey Dinesh,
Thanks for your work,
does this have sfdroid support?
Click to expand...
Click to collapse
Hey, Nope. SFDroid support is on my TODO list for now.
It may take a while though. I need a Multirom working with CM13.0(which is my primary ROM), so I can safely port all the needed changes for SFDroid to my CM12.1 base without losing all my data. Any help welcome here!
Cheers
saidinesh5 said:
Hey, Nope. SFDroid support is on my TODO list for now.
It may take a while though. I need a Multirom working with CM13.0(which is my primary ROM), so I can safely port all the needed changes for SFDroid to my CM12.1 base without losing all my data. Any help welcome here!
Cheers
Click to expand...
Click to collapse
Thank you!!! this is awesome!!
Almost everything it seems to be working :good:
Is it stable for daily use?
Rocketval said:
Thank you!!! this is awesome!!
Almost everything it seems to be working :good:
Is it stable for daily use?
Click to expand...
Click to collapse
Great!
Right now i don't think it's ready for daily use yet, as sometimes my device's sensors and audio stop working randomly. Not sure if it is just my device though (because of some weird hacks I've been using).
I suspect this maybe because the CM 12.1 zip i was using to boot differs from the sources I've used to compile this rom. Once that issue is fixed, i think this will be usable for daily use. Camera works, Browser works, basic apps work.. And compiling that cm 12.1 means even sfdroid will work ...
saidinesh5 said:
Great!
Right now i don't think it's ready for daily use yet, as sometimes my device's sensors and audio stop working randomly. Not sure if it is just my device though (because of some weird hacks I've been using).
I suspect this maybe because the CM 12.1 zip i was using to boot differs from the sources I've used to compile this rom. Once that issue is fixed, i think this will be usable for daily use. Camera works, Browser works, basic apps work.. And compiling that cm 12.1 means even sfdroid will work ...
Click to expand...
Click to collapse
For what I know only few cm12 builds worked fine when flashed before sfos..
Maybe you need another build.. I don't know..
Rocketval said:
For what I know only few cm12 builds worked fine when flashed before sfos..
Maybe you need another build.. I don't know..
Click to expand...
Click to collapse
Could be. Most bugs i had to fix last week were because of differing versions too. That's why I'm trying to compile a cm12.1 right now.
Also right now as I'm on CM13.0, i was just using a system.img from the CM12.1.zip.. And making sailfish loop Mount that as the actual /system/ . not sure if that's causing any issues.
Right now my options are port multirom to CM13.0 (having some weird errors there) or wipe my device clean and downgrade to CM12.1 (have been trying to avoid this for months now!).
saidinesh5 said:
Could be. Most bugs i had to fix last week were because of differing versions too. That's why I'm trying to compile a cm12.1 right now.
Also right now as I'm on CM13.0, i was just using a system.img from the CM12.1.zip.. And making sailfish loop Mount that as the actual /system/ . not sure if that's causing any issues.
Right now my options are port multirom to CM13.0 (having some weird errors there) or wipe my device clean and downgrade to CM12.1 (have been trying to avoid this for months now!).
Click to expand...
Click to collapse
Yeah, we definetely need multirom, with 64gb mi4w I have more than 32+ free and a lot of will to try
Thank bro
Thank you!!!
As a temporary fix for radio, pulseaudio could be restarted, NOT as root.
Code:
systemctl restart pulseaudio --user
adeen-s said:
As a temporary fix for radio, pulseaudio could be restarted, NOT as root.
Code:
systemctl restart pulseaudio --user
Click to expand...
Click to collapse
I currently use this command everytime i wanted the FM radio to work. I will have to look into why this is failing by default though
Code:
$pactl set-source-port source.primary input-fm_rx
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Dr. Ramm said:
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Click to expand...
Click to collapse
this isn't android, you cannt flash gapp
Dr. Ramm said:
i cant undersatand for what need to flash cm-12.1? I cant flash clean sailfish.zip?
UPD can i flash gapps and supersu?
Click to expand...
Click to collapse
Due to legal reasons, Sailfish OS doesn't bundle the proprietary blobs(device drivers, system libraries etc..) provided by the phone vendors in it's zip.
As I have compiled Sailfish OS using sources from CM-12.1, it tries to access these proprietary files on your device via. CM-12.1 libraries. That's why you have to flash a CM-12.1 zip first, before flashing Sailfish OS. (i.e just clean flashing sailfish.zip won't work)
As of now, you don't have to flash gapps, as there is no way to use them from Sailfish OS. Once we get sfdroid running, we can run Android apps from within Sailfish OS, then you can flash gapps if you want.
Sailfish OS already comes with an su binary (accessed via. devel-su command) and full root access. So, you won't need Super SU.
saidinesh5 said:
As I have compiled Sailfish OS using sources from CM-12.1, it tries to access these proprietary files on your device via. CM-12.1 libraries. That's why you have to flash a CM-12.1 zip first, before flashing Sailfish OS. (i.e just clean flashing sailfish.zip won't work)
Click to expand...
Click to collapse
got it
saidinesh5 said:
As of now, you don't have to flash gapps, as there is no way to use them from Sailfish OS. Once we get sfdroid running, we can run Android apps from within Sailfish OS, then you can flash gapps if you want.
Click to expand...
Click to collapse
Stock market not working (as u say in 1st post) but how i can install some apps?
saidinesh5 said:
Sailfish OS already comes with an su binary (accessed via. devel-su command) and full root access. So, you won't need Super SU.
Click to expand...
Click to collapse
nice
run very smooth on my mi3
Dr. Ramm said:
got it
Stock market not working (as u say in 1st post) but how i can install some apps?
nice
Click to expand...
Click to collapse
You can use https://openrepos.net/content/basil/warehouse-sailfishos app to install apps.. I will include this in the zip for the next build (Which will soon be available).
First enable installation of untrusted software in Settings, then download the latest rpm of that from your browser and install it.
saidinesh5 said:
You can use https://openrepos.net/content/basil/warehouse-sailfishos app to install apps.. I will include this in the zip for the next build (Which will soon be available).
First enable installation of untrusted software in Settings, then download the latest rpm of that from your browser and install it.
Click to expand...
Click to collapse
can u tll me where located screenshots and how i can upload it on pc
some screens is here
after turn off mi3 10s, i dont turn on device
Related
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Introduction
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
NOTE: This is a cooked ROM based on Compiled from Source by Bule.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------
This project no longer updated because I sold this device. Thanks for following my projects :good:
-----------------------------------------------------------------------------------------------------------------Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Click to expand...
Click to collapse
Features
It's a standard CyanogenMod 12.1 Bule build 20160102 porting plus this:
Deleted China app
Default system theme
Added Xperia keybord (deleted china keyboard)
Europe timezone
Fixed host for normal contacts synchronization
en local
Root explorer in data/app (can delete from home app)
.
Click to expand...
Click to collapse
Installation instructions
Download the ROM into internal/external SD.
Download GoogleApps into internal/external SD.
Create a backup with TWRP if need.
Factory Reset via TWRP.
Flash it via TWRP.
Flash GoogleApps via TWRP.
If you receive the error in the TWRP "mount: failed to mount /dev/block/platform/mtk-msdc.0/..." flash the rom again.
Wipe dalvik-cache and cache via TWRP.
Reboot and waiting to complete the ROM installation.
Click to expand...
Click to collapse
Update instructions
Download the ROM into internal/external SD.
Download GoogleApps into internal/external SD.
Create a backup with TWRP for security.
Flash it via TWRP.
Flash GoogleApps via TWRP.
If you receive the error in the TWRP "mount: failed to mount /dev/block/platform/mtk-msdc.0/..." flash the rom again.
Wipe dalvik-cache and cache via TWRP.
Reboot and waiting to complete the ROM update.
Click to expand...
Click to collapse
Xposed installation
For Xposed installation follow this thread and install the arm64-sdk22 version.
Click to expand...
Click to collapse
Know bugs
Notifications LED: working fine with some colors, red | green | cyano | pink | orange | white but the cm color selection go crazy sometimes, we working to fix this, but the notifications now working fine.
Engineering mode not working (in this moment into no one CM working).
FM Radio module not working.
Sim 2 not working (need testing).
Click to expand...
Click to collapse
Change log
Code:
Build 1 - 2016/01/06
[new] First release.
Click to expand...
Click to collapse
Downloads
External Download (sorry but I can't upload every build): The author abandoned for a moment for instability issue, when this rom come back again, I repost here too.
Click to expand...
Click to collapse
Important notes
This ROM is based on Bule Version with plus features get from other CyanogenMod available for our device. The most important in this ROM is stability with velocity. If you wanna try this ROM remember this is a testing ROM and all times we working for give the best experience with this ROM and device. If you have a problem you can write here or into the official site (I suggest to talking here because into XDA we have the best developers in the android ecosystem).
Click to expand...
Click to collapse
XDA:DevDB Information
[ABANDONED][ROM][BUILD 1 - 2016/01/06] CyanogenMod 12.1 - Bule Repack, ROM for the Redmi Note 2
Contributors
Namaless, vova_vafin, bule
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-01-06
Last Updated 2016-02-01
Reserved
You should tell us...WHY THIS ROM, WHY THIS THREAT?
There is the Daniel101 mod already which seems to have all this here PLUS other cool stuff.
Even if one doesn´t need the extra stuff....just ignore it. So no need for this ROM/THREAT here.
Otherwise please tell us what makes this here so special?
DJ-Tumor said:
You should tell us...WHY THIS ROM, WHY THIS THREAT?
There is the Daniel101 mod already which seems to have all this here PLUS other cool stuff.
Even if one doesn´t need the extra stuff....just ignore it. So no need for this ROM/THREAT here.
Otherwise please tell us what makes this here so special?
Click to expand...
Click to collapse
First for all thanks to post your idea with rude method.
Next you know some ppl can use some roms?
Third you can ignore the rom/thread and use what you want, example I used Miui stable but I testing all roms when come out for funny and for help other ppl.
What you think resolve with your post? Nothing...
Sorry if you think I'm rude, but I reply with the same method you post here...
The owner of the rom have removed from public access, I talking with him if want repost or I request deleting to this thread. Sorry for inconvenience.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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.
*
*/
LineageOS 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). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for LG G4 . The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
Video Recording
Installation:
First time flashing LineageOS 14.1 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 data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
h815: https://download.lineageos.org/h815
h811: https://download.lineageos.org/h811
personnal nightlies http://host.erwanleboucher.fr/
XDA:DevDB Information
CM 14 on LG G4, ROM for the LG G4
Contributors
genesixxbf3, codeworkx
Source Code: http://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: V20A Bootloader and modem
Version Information
Status: Beta
Created 2016-10-10
Last Updated 2018-01-28
Reserved
What's working.
everything except what's not working.
What's not working ?
encryption (who use that )
f2fs (who use that too )
QHD video recording
official = signed
unofficial = no signed
to go to unofficial to official flash experimental first (and boot it)
Reserved
If you don't have a sim card detected try that
Code:
adb root
adb shell rm /data/user_de/0/com.android.providers.telephony/databases/telephony.db
adb shell rm /data/user_de/0/com.android.providers.telephony/databases/mmssms.db
adb reboot
Nice job mate! Thank you!
Everythink work ??? no bug ? no issues ? theme engine work ?
yes i know Nougat is too Young for Stable custom Rom at this moment but hope
What doesn't work? if you dont mind me asking?
Awesome work, thanks Genesixx
If there are known issues I am sure the OP will update the first post. You can also flash it and post if you find anything, just don't forget to make a full backup first ????
How is the camera on this build?
Op says you should flash gapps 6.0, is this right?
ashensii said:
Op says you should flash gapps 6.0, is this right?
Click to expand...
Click to collapse
7.0 gapps
to see what's not workin check second post
wow excellent work!
Is this stable enough to use as a daily driver?
ceanth said:
wow excellent work!
Is this stable enough to use as a daily driver?
Click to expand...
Click to collapse
It is
Was running the 10-05 build for several days. I find it works just as good as CM13, possibly better (smoother/faster). Bugs are very minimal, features are too but overall this is a very stable and solid build so far!
THANK YOU @genesixxbf3 for bringing this to us! I don't really like CM13, but 14, something about it is very nice (coming from someone that prefers stock over aosp).
EDIT: It should be posted that H811 users need to be on 20o FW before flashing this, to make sure they get best experience (if you want sound/camera working).
EDIT2: Oh and now there is a thread for me to report: Zooming with standard gallery hot-reboots the phone.
theslam08 said:
It is
Was running the 10-05 build for several days. I find it works just as good as CM13, possibly better (smoother/faster). Bugs are very minimal, features are too but overall this is a very stable and solid build so far!
THANK YOU @genesixxbf3 for bringing this to us! I don't really like CM13, but 14, something about it is very nice (coming from someone that prefers stock over aosp).
EDIT: It should be posted that H811 users need to be on 20o FW before flashing this, to make sure they get best experience (if you want sound/camera working).
Click to expand...
Click to collapse
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
ceanth said:
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
Click to expand...
Click to collapse
Unfortunately I am not sure about the h815. With the h811 we had a recent issue where we had to be on the latest FW for it to fully work.
I would 'assume' it would be the same for you. May wish to wait for 815 users to report back which FW they're on and how it all works for them.
(and you don't have to actually be running the stock ROM before flashing this, the firmware is a once-flash-always-flashed type situation; firmware is not ROM based it stays between ROMs)
ceanth said:
thanks, i might flash it tonight then. Should 815 users also be on stock rom before flashing this? I am currently on v20d stock rom
Click to expand...
Click to collapse
v20A or newer. So you are fine. Before flashing you don't care what rom you are on. You just need to wipe system , data , cache and dalvik cache and flash whatever you like.
kessaras said:
v20A or newer. So you are fine. Before flashing you don't care what rom you are on. You just need to wipe system , data , cache and dalvik cache and flash whatever you like.
Click to expand...
Click to collapse
ok great.
I'll give it a go and report back with feedback to the group
ceanth said:
ok great.
I'll give it a go and report back with feedback to the group
Click to expand...
Click to collapse
(out of subject)
I wonder how do you live with the stock rom on G4
You charge the phone 2 times per day ? haha
The stock rom has issues and it doesn't let the phone get into doze.
Have fun flashing you will never wanna go back to stock again
kessaras said:
(out of subject)
I wonder how do you live with the stock rom on G4
You charge the phone 2 times per day ? haha
The stock rom has issues and it doesn't let the phone get into doze.
Have fun flashing you will never wanna go back to stock again
Click to expand...
Click to collapse
Haha. I flashed stock rom because I wanted to use Android Pay. There is a deal on in the UK where by you get free London Underground travel on Mondays throughout October.
I was planning on flashing something else after the offer is done but Android Pay failed to work this morning causing a massive queue behind me I have had enough of it!
ceanth said:
Haha. I flashed stock rom because I wanted to use Android Pay. There is a deal on in the UK where by you get free London Underground travel on Mondays throughout October.
I was planning on flashing something else after the offer is done but Android Pay failed to work this morning causing a massive queue behind me I have had enough of it!
Click to expand...
Click to collapse
Hmmm. I don't use android pay but I read somewhere that you can use it with cm 14 or 13 if you use an official and stable build , not nightly or unofficial , and disable superuser in developer settings.
Of course I don't know if that's true
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
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.
*
*/
This is an unofficial TWRP 3.x build for the Huawei Honor 3C (h30u10/H30-U10)
This project is abandoned! I'll reopen the thread if I have any progress in the future... If you want anything from me you can contact me in my email address, in Telegram (@iamnotstanley) or in private message.
Only use this binary with your own responsibility, and please read the "known issues" list.
Working:
Everything, except the things in the "known issues" list.
TWRP functional checklist, but in this list not everything applies for our device
Known issues:
flash/restore image (boot&recovery) (installing with a zip [if you're using codelover's fixed update-binary] and backup working correctly) **need help **
Download:
Latest and older versions: See the DevDB Downloads page or click here. (Mirror)
Install:
You can install this recovery in 4 way:
Using an another version of TWRP: install the downloaded zip
Using an another version of TWRP: extract the zip and flash the image
Using SP Flash Tools: extract the zip and flash the image
Using Flashify or other flashing app: extract the zip and flash the image
Revert easily to codelover's TWRP:
Download from here the UPDATE-TWRP-2.8.6.0_H30-U10.zip or the UPDATE-TWRP-2.8.6.0_V2_H30-U10_EU.zip and install it inside the TWRP, after that if you reboot to recovery, you will see the old version.
Changelog:
TWRP changelog: here
Device changelog:
3.1.1-0:
Updated to the latest version.
We still have the the "image flash" problem!
3.1.0-0:
First release for Huawei Honor 3C (h30u10)
Built with omnirom android-5.1 tree
Prebuilt kernel: EU B306 (3.4.67)
Screenshots: See the DevDB Screenshots page or click here.
Credits:
iamnotstanley
codelover
carliv for his bootimg module
MSF-Jarvis for his initial device tree
TeamWin team
omnirom team
XDA:DevDB Information
TWRP for Huawei Honor 3C, Device Specific App for the Honor 3C
Contributors
iamnotstanley, codelover, carliv, MSF-Jarvis, TeamWin team & omnirom team
Source Code: https://github.com/iamnotstanley/android_device_huawei_h30u10/tree/android-5.1
Version Information
Status: Abandoned
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-05-13
Created 2017-04-01
Last Updated 2018-01-29
Reserved
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
hassanjavaid8181 said:
Nice woork bro
why did not you patch it bro for img files flashing??
Can you Send Me sources
Click to expand...
Click to collapse
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
iamnotstanley said:
Thanks.
I'm working on the image flashing fix, but I'm building from source code and nearly scratch, and now I finding the cause of the problem. I'll fix it as soon as I can.
My source code (TWRP device tree) is in the post: https://github.com/iamnotstanley/android_device_huawei_h30u10
Click to expand...
Click to collapse
really appreciate your efforts:good:
good luck
Bro can we flash magisk by this version.
mnumaher said:
Bro can we flash magisk by this version.
Click to expand...
Click to collapse
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
iamnotstanley said:
If Magisk doesn't work in the older or other recoveries, it won't work in this recovery.
I think, because Magisk modify the boot image and MT6582 phones has a boot image with a special MTK header, and I think Magisk currently doesn't support this format. (Like the "new" systemless SuperSU.)
Click to expand...
Click to collapse
Thanks.
Is touch working correctly in this version?
mnumaher said:
Thanks.
Is touch working correctly in this version?
Click to expand...
Click to collapse
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Rayquaza said:
Thanks bro bringing twrp 3x to our device!!
I'm hoping you keep maintain this project as well till reach bugless
Click to expand...
Click to collapse
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
iamnotstanley said:
For me, yes. This version has B306 kernel. If your phone's touch is working on B306, it'll work, but it's not, you will need to change kernel. You can try this first, but if isn't working, tell me which kernel has working touch for your phone and I'll make a version for that.
Kernels: https://forum.xda-developers.com/showpost.php?p=60721740&postcount=861
Thanks for your support. I'll maintain this project while I have this phone. I'm trying to fix the img flash issue, but I think I need help with it.
Click to expand...
Click to collapse
Ty bro it's working absolutely fine.
When we will be able to flash img.
mnumaher said:
Ty bro it's working absolutely fine.
When we will be able to flash img.
Click to expand...
Click to collapse
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
working fine cheers!
iamnotstanley said:
I'm working on it, but I think I need help to fix that. I hope maybe somebody can help me.
Click to expand...
Click to collapse
hi and great work, thanks for that
codelover maybe have a patch for that, past time he say i forget it, but can help you to know how solve that
Hi @iamnotstanley, to answer your question:
If i recall correctly i did explained about the problem in my thread earlier - the problem lies on 3C KK kernels. (MTK variant only)
H30-U10 stock KK kernels do not permit writing to the boot partition (/dev/bootimg) directly, the partition is mounted as read only.
Interestingly, there are some ported recoveries out there that doesn't work, and user doesn't even know about it. (eg: ROM appeared to be flashed successfuly but failed to boot because boot.img didn't get through, missing assert() to stop)
If you find a working H30-U10 recovery that can write to boot for 3C, it's likely using JB kernel or KK kernel from other 6582 compatible KK kernel, not sure if someone has compiled a fully working 3C kernel.
With JB kernel, you will be missing SELinux & some other features, while KK kernel from other device is dangerous IMHO, unless you are 100% sure it's compatible, sometimes i wonder whether those permanently bricked 3C with partition error were using these 'patched' recoveries...
My TWRP 2.8.6.0 has been customized to deal with this, i wrote a few C custom functions for twrp, it works like this;
1) read the partition table while flashing, loop through until you find the details for target partition that you need to write.
2) calculate the size and offset to write (you will need to convert the hex to int, then some math again to get the bs, skip, etc value for dd)
3) use 'dd' to write directly to mmcblock0, instead of C fwrite to the specific built-in partition mount point, eg: /dev/bootimg
Wish i could help more, unfortunately i don't have 3C data with me anymore (hdd crashed), and my work is killing me.
Good luck with that!
codelover said:
Hi @iamnotstanley, to answer your question:
...
Click to expand...
Click to collapse
Hi!
Thanks for your answer, I really appreciate your help.
So the problem is mainly in the kernel. I don't think I can fix this, but I'll try after my exams.
TWRP updated to 3.1.1-0
Hello guys!
I updated the TWRP to 3.1.1-0 yesterday. Unfortunately it still have the image flash issue. If you're interested you can download from the DevDB Downloads page or the Github mirror.
Huawei Honor 3C H30-U10
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
SHBhatti said:
Hello guys
I m new on this site and want to know about my huawei honor 3c h30-u10
I want to root and install TWRP custom recovery in my cell without PC. .
I am using EMUI 3 and android ver 4.4.2 whereas build number is B310
Please any one give me detail with images.
Thanx in advance
Click to expand...
Click to collapse
Try rooting with root applications such as Baidu root and etc.
TamaziAce said:
Try rooting with root applications such as Baidu root and etc.
Click to expand...
Click to collapse
I was Try to root with king root, king root said that your device is rooted successfully but root checker said no root???? what should i do now..?
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on find7
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want. Recommended nano package)
Official root addon
LineageOS Extras
Changelog:
Changes for find7
Bug reports:
How to submit a bug report
LineageOS JIRA
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 15.1 for Find7a/s, ROM for the Oppo Find 7
Contributors
mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any version of ColorOS. Unified storage not supported.
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-07-09
Last Updated 2018-11-15
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Am having problem of cold start gps. Takes about 8-10 mins before locking in. However, once lock in,everything work perfectly.
Updated on 18july.now everything is perfect. Even the battery life got better.
thank you???
luckywang95 said:
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Click to expand...
Click to collapse
You can delete the storage check in the installer script. Did it before and worked fine. I'm gonna try it tonight with this build.
Update: Stucked in bootloop. Gonna try tommorow again.
Update#2: Here is my working solution:
1. Flashing rom
2. Flashing addonsu
3. Flashing openGapps micro
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Zoltan-X said:
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Click to expand...
Click to collapse
Are you serious? These are just simple apks for the styles you can change from display settings.
If you are so curious about "being hacked" look at the source: https://github.com/LineageOS/android_packages_overlays_Lineage
Curios i've had in those app a data collecting folder structure,
like db, files, and more, maybe a rootkit on my device???
I don't know, since i removed those my find7 works again really well,
what it didn't do since a long time in this year....
With best regards
Code looks fine and i'll recheck if the image was compromised or not or how, but later these days.
thank you for the quick hint to those files!
P.S.: I've dirty reflashed the image i used to install lineageOS, after the expected remove, and no these nightly seems not been compromised,
Sorry for the alert,
but in the last days many hacks occured in my private relationships with my dearest, so I was a little curios, but seems now clean on my device!
Thank You verry much,
and Kudos Kudos Kudos to your quick hint reply.
I just installed lineage-15.1-20180806-nightly-find7-signed.zip to replace my stock Oppo Find7 firmware on the weekend and after a few days with it, so far so good! I had to lose the LVM unfortunately, but I'd rather have an up to date OS.
The battery life seems shorter than the stock firmware. I can still get through the day, but down to 40 or 50% or less by 6PM instead of much more with the stock Oppo FW. I haven't tried tweaking any battery life settings yet though.
Two minor things with the install compared to the LineageOS howto - the SD card path was different to what was documented ( /internal_sd not /sdcard) , and I had to install open_gapps-arm-8.1-pico-20180812.zip (pico instead of the documented nano version)... but this was minor stuff and I got where I wanted to go.
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
knusto said:
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
Click to expand...
Click to collapse
Wooot ! They have nougat builds for find 7
hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
It will be fixed in next build.
mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Thank you so much. Can't wait
hexplor said:
Wooot ! They have nougat builds for find 7
Click to expand...
Click to collapse
AOKP is now on Oreo for Find 7
mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Got the latest build. All fine Thanks
Allthough its not supported i've got unified working. not reliable tho. the only way i got it working when flashing los and direct rebooting into recovery again and then flashing the cm-13.0-find7-unified-storage-patch.zip from the according thread. cuz the original link is dead incl mirror i got my copy uploaded to gdrive here. https://drive.google.com/file/d/1sZ72qUD5P7qL4tsIF3MB-cQk9x9pamRR/view?usp=sharing
only drawback being you cant reboot anymore cuz that will somehow give you the your-sdcard-is-****ed message. havent found a reasonable routine so i guess you'll have to try your luck yourself and maybe give feedback?
Hi, could you disable CABC(Content Adaptive Brightness Control) or provide a way to disable it? The hardware of Find 7 use it and it really makes some troubles, brightness, color. Really thanks if you have that time
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Manas1796 said:
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Click to expand...
Click to collapse
That commit has already been applied for Find7 - https://github.com/LineageOS/androi...mmit/80e1e7e5ffca2c69730eecc8c498423c2ea48463
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?