I have a device tree but it is giving a error of bootctrl when building it need help getting it to work please trying to build a twrp recovery here is a link to the device tree https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk
If any one knows how to fix a device tree help plz I have a rom and recovery built just need this to finish them all up
I have a rom and a twrp built just need to get the mount points in device tree working with error bootctrl and help
svoc said:
I have a rom and a twrp built just need to get the mount points in device tree working with error bootctrl and help
Click to expand...
Click to collapse
I don't know how to fix mount points but I can help test once it's all finished. I wish I knew more than I do
Txdude35 said:
I don't know how to fix mount points but I can help test once it's all finished. I wish I knew more than I do
Click to expand...
Click to collapse
I got to find some one that knows how help
Related
Hello everyone,
I am a newbie here, I want to compile Cyanogenmod from source and I learned CyanogenMod wiki.
Unfortunately I didn't find my device, ZTE v889d. I have downloaded the Cyanogenmod source, the wiki tells
cd ~/android/system/device/manufacturer/device-name/
./extract-files.sh
Click to expand...
Click to collapse
However I didn't see device/zte/v889d, so I don't know what to do. I searched the github, there's no such file either.
Is there any guide for me to do this? Thanks in advance.
josephok said:
Hello everyone,
I am a newbie here, I want to compile Cyanogenmod from source and I learned CyanogenMod wiki.
Unfortunately I didn't find my device, ZTE v889d. I have downloaded the Cyanogenmod source, the wiki tells
However I didn't see device/zte/v889d, so I don't know what to do. I searched the github, there's no such file either.
Is there any guide for me to do this? Thanks in advance.
Click to expand...
Click to collapse
You have to find a device tree for your device...or make one
I can't help with making one as I've never made a device tree...
But for finding one just Google ZTE v889d github...if someone has made one it should pop up...if you can't find any...then your out of luck and will have to make your own..
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
You have to find a device tree for your device...or make one
I can't help with making one as I've never made a device tree...
But for finding one just Google ZTE v889d github...if someone has made one it should pop up...if you can't find any...then your out of luck and will have to make your own..
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. I can't find device tree on github, it seems that I have to create one, is there any guide for this?
josephok said:
Thanks for reply. I can't find device tree on github, it seems that I have to create one, is there any guide for this?
Click to expand...
Click to collapse
I'm no pro either, but perhaps you could find a device that is close to your model that is cm supported and then look into its vendor tree on github. Doing this will allow you to see what you need to pull from your firmware to start a tree. Or if the devices are close enough you might even be able to barrow some of the supported devices pre existing tree.
Hope this helps a little
Sent from my HTC Rezound using Tapatalk 2
wildstang83 said:
I'm no pro either, but perhaps you could find a device that is close to your model that is cm supported and then look into its vendor tree on github. Doing this will allow you to see what you need to pull from your firmware to start a tree. Or if the devices are close enough you might even be able to barrow some of the supported devices pre existing tree.
Hope this helps a little
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
Thanks
I did wonder did you get it to work for you..?
Could try my guide to give it a nother try here: http://forum.xda-developers.com/showthread.php?t=1935162
If its not too late:
http://forum.xda-developers.com/showthread.php?t=2010281
How to create device tree.
garwynn said:
AOKP builds straight from repo sync. If you're having trouble with it please let me know which jf device you're trying for and I'll ask the maintainer if not me.
Click to expand...
Click to collapse
hi sir, i am building for huawei honor (u8860).
https://github.com/DESHONOR/android_device_huawei_u8860
and i don't use my own release tool folder but the one from source...
i am building AOKP KK and here is the error i have:
"ERROR: couldn't find <type 'property'> in build.prop"
thank you.
desalesouche said:
hi sir, i am building for huawei honor (u8860).
https://github.com/DESHONOR/android_device_huawei_u8860
and i don't use my own release tool folder but the one from source...
(i don't know what is a jf device)
thank you.
Click to expand...
Click to collapse
Please post your question in the appropriate forum. I will try to find the right home for yours later and point in the right direction if no one else beats me to it. Thank you.
Sent from my LG-LS980 using Tapatalk
garwynn said:
Please post your question in the appropriate forum. I will try to find the right home for yours later and point in the right direction if no one else beats me to it. Thank you.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
i am the only one unofficial maintener for that device... and i couldn't find any working answer yet.
Moved to appropriate forum as a new thread. Hope this helps you get the answers you need.
So that others can help can you please explain what you are trying to build?
(AOSP, CM, AOKP, etc...)
Thanks and good luck!
OK, did some looking from where I moved this from and I see you're looking to build AOKP, correct?
Are you trying to do the initial bringup for this device?
Or do you know if any other AOSP projects support this device?
I'll look at your device tree but you're going to need a kernel (and/or source) and vendor tree as well.
If you don't have these it's not going to build.
Edit: Looks like your device tree is designed for CM at the moment.
Is CM building OK for this device?
Thanks!
Hey everyone
If any of you know, then can anyone please provide me with the links for
1. Device tree
2. Kernel
3. Vendor
For a500f?
Any help is highly appreciated
here is what u need bro,google is your friend.greeeeetz!!!!
Device Tree - https://github.com/MSM8916-Samsung/android_device_samsung_a5ltexx
Kernel - https://github.com/emceethemouth/kernel_a5ltexx
Vendor etc - https://github.com/MSM8916-Samsung/proprietary_vendor_samsung
hope this helps u,have fun!!!!!
-CALIBAN666- said:
here is what u need bro,google is your friend.greeeeetz!!!!
Device Tree - https://github.com/MSM8916-Samsung/android_device_samsung_a5ltexx
Kernel - https://github.com/MSM8916-Samsung/kernel_samsung_e5lte
Vendor etc - https://github.com/MSM8916-Samsung/proprietary_vendor_samsung
hope this helps u,have fun!!!!!
Click to expand...
Click to collapse
Thank you so much!
no problem,glad to help.
@-CALIBAN666- The github page for the kernel says that it is for e5lte
oops,sorry.ive added right link in my post above.
-CALIBAN666- said:
oops,sorry.ive added right link in my post above.
Click to expand...
Click to collapse
@-CALIBAN666- Could you check the vendor sources once again as well?
How can I generate device tree for a device ? I have SM-A710F and I couldn't find device tree for it so I want to create it by my own ?
Hi to all. I created a porting of MIUI 8 coming from Nexus 5 for d802. It remains only in bootanimation and got bootloop... Can anyone help me?
Here are the logs: https://drive.google.com/open?id=0B2CDSAt5MIakTTlOc3Nic2R6aDg
From which base are you creating 7 or 6?
shaneel1491 said:
From which base are you creating 7 or 6?
Click to expand...
Click to collapse
I'm porting miui 8 with cm13 based kernel with some modifies
Maybe it's having to do with nexus 5 modules, where some are not the same as G2, and maybe that is causing problems?
Don't we need specific binaries and blobs for our device?
shaneel1491 said:
Maybe it's having to do with nexus 5 modules, where some are not the same as G2, and maybe that is causing problems?
Don't we need specific binaries and blobs for our device?
Click to expand...
Click to collapse
I used at least all were kernel, i putted only somethig of n5... What i can do now? Must i do some sources? I don't know what i can do.
matteo0026 said:
I used at least all were kernel, i putted only somethig of n5... What i can do now? Must i do some sources? I don't know what i can do.
Click to expand...
Click to collapse
Maybe try following this and see, I haven't ever built a ROM, so I don't know what to do
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
shaneel1491 said:
Maybe try following this and see, I haven't ever built a ROM, so I don't know what to do
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
Click to expand...
Click to collapse
Yes, i'm the official manteiner of XOSP for this device! I can try to compile! Thank you so much!
Just remember this is aimed at miui 7 so point the source to your miui 8 code
Bro if I could also ask you a question, how do I go about building Android 7 for G2? Are there any good guides on the web, I don't even know where to start...
shaneel1491 said:
Just remember this is aimed at miui 7 so point the source to your miui 8 code
Bro if I could also ask you a question, how do I go about building Android 7 for G2? Are there any good guides on the web, I don't even know where to start...
Click to expand...
Click to collapse
I don't know... I tried to build cm14 and i got it, resolving a lot of building issues, but it work only wifi...
Anyway, i looked in the README MIUI patchrom's page, and i'm blocked at the command:
Code:
cp ../honor/makefile
i don't know what i must do... i tried to replace honor with d802 (name of my device folder) but terminal give me this error:
Code:
cp: missing destination file operand after '../d802/makefile'
Try 'cp --help' for more information.
[email protected]0-15ISK:~/patchrom/d802$
matteo0026 said:
I don't know... I tried to build cm14 and i got it, resolving a lot of building issues, but it work only wifi...
Anyway, i looked in the README MIUI patchrom's page, and i'm blocked at the command:
Code:
cp ../honor/makefile
i don't know what i must do... i tried to replace honor with d802 (name of my device folder) but terminal give me this error:
Code:
cp: missing destination file operand after '../d802/makefile'
Try 'cp --help' for more information.
[email protected]:~/patchrom/d802$
Click to expand...
Click to collapse
i looked through the readme and maybe you missed something
the readme says:
Code:
cp ../honor/makefile .
maybe you missed the .
according to the error message your cp command has no destination where to copy this file and the dot seems to be the destination in this case
Maybe I'm wrong
this is just an idea
Blumdum said:
i looked through the readme and maybe you missed something
the readme says:
Code:
cp ../honor/makefile .
maybe you missed the .
according to the error message your cp command has no destination where to copy this file and the dot seems to be the destination in this case
Maybe I'm wrong
this is just an idea
Click to expand...
Click to collapse
Very likely the solution, cause he didn't specify a location to copy to. Also is the directory you're working from named d802?
shaneel1491 said:
Very likely the solution, cause he didn't specify a location to copy to. Also is the directory you're working from named d802?
Click to expand...
Click to collapse
Yes... Anyway... I completed a fullota ROM and tried to flash... But bootloops. Here's the log
https://drive.google.com/open?id=0B2CDSAt5MIakTTlOc3Nic2R6aDg
(Read patchrom log)
I can say that you were wrong base rom. Because you're so complicated life, you have to fill the power command after boot animation. You were wrong some trivial step, you have to thunder back.
P.S It is an exceptional work, the finished project looks.
Sorry for my bad english
CHIRCA_ROBERT said:
I can say that you were wrong base rom. Because you're so complicated life, you have to fill the power command after boot animation. You were wrong some trivial step, you have to thunder back.
P.S It is an exceptional work, the finished project looks.
Sorry for my bad english
Click to expand...
Click to collapse
Why wrong base ROM? Which ROM must i use? I would like to use aosp pure or cm13... Anyway, after resolved some problems, i got another logcat...
https://drive.google.com/file/d/0B2CDSAt5MIakVm1xeVJFZlVTbms/view?usp=drivesdk
Dev @LinhPhi9x94 from XdaVN team patch rom complete Miui v8 for lg g2 f320
thinhx2 said:
Dev @LinhPhi9x94 from XdaVN team patch rom complete Miui v8 for lg g2 f320
Click to expand...
Click to collapse
Ok thanks i contact him
Wait D802
Hey guys i found it https://github.com/linhphi9x94/MIUI8_Patchrom_LG-G2/blob/master/README.md how to build miui 8 for g2. İf any developer try it must see work. Because xdavn try it and working f320.
Emresaygin said:
Hey guys i found it https://github.com/linhphi9x94/MIUI8_Patchrom_LG-G2/blob/master/README.md how to build miui 8 for g2. İf any developer try it must see work. Because xdavn try it and working f320.
Click to expand...
Click to collapse
Oh wow sources yet patched for g2! Thank you so much i try this afternoon!!!
matteo0026 said:
Oh wow sources yet patched for g2! Thank you so much i try this afternoon!!!
Click to expand...
Click to collapse
İf you know build rom i am ready to test for d802 bro. This source for f320
HI everyone, I need help to compile a custom recovery for a Motorola One Macro it has a Mediatek Helio P60 i tried doing it but the device doesn't have any recovery partition if someone can guide me or help me compiling it that would be great
0
Seppppx said:
It doesn't matter if it has or hasn't got a recovery partition.
To get more info about making the twrp device tree you can look here.
thx sir I will take a look and see what i can get done
Click to expand...
Click to collapse
@Kratos574
A/B devices don't have a dedicated /recovery partition
jwoegerbauer said:
@Kratos574
A/B devices don't have a dedicated /recovery partition
Click to expand...
Click to collapse
I see, Is there any possible way to develope a Custom recovery for this device or is it impossible or DIfficult?