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..?
Related
PREAMBLE
Team Win Recovery Project 2.x, or twrp2 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.
NOTE: I have built and tested this on my Lenovo A3000-H (16 GB version with 3G) with the a3000_prc_3gfull board/partition table. This is not going to work with FUSE devices!
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 recovery image
* 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.
*/
I'll keep this thread short and simple. Want a changelog or a list of features? Then visit teamw.in.
DOWNLOAD
You can always get the latest build from here. You can flash them using an already existing recovery or by extracting and flashing it using SP Flash Tool.
CREDITs
chrmhoffmann
TeamWin and OmniROM
XDA:DevDB Information
TWRP for the Lenovo IdeaTab A3000-H, Tool/Utility for the Lenovo A3000
Contributors
Olivier
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2014-06-26
Last Updated 2014-12-28
Where download-link?
Well, I really want to install that, but this internal storage bug is really major.. What's a recovery software is good for if it can't flash things?
..And where is that link? ?
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app
faissl said:
Well, I really want to install that, but this internal storage bug is really major.. What's a recovery software is good for if it can't flash things?
..And where is that link? ?
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app
Click to expand...
Click to collapse
FUSE-firmware haven`t internal sdcard. What firmware are you used?
I just bought this tablet, is bootloader unlocked? I got a 4gb version of the A3000, can I normally fastboot flash recovery twrp.img?
Download link?
I just got Lenovo A3300-T Tablet from China, and I want to wipe off all things on that and just install some custom OS. Can some one please help me with the same.
Is A3300 same as A3000 as this post points to A3000 only. Please help me as I am having really hard time with this tablet.
Feche said:
Download link?
Click to expand...
Click to collapse
See DevDB.
anshumangoyal said:
I just got Lenovo A3300-T Tablet from China, and I want to wipe off all things on that and just install some custom OS. Can some one please help me with the same.
Is A3300 same as A3000 as this post points to A3000 only. Please help me as I am having really hard time with this tablet.
Click to expand...
Click to collapse
No. This is for A3000 and has only been tested on A3000-H.
Can you help me find it for Lenovo A3300-T Tablet. I want to install custom OS on that but not able to find it's recovery.
I'd give feedback if I found the download link, but I haven't.
kupyxa4444 said:
FUSE-firmware haven`t internal sdcard. What firmware are you used?
Click to expand...
Click to collapse
The last one there is, of 9-26
I flashed, and when I enter recovery I stuck in bootloop
A new build (TWRP 2.8.1.0) is up, it works just fine (I have fixed all of the bugs). Do note it will only work on a3000_prc_3gfull devices! I have also added a download link to the OP since you guys don't seem to like DevDB...
Olivier said:
A new build (TWRP 2.8.1.0) is up, it works just fine (I have fixed all of the bugs). Do note it will only work on a3000_prc_3gfull devices! I have also added a download link to the OP since you guys don't seem to like DevDB...
Click to expand...
Click to collapse
Please remove my bug reports
I have flashed that and no bugs till now
Thank you for your hard work
A new build (TWRP 2.8.3.0) is up, enjoy.
Olivier said:
A new build (TWRP 2.8.3.0) is up, enjoy.
Click to expand...
Click to collapse
Think you sir...
It is worked fine on my tablet
request
Sir @Olivier I am on build A3000_A422_013_025_140626_WW_CALL_FUSE....... previous version of recovery worked for me.....except emmc bug.......now I see that you have fixed the bug but the new update doesn't even boot on my device.....I know that you mentioned it will only work on pgrc_3g_full......and I am not on the same.....but I would just like to request a port to the above build number because......your cm11 also installs quite nicely over This build as reported by other users in cm11 thread.....I would love to help with beta testing if needed.....thanks in anticipation.....and I got this build by installing azam426's posted rom and then installing a little ota update.....
Keep up the good work..sir......great respect.....:good:
Do not do a full wipe. IMEI number has deleted the possibility. Deleted my imei i can't write imei. :/
Reupload please, because link is dead
reupload pls
Xperia M5 First CyanogenMod Rom
* 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.
this rom is beta port and need tester
Working:
You tell me
Bugs:
You tell me
ROM link
Beta 1 [COLOR="Red"]NO KERNEL SOURCE =[/COLOR]
Beta 2 [COLOR="Red"]NO ES BUENO :([/COLOR]
Installation Instructions:
-unlock bootloder
-root and twrp install
-zip flash via twrp
-wipe data
-reboot
rom base customized tr marsmallow
this rom is beta and need tester.ıf you test and tell me work, TRXteam port new roms on xperia m5.
thanks @ByBlaCk @krkshalill @TheShadow35
Contributors
TRXteam,ByBlaCk,krkshalill,TheShadow35
ROM OS Version: Marsmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP+Any Rooted Stock Rom
Based On: CyanogenMod
Version Information
Status: Beta
How nice is that. Finally some custom roms are avaiable for m5.
jonathangrag said:
How nice is that. Finally some custom roms are avaiable for m5.
Click to expand...
Click to collapse
thanks.
my team port xperia m5 custom roms but need tester and tell me bugs.ıf some people test and report bug ı port new roms(eg.flyme cm14) xperia m5 and ı fix bugs.
Thread moved to Android Development. I would like to see kernel source very soon.
thx
Since it takes forever for anyone to do anything in these threads I went ahead and tested.
I was on Customized AU MM, TWRP&Rooted.
Wiped data, and flashed zip.
Boot loop was the result.
グリッチ said:
Since it takes forever for anyone to do anything in these threads I went ahead and tested.
I was on Customized AU MM, TWRP&Rooted.
Wiped data, and flashed zip.
Boot loop was the result.
Click to expand...
Click to collapse
this rom beta and some devices was boot loop.My team cant fix that and not update.If you like cm13 and you port it like devices(e.g elephone wowney lite,infinix zero 3,redmi note 2,redmi note 3(Mediatek),or any mt67xx eg.jıayu s3,jıayu s3 plus,....)
グリッチ said:
Since it takes forever for anyone to do anything in these threads I went ahead and tested.
I was on Customized AU MM, TWRP&Rooted.
Wiped data, and flashed zip.
Boot loop was the result.
Click to expand...
Click to collapse
https://mega.nz/#!dhNC2Qha!HeCEBti25M1ecmxUFhsZ_AZE_dX-amjMJZL-OZea-sc
if you test its new rom wait 30 minutes black screen after flashed and reboot,ıf work you lucky guy,but not work you unlucky guy,My team Closed this thread because some devices boot loop or not working but some devices working,ı dont known this.If fix , share it.
.Have a good day.
thread closed.
TRXteam said:
https://mega.nz/#!dhNC2Qha!HeCEBti25M1ecmxUFhsZ_AZE_dX-amjMJZL-OZea-sc
if you test its new rom wait 30 minutes black screen after flashed and reboot,ıf work you lucky guy,but not work you unlucky guy,My team Closed this thread because some devices boot loop or not working but some devices working,ı dont known this.If fix , share it.
.Have a good day.
thread closed.
Click to expand...
Click to collapse
Ok, I downloaded it, but I just want to make sure before flashing...
Your instructions say flash zip > wipe data.
Should I do that or Wipe data (data only?) > flash zip?
TRXteam said:
Xperia M5 First CyanogenMod Rom
* 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.
this rom is beta port and need tester
Working:
You tell me
Bugs:
You tell me
ROM link
https://mega.nz/#!Fg1AQCyA!SlGKtLdQmLJbFw8JHeulDa4b4KznRRkkYtusK1Ea0K0
Installation Instructions:
-unlock bootloder
-root and twrp install
-zip flash via twrp
-wipe data
-reboot
rom base customized tr marsmallow
this rom is beta and need tester.ıf you test and tell me work, TRXteam port new roms on xperia m5.
thanks @[email protected]@TheShadow35
Contributors
TRXteam,ByBlaCk,krkshalill,TheShadow35
ROM OS Version: Marsmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: TWRP+Any Rooted Stock Rom
Based On: CyanogenMod
Version Information
Status: Beta
Click to expand...
Click to collapse
will this rom pass safetynet api test?
Hello, this ROM is compatible with Sony Xperia M5 E5603, E5606 and E5653? It's correct?
The version dualSIM "hollyds" is compatible? Thank you very much for the support!
ataraxist said:
will this rom pass safetynet api test?
Click to expand...
Click to collapse
ı dont known,you test and look it.:good:
pickmod said:
Hello, this ROM is compatible with Sony Xperia M5 E5603, E5606 and E5653? It's correct?
The version dualSIM "hollyds" is compatible? Thank you very much for the support!
Click to expand...
Click to collapse
not support hollyds,this rom compatible with hollyss(eg.E5603)
グリッチ said:
Ok, I downloaded it, but I just want to make sure before flashing...
Your instructions say flash zip > wipe data.
Should I do that or Wipe data (data only?) > flash zip?
Click to expand...
Click to collapse
グリッチ said:
Since it takes forever for anyone to do anything in these threads I went ahead and tested.
I was on Customized AU MM, TWRP&Rooted.
Wiped data, and flashed zip.
Boot loop was the result.
Click to expand...
Click to collapse
rom update beta2 and need tester.
TRXteam said:
rom update beta2 and need tester.
Click to expand...
Click to collapse
rom not working: after install file via twrp and reboot device i get the bootloop. I use TWRP 3.0.2.2. After try wipe cache partition i get error message "can't umount /cache: device busy". Tested b1 and b2 too.
spark1991z said:
rom not working: after install file via twrp and reboot device i get the bootloop. I use TWRP 3.0.2.2. After try wipe cache partition i get error message "can't umount /cache: device busy". Tested b1 and b2 too.
Click to expand...
Click to collapse
thanks your reply,My team goes to holiday and ı am alone but ı work it.
I'm downloaded the cm13 sources for build cm13 with kernel 3.10.[61/72] and binaries based on redmi note 2. If you want, i can help for you. Send me your usable binaries (/vendor and /device/ folders)
spark1991z said:
I'm downloaded the cm13 sources for build cm13 with kernel 3.10.[61/72] and binaries based on redmi note 2. If you want, i can help for you. Send me your usable binaries (/vendor and /device/ folders)
Click to expand...
Click to collapse
okay thanks your help.:good:
spark1991z said:
I'm downloaded the cm13 sources for build cm13 with kernel 3.10.[61/72] and binaries based on redmi note 2. If you want, i can help for you. Send me your usable binaries (/vendor and /device/ folders)
Click to expand...
Click to collapse
I dont understand... Sony opened sources for our device - why are you need sources for other device??!
Thread closed as there is no kernel source available. I have warned the OP a few days ago - without any success apparently
Here's a nice lecture about being a good developer. Rules are made to follow them and I fully expect it from you.
Regards,
Tom
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
*Only tested on TA-1032 but it should work on other models too*
Downloads:
Build 1:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
This TWRP now supports removing data encryption on Oreo.
General Changelog for TWRP version:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelog:
Build 1:
- Initial release
What works:
- Touch
- OTG
- Backup (system.img backup doesn't work but don't worry, you can backup System and you'll be fine)
- Restore
- Flashing IMGs and ZIPs
What doesn't work:
- Battery percentage is incorrect (it's possible to fix but need some time)
- MTP (it's possible to fix but need some time)
- you tell me
For full backup you need to remove encryption so you can backup /data too.
If you're wondering why protect_f, protect_s, para and uboot partitions have 0MB it's because these partitions have less then 1MB.
Comment if link need to be updated.
Credits:
@mohancm for Lenovo K4 Note TWRP
Screenshots:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Riadh300 said:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Click to expand...
Click to collapse
i installed it without problems, tell me your device model and how you installed it.
Worst thing that could happen is that recovery got bricked, to recover simply flash new recovery. it worked for me, with twrp flash img, with flashify and with SP Flash Tool. Maybe you flashed it in wrong way.
Also please can someone flash/test this twrp so i can see does it work for others.
System and Data can be backed up and restored on oreo with this twrp?
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
ChalapathiRevanth said:
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
Click to expand...
Click to collapse
Top.
Thank you
Reygal21 said:
System and Data can be backed up and restored on oreo with this twrp?
Click to expand...
Click to collapse
data can be backed up only after removing encryption, system can be backed up without problems.
As for restore, it works on Nougat (i restored whole rom when i tried substratum theme)
but i didn't tested for Oreo.
I think that will work on Oreo too because there is no change in partition mount points between Nougat and Oreo.
Update:
I found out that incorrect battery percentage and MTP are not kernel issue so it is possible to fix it.
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Nikola Jovanovic said:
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Click to expand...
Click to collapse
it's ported from Lenovo K4 Note TWRP which have MT6753 CPU
Though i noticed that medifire007 is smother, especially when changing storage. This TWRP have latest TWRP version and touch works smoothly while on mediafire007 TWRP you need to wait in beginning to work.
Can this work on Nokia 1 with Android Oreo 8.1?
abdul_manan said:
Can this work on Nokia 1 with Android Oreo 8.1?
Click to expand...
Click to collapse
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
SkaboXD said:
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
Click to expand...
Click to collapse
Thanks Bro! It worked! But there is a new problem Now. Here it is..
https://forum.xda-developers.com/nokia-1/help/stock-recovery-error-nokia-1-black-t3798928
Tested and working on TA-1028 variant with Android nougat. Installed SuperSU and everything seems okay. Thx dev:victory:
Is there any custom Rom and kernel for Nokia 3 .
Stock Nokia 3 Rom and kernel is really bad
Can i use for Nokia 3 locked bootloader???
How to install ?
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Umairali321 said:
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Click to expand...
Click to collapse
Doesn't work on 8.1? Did you tried it?
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 ?