Related
Hey guys, today after a long time i came back around to this subforum to see if there are any news for my yoga 2 380f but all i found were closed threads?! wtf happened?
after so many months of waiting one could finally unlock the bootloader and install a custom recovery - but now even the posts in these threads are empty.... why?
I am in the mids of gathering all the files that I did manage to get before they were removed. My tab is 1050f. Have all the stuff somewhere fore it
Sent from my SM-G901F using Tapatalk
I suspect a New dedicated forum
New TWRP 2.8.7.0 for YT2 1050 soon !
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
A recovery image does contain a Linux kernel which is under GPLv2, and the TWRP source code is under GPLv3 (see the license header in https://github.com/omnirom/android_b...d-6.0/twrp.cpp)
Click to expand...
Click to collapse
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
surdu_petru said:
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
Click to expand...
Click to collapse
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
pug1 said:
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
Click to expand...
Click to collapse
Yes, was started from scratch... should be OK for all YT2.
Also pixelflinger for _X86 are implemented, twrp works fine. ... and sure will work on stock Lenovo kernel for Android L.
Best regards.
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
pug1 said:
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
Click to expand...
Click to collapse
Kernel and also twrp must be compiled along with cm-12.1.
As I already said , my kernel source cannot be compiled ...( Lenovo do not provide a complete one ), but I'll update today later in order to fix all Lenovo issues.
Best regards.
New TWRP 2.8.7.0 for YT2 - 1050 ! Source code already available !
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
DEV-Flash
Brought to you by Thargorsson with a HUGE thanks to argraur​
DISCLAIMER
IM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOU OR YOURE PHONE YOU DO THAT ON YOUR OWN.
OK?
First, modifying he bootloader is risky.
Even more if you update it via recovery.
Dev-Flash is a project that was created by me serveral years ago but for now only for private use cases on my old HTC ONE m7 (that's why i call it hboot)
The final point gave argraur to me by releasing his AWESOME Pixel port for out 5X that brings it's own bootloader.
To wrap it up you can flash those zips to use multiple android systems (one after another of course) on your phone without freaking out in front on the computer due to a new factory image you have to flash (in order to get the lastest custom rom working with newer radio etc...).
Download links are below this little Q&A PLEASE DO NOT MIRROR THEM!
Obviusly only the 7.1.1 and 7.0.0 are uploadet now.
The others are coming later next week.
What is it?
- a collection of Bootloader/Radio/Vendor images
What are the opportunitys?
- no need for a computer anymore :victory:
-> in cause of a flashable zip?
Is this backwards/custom rom/stock etc... compatible?
- simply yes it is as long as you do not really mess around with those things
Downloads
Code:
Leave a thanks if u used my work :)
Android 7.0.0 (without vendor.,img)
https://mega.nz/#!md80ybia!5DM_dC_WW_mGT3gdPSveLdAv_9zFjYiK5bVmicVm7Ac
XDA:DevDB Information
Dev-Flash, Tool/Utility for the LG Nexus 5X
Contributors
Thargorsson, argraur
Version Information
Status: Alpha
Created 2016-12-21
Last Updated 2016-12-21
reserved #1
reserved #2
op5 cheeseburger
Stable
You need to decrypt, so either format userdata in TWRP or via fastboot
Flash at your own risk
Oct 10
Tipsy op5 cheeseburger v6.9.6 Final Nougat
- Oct security patches
- Stuff & fixes
working: ril, wifi, camera,gps bt, nfc,...
NOT working:
- ?
device tree: https://github.com/TipsyOs-Devices/device_oneplus_cheeseburger
kernel: https://github.com/GZR-Kernels/kernel_oneplus_msm8998
XDA:DevDB Information
GzR Tipsy, ROM for the Ground Zero ROMs
Contributors
martinusbe
Source Code: https://github.com/TipsyOs
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: v6.6 Ultra Blonde
Stable Release Date: 2017-07-23
Current Beta Version: July 6 2017
Beta Release Date: 2017-07-06
Created 2017-07-06
Last Updated 2017-10-14
Reserved
ss
Reserved
MultiRom for oneplus5 cheeseburger
You need to decrypt so either format userdata in TWRP or via fastboot
First build 07/17
I had some issues to get our blockbased zips to boot
Found out i needed a commit in recovery ROM-side, here in Tipsy , here on SlimRom's gerrit so if you have a not boot secondary rom, get your dev to pick it. Lineage should be fine, it's there.
Also an device commit could be needed like here on my Tipsy tree
I'm going to update the OP with an op5 Tipsy build that works as secondary, and will rebuild Validus too.
build 07/17
Recovery: TWRP-GzR-multirom Recovery IMG
Multirom zip: multirom-GzR-cheeseburger ZIP
Multirom uninstaller: uninstaller ZIP
build 07/20
* Enabled icons for the app * Enabled crypto (you still need to decrypt to flash custom roms)
Recovery: TWRP-GzR-multirom Recovery IMG
Multirom zip: multirom-GzR-cheeseburger ZIP
build 07/23
* Fixed booting from the app
Recovery: TWRP_multirom_cheeseburger_20170723-02.img
Multirom zip: multirom-20170723-v33g-UNOFFICIAL-cheeseburger.zip
build 09/19
* updated so i can flash O testbuilds on secondary, so here it is. Experiment at your own risk,
i have tipsy 7.1 last build as primary, and gzosp O as secondary
Recovery: TWRP_multirom_cheeseburger_20170919-03.img
Multirom zip: multirom-20170919-v33o-UNOFFICIAL-cheeseburger.zip
MultiRom Manager apk, added oneplus5 support. (now supports all oneplus devices with mr again)
GzR-MultiROMMgr-5.0.apk
I have no time for a tutorial now, so if you don't know what it is, or how to use it, please don't try
Big thanks to @nkk71 for pointing me at the recovery commit, and all his work on multirom of course :good:
Does it have jelly feature built in?
Unreal much alohas @martinusbe
Cheeseburger + Beer = Tipsy..
Hmmm, I'm suddenly hungry for a cheeseburger
Lovely, so the fun begins properly
Is this AOSP?
Mmmm... GZR... Do i have to be decrypted to try out? Not new to gzr but to OP5
Edit: OK now I see in OP that it "probably needs to be done", can probably confirm, since I tried with encryption but only bootloop.. Too lazy to backup data and decrypt so will probably wait a bit more
Do i need to flash gapps? And is magisk already inside? And what about substratum? Thanks
nadejo said:
Do i need to flash gapps? And is magisk already inside? And what about substratum? Thanks
Click to expand...
Click to collapse
To get Google Play and so on ... You need to flash gapps
Magisk is already inside the rom
I don't know about substratum but I think it's working
Everything works for me except Bluetooth . It connects but the music comes from the phone and not from the headphones
nadejo said:
Everything works for me except Bluetooth . It connects but the music comes from the phone and not from the headphones
Click to expand...
Click to collapse
Are you encrypted or also decrypted? Trying one more time to see if I didn't do something wrong, will probably try later a different TWRP image ...
caki25 said:
Are you encrypted or also decrypted? Trying one more time to see if I didn't do something wrong, will probably try later a different TWRP image ...
Click to expand...
Click to collapse
Im decrypted (requires formating trough ADB) im downloading carbon OS maybe they got Bluetooth working
https://www.androidfilehost.com/?fid=745425885120746040
nadejo said:
Im decrypted (requires formating trough ADB) im downloading carbon OS maybe they got Bluetooth working
Click to expand...
Click to collapse
really?
martinusbe said:
really?
Click to expand...
Click to collapse
That carbon Rom doesnt work dont flash it!!!
Im back on tipsy, yes i am decrypted and i used the latest test recovery
nadejo said:
That carbon Rom doesnt work dont flash it!!!
Im back on tipsy, yes i am decrypted and i used the latest test recovery
Click to expand...
Click to collapse
don't post links to other rom's using my trees here, it's kind of frowned upon, by me.
i'll look at the bt thing tomorrow
Awesome sauce.
martinusbe said:
i'll look at the bt thing tomorrow
Click to expand...
Click to collapse
im sry, i should have known that !
TWRP 3.6.2 For Griffin
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Bugs: You Tell Me
Download: Here
Spoiler: How To Flash?
Step 1) Install image
Step 2) Reboot To TWRP
Step 3) Click Flash Image
Step 4) Flash recovery.img to recovery
Thanks:
SirRGB for test
TeamWin Recovery Project for Device Trees
XDA: DevDB Information
[RECOVERY][UNOFFICIAL][griffin] TWRP 3.6.2 for Moto Z, Tool/Utility for the Moto Z
Contributors
@Batuhantrkgl
Source Code: https://github.com/TeamWin/android_device_motorola_griffin
Version Information
Status: Stable
Created 2022-09-03
Last Updated 2022-09-03
i will installed 3.7.0 later and report here.
3.7.0 is working. thanks for silence update.
and just checked your LOS 19.1 is booting btw.
Hi, just wanna mention, moto mod manager app on your PE 10 is crash. But i cant test any mod coz i dont have it. I just disable the app, the problem is gone.
His build is almost the same as mine, just includes more debugging (eng instead of userdebug)
qwek said:
3.7.0 is working. thanks for silence update.
Click to expand...
Click to collapse
can you share the 3.7.0 links?
sxjice said:
can you share the 3.7.0 links?
Click to expand...
Click to collapse
Here's a link to everything related to griffin:
GitHub - Android-Link-Collections/griffin
Contribute to Android-Link-Collections/griffin development by creating an account on GitHub.
github.com
If you like it, you can share it and join our tg chat