Hi
As there is no proper custom recovery for lg g3 f460k snapdragon 805 variant i decided to build one. I have come very close but face this error as shown in the attached image. Pls provide your insight on this.
Code:
error could not load device tree image '/home/pnnam/android/system/out/target/product/tiger6/dt.img
thats normal as lollipop doesnt use that file anymore. you should be more worried about why it hasnt compile dt.img, becuase that is needed for recovery
winxuser said:
thats normal as lollipop doesnt use that file anymore. you should be more worried about why it hasnt compile dt.img, becuase that is needed for recovery
Click to expand...
Click to collapse
yea , I realized that after searching thru the internet. Any idea why it isn't compiling dt.img ?
Pannam said:
yea , I realized that after searching thru the internet. Any idea why it isn't compiling dt.img ?
Click to expand...
Click to collapse
No sorry wouldn't have a clue. I'm not that skilled
Sent from my LG-D855 using XDA Free mobile app
winxuser said:
No sorry wouldn't have a clue. I'm not that skilled
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
thats okay. i think it has something to do with mkbootimg_tools . Just trying to figure out how it actually works
HTML:
https://github.com/xiaolu/mkbootimg_tools
add this to your local_manifest.xml
Code:
<project path="device/qcom/common" name="cyanogenmod/android_device_qcom_common" remote="github" revision="cm-12.0" />
it will add to your build the mkbootimg and will be able to bump it automatically
for anything you can read this
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
it's old (cm12 unofficial) but still useful
manups4e said:
add this to your local_manifest.xml
Code:
<project path="device/qcom/common" name="cyanogenmod/android_device_qcom_common" remote="github" revision="cm-12.0" />
it will add to your build the mkbootimg and will be able to bump it automatically
for anything you can read this
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
it's old (cm12 unofficial) but still useful
Click to expand...
Click to collapse
i have that already.
well normally dt.img is made in build process normally.. you sure everything is in place for the device?
manups4e said:
well normally dt.img is made in build process normally.. you sure everything is in place for the device?
Click to expand...
Click to collapse
i was actually able to make recovery for other devices i.e 801 variant from the tutorial you have posted but not this one. The mkbootimg.mk is the file responsible for dt.img (i assume). Does it need any specific tweaking ie path etc ? mkbootimg.mk is the same i have that u have in your tutorial.
I am using a prebuilt kernel as i ran into trouble while compiling it in cwm process. The guide you shown me is compiling kernel so i think it has something extra than stock prebuilt kernel.
maybe is something in cwm source code that prevents dt.img from being built?
manups4e said:
maybe is something in cwm source code that prevents dt.img from being built?
Click to expand...
Click to collapse
This is the link to mkbootimg.mk . i have a prebuilt bt.img can you tell me how to link it directly? As cwm build is not picking it up.
https://github.com/CyanogenMod/android_device_lge_g3-common/blob/cm-12.0/mkbootimg.mk
normally it goes in "out/target/product/d855/" (for example) i mean the normal out directory
manups4e said:
normally it goes in "out/target/product/d855/" (for example) i mean the normal out directory
Click to expand...
Click to collapse
hey bro! how u doing ?
okay i built the recovery but it stucks in the fastboot screen .
everything has passed just wont go to recovery. check attachement .
if you look closely there are some errors.. like "ERROR: len= 64" or "could not found lcd_primary_mode"....
boot into TWRP and check if you have a LAST_KMSG that would be more helpful
manups4e said:
maybe is something in cwm source code that prevents dt.img from being built?
Click to expand...
Click to collapse
Have you got device_qcom_common
Sent from my GT-I9305 using XDA Free mobile app
winxuser said:
Have you got device_qcom_common
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I had it while building it for cwm recovery. I have niw shifted to omni rom and not sure if it is still required. Still I'll give it a try. Lets see. Thnx for the reminder.
I think i will make a new thread.
Related
Okay so that we have a development topic (due to lack of a forum) for both phones which are basically the same.
What's going on the Galaxy W side:
Arco68 is porting CM9 to the phone
KezraPlanes is trying to port CM7 to the phone and making a custom stock ROM.
What's going on the Exhibit 2 side:
**placeholder text**
Try to keep general discussion to this topic I will post:
This will be a development topic.
So I was finally able to solve my issues with downloading the CM7 sources. Apparently it was in issue with the manifest.xml file which can be easily solved by doing this:
Add this in the beginning of the file where all the other equal references are:
<remote name="github-https"
fetch="https://github.com/"
review="review.cyanogenmod.com" />
Click to expand...
Click to collapse
And replace the original line near the end of the file with this:
<project path="prebuilt" name="CyanogenMod/android_prebuilt" remote="github-https" />
Click to expand...
Click to collapse
This fixes the download sources issue.
So r u gonna help us w/ cm9 an recovery
sent from my exhibit 2 greatness
KezraPlanes said:
So I was finally able to solve my issues with downloading the CM7 sources.
Click to expand...
Click to collapse
I'm not sure what issue you are referring to or what file ?
I have trouble with their instruction on the "building kernel from sources page"
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j8
is not working for me.
Do you suggest to modify the repo file or is that another procedure you are talking about ?
Nilpotent said:
I'm not sure what issue you are referring to or what file ?
I have trouble with their instruction on the "building kernel from sources page"
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j8
is not working for me.
Do you suggest to modify the repo file or is that another procedure you are talking about ?
Click to expand...
Click to collapse
dswaggz was referring to this thread for the Exhibit 2.
My Galaxy W should arrive any day now (*impatient*) and I have an Exhibit 2. I think it'll be easy to cooperate on developing for both phones. I don't see anything in your first post about what's already working. (The phone is rooted, but beyond that, if you have any updates I'll look at post #1 )
Is it ok to PM you?
Nilpotent said:
I'm not sure what issue you are referring to or what file ?
I have trouble with their instruction on the "building kernel from sources page"
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j8
is not working for me.
Do you suggest to modify the repo file or is that another procedure you are talking about ?
Click to expand...
Click to collapse
Depending on what error you are getting, it might work for you. It solved everything for me but I was using "repo sync -j16" (I was also following one tutorial from their wiki).
In my case the error made me unable to download the sources past 93%
Hi Guys,
Just have the phone for a week now, and i gotta say i really like this phone!
Had a LG Optimus Me before, but the Galaxy Wonder is so much more and better.
Hope there will be a CM 7 or 9 very soon.
Good luck with developping!
I was going to release a deodexed-rooted-arcokernel'd stock ROM today because I've figured out how to do it while helping Arco68 with ICS, but unfortunately the laptop I'm using right now (which is not the computer I use for dev'ing) corrupts the ROM everytime I build it.
I might bring back to my hometown (where I spend my weekends) my broken-screen laptop, connect it via HDMI to the TV in the living room and create the ROM there, since I have to go to my rented apartment to get some stuff anyway.
I'm aiming at a release tomorrow at the most.
Edit: I'm a ****ing idiot. I'm guessing it's going to work now,
Will it work for the exhibit 2
sent from my exhibit 2 greatness
The best of luck...make it work I would like to try it....BTW what will be required to flash it...ClockworkMod ?
Sent from my GT-I8150 using xda premium
Is there already a overclock kernel for our device?
Cheers, Gerard
TuxBrothers said:
Is there already a overclock kernel for our device?
Cheers, Gerard
Click to expand...
Click to collapse
Off course the heritage of CM7
Sent from my GT-I8150 using xda premium
andynroid said:
The best of luck...make it work I would like to try it....BTW what will be required to flash it...ClockworkMod ?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Any recovery.
The ROM is installing fine but apparently hangs. Apparently it's the Dalvik's fault, but I don't remember messing with it.
Gonna work a little on it today.
Hopefully it will work for my device here in Malaysia...Have attached my firmware SC
Sent from my GT-I8150 using xda premium
Sent from my GT-I8150 using xda premium
dswaggz said:
Will it work for the exhibit 2
sent from my exhibit 2 greatness
Click to expand...
Click to collapse
I can't promise anything, but from what I know, it should.
KezraPlanes said:
I was going to release a deodexed-rooted-arcokernel'd stock ROM today because I've figured out how to do it while helping Arco68 with ICS, but unfortunately the laptop I'm using right now (which is not the computer I use for dev'ing) corrupts the ROM everytime I build it.
I might bring back to my hometown (where I spend my weekends) my broken-screen laptop, connect it via HDMI to the TV in the living room and create the ROM there, since I have to go to my rented apartment to get some stuff anyway.
I'm aiming at a release tomorrow at the most.
Edit: I'm a ****ing idiot. I'm guessing it's going to work now,
Click to expand...
Click to collapse
Testing volunteer here
fender90 said:
Testing volunteer here
Click to expand...
Click to collapse
I'll second that, I need to jump back to stock on my T679 anyways so if you have any thing to test run before I do that feel free to let me know.
PS: woo first post!!!1!!111!!one
matt_6288 said:
I'll second that, I need to jump back to stock on my T679 anyways so if you have any thing to test run before I do that feel free to let me know.
PS: woo first post!!!1!!111!!one
Click to expand...
Click to collapse
@matt_6288: the T679 is the T-Mobile USA Exhibit II. KezraPlanes' ROM is for the Galaxy W (a.k.a. I8150). You can't use it as-is, but we're working on ROMs for both.
Well thanks to my mentor Arco68, I have my hands on the newest Samsung FW for the Galaxy W which makes me re-start my work from scratch. But now that I'm working on a decent computer, I should be able to do things much faster.
***this thread is made strictly for development purposes so that any developer can join up and help the development of a working port of this for the Galaxy Wonder***
Okay at this point in time I'm trying to make an hard port (the easy way) of CM7 by trying to make a generic build of CM7, then bundling it with Arco68's kernel and afterwards fix the libs and whatnot.
I've already managed to compile the generic build and am now playing around to create a working .ZIP file.
Update 1 : ZIP install fine, but no boot, at least for now. Time to play a little
Update 2: Hm, weird. I was convinced this was gonna work. I'm most likely missing some Samsung patches and **** that generic builds don't have. Going back to the drawing board.
Update 3: While I go into theories about how I should go about CM7, I'm also downloading the sources for Oxygen, because I prefer it over CM7. That way I can study both.
Right on bring it on !
Sent from my GT-I8150 using xda premium
KP, as always I can test whatever firmware you are working on, even if it doesn't boot on your device I can try on mine to see if it works
fender90 said:
KP, as always I can test whatever firmware you are working on, even if it doesn't boot on your device I can try on mine to see if it works
Click to expand...
Click to collapse
Same for me!
Inviato dal mio GT-I8150 usando Tapatalk
i appreciate it and waiting for good news....
i can help by trying it on mi thone
KP....any updates
Sent from my GT-I8150 using xda premium
Since hard porting was getting me nowhere, I decided to try the hard way and I'm currently making a vendor and device config manually. I'm basing it on YardE's awesome work on the Galaxy S Plus front. At least it saves me some work, but there is still a whole lot to do.
Sent from my GT-I8150 using XDA App
Will u make this compatible with the exhibit II
via Dan swagger
How's it going KP? We're starving for updates
Got stuck, waiting for feedback from Arco.
KezraPlanes said:
Got stuck, waiting for feedback from Arco.
Click to expand...
Click to collapse
For a moment when I saw KP replied to this thread I went "yes! yes! he made it!" and when I read your post I just went "aaaawwwwwww...."
Sorry, could not help it. LOL!
It seems Arco's been busy too.
wiseless said:
For a moment when I saw KP replied to this thread I went "yes! yes! he made it!" and when I read your post I just went "aaaawwwwwww...."
Sorry, could not help it. LOL!
It seems Arco's been busy too.
Click to expand...
Click to collapse
yeah me too
Waiting Mode : ON
Really really am hungry for this thread's updates.
SyzwnFrzRdz said:
Really really am hungry for this thread's updates.
Click to expand...
Click to collapse
me too, i can't wait for this thread's updates
Any updatee?
Kezra i want to try by using this http://www.droidforums.net/forum/steel-droid/196475-guide-how-build-your-own-rom-cm7-source.html guide
DarthJonathan said:
Kezra i want to try by using this http://www.droidforums.net/forum/steel-droid/196475-guide-how-build-your-own-rom-cm7-source.html guide
Click to expand...
Click to collapse
Good luck with that considering we have zero basis to work on and building a ROM from source. If you achieve the miracle of building a 'vendor' folder that actually compiles, tell me. That tutorial assumes you have a vendor config that works for your device.
Anyways good luck. I'm still trying to make a working vendor folder.
KezraPlanes said:
Good luck with that considering we have zero basis to work on and building a ROM from source. If you achieve the miracle of building a 'vendor' folder that actually compiles, tell me. That tutorial assumes you have a vendor config that works for your device.
Anyways good luck. I'm still trying to make a working vendor folder.
Click to expand...
Click to collapse
He says i should take out the make files?? but how?? where is our device setup folder where i can excecute the . setup-makefile.sh command? THX A TON KEZRAAA
EDIT : and the have not the vendor for I9001 either so we are starting from zero i do what i can to help you
DarthJonathan said:
He says i should take out the make files?? but how?? where is our device setup folder where i can excecute the . setup-makefile.sh command? THX A TON KEZRAAA
EDIT : and the have not the vendor for I9001 either so we are starting from zero i do what i can to help you
Click to expand...
Click to collapse
You might be able to find those files at Arco's Github.
https://github.com/arco/android_device_samsung_ancora
The above link does contain a file called " setup-makefiles.sh"
You might also want to look at the following:
https://github.com/arco/android_vendor_samsung_ancora
I am not sure if this is what you are looking for, but Hopefully this will help you.
This is the latest ClockworkMod recovery compiled by me. Everything you are doing is on your own risk.
There is a warning "No file_contexts". But ignore this, it's normal and won't give any problems.
non-touch version (6.0.4.4)
Download img file (for flashing with ADB shell)
Download tar.md5 file (for flashing with Odin)
touch version (6.0.3.6)
Download img file (for flashing with ADB shell)
Download tar.md5 file (for flashing with Odin)
Tutorials
How to flash ClockworkMod with Terminal Emulator
How to flash ClockworkMod with Odin
Thanks to:
CyanogenMod Team for the sources
arco68 for his sources
buffo1987 for his nice tutorial and his help
I've been wondering too... But this kind of stuff is REALLY dangerous... This like sorta messin' with the system partition so i'm not sure...
I'm back to OneOfAKind v21
Hey I'm using the clockworkmod touch v6.0.3.2 unreleased by @miki2o, the cwm has "pink screen" bug but it works perfectly. You two can discuss for fixing it I think
Sent from my GT-I8150 using xda app-developers app
ipromeh said:
Hey I'm using the clockworkmod touch v6.0.3.2 unreleased by @miki2o, the cwm has "pink screen" bug but it works perfectly. You two can discuss for fixing it I think
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Is this the touch recovery version?
Maybe I can fix the pink screen bug. But first I have to know if I could brick my phone and if it is right to use the required data from arcos cm10.1 branch or if they should be from the cm9 branch and so on..
I would try it out but I don't know if I brick the download mod too with flashing a bad cwm. I have no experiences about that for now.
sdfee said:
Is this the touch recovery version?
Maybe I can fix the pink screen bug. But first I have to know if I could brick my phone and if it is right to use the required data from arcos cm10.1 branch or if they should be from the cm9 branch and so on..
I would try it out but I don't know if I brick the download mod too with flashing a bad cwm. I have no experiences about that for now.
Click to expand...
Click to collapse
Man if you don't wanna risk, you shouldn't have released this.
Before releasing, you MUST test it on your hands.
miki2o said:
Man if you don't wanna risk, you shouldn't have released this.
Before releasing, you MUST test it on your hands.
Click to expand...
Click to collapse
Yes. I want test it by my self first. But my question for now is if I could damage my phone with a bad builded recovery.
miki2o said:
Man if you don't wanna risk, you shouldn't have released this.
Before releasing, you MUST test it on your hands.
Click to expand...
Click to collapse
lol he isn't releasing it yet dude
sdfee said:
Yes. I want test it by my self first. But my question for now is if I could damage my phone with a bad builded recovery.
Click to expand...
Click to collapse
If the image is corrupted,then yes.
hotheabilly said:
lol he isn't releasing it yet dude
Click to expand...
Click to collapse
Sorry, I'm tired. I didn't read it correctly
Now everything is clear. There is only the bug ipromeh told.
@arco68: Thank U Sir for your very very great support and development for our device! :good:
Now I want to help the Galaxy W users with things I can do. Building CWM is one of these things. I want to support this recovery. But there is only one bug at version 6.0.3.2 (touch and non-touch) and I don't know how to fix it. I think that it would be a "10-minute thing" for you.
It is only a graphic bug because the whole texture and graphic is pink, but you see the buttons and all functions are working as they should. Is this because of the /recovery/graphics.c ? How to solve it?
It would be very nice and helpful to hear something from you about that.
I tried to build cwm for ancora but I failed due to a curropted graphics.c . Now I found that mine is corrupted too so I 'm trying to build a new one
The only problem is that I hav'nt a sgw !
And I have a suggestion , please try to build the cwm with zImage of both 3.0 , 3.4 and one time with 2.6 . It may be related to kernel too !
alireza7991 said:
I tried to build cwm for ancora but I failed due to a curropted graphics.c . Now I found that mine is corrupted too so I 'm trying to build a new one
The only problem is that I hav'nt a sgw !
And I have a suggestion , please try to build the cwm with zImage of both 3.0 , 3.4 and one time with 2.6 . It may be related to kernel too !
Click to expand...
Click to collapse
Thanks for your help.
I'm an android dev beginner and I don't know what you mean. I don't know what a zImage is and how to build it. I'm using the builder from CWM because I only have a Windows computer.
If you want me to test something of your builds, I will do so. But I will learn the things how it works too
sdfee said:
Thanks for your help.
I'm an android dev beginner and I don't know what you mean. I don't know what a zImage is and how to build it. I'm using the builder from CWM because I only have a Windows computer.
If you want me to test something of your builds, I will do so. But I will learn the things how it works too
Click to expand...
Click to collapse
Could you please try once again with the cwm 6.0.3.0 ( Arco's ) withoit a custom graphic.c ?
alireza7991 said:
Could you please try once again with the cwm 6.0.3.0 ( Arco's ) withoit a custom graphic.c ?
Click to expand...
Click to collapse
I tried now. But the same bug!
Originally Posted by alireza7991<br />
Could you please try once again with the cwm 6.0.3.0 ( Arco's ) withoit a custom graphic.c ?
Click to expand...
Click to collapse
<br />
<br />
I tried now. But the same bug!
Click to expand...
Click to collapse
Once again with the old 5.0.5.4 ?
alireza7991 said:
Once again with the old 5.0.5.4 ?
Click to expand...
Click to collapse
I can't find a download link for the 5.0.5.4 CWM. It's everywhere down
Maybe a try with the stock recovery could help. But there is no downloadlink for it too.
I think that arco knows the solution, but he seems very busy. I can't ask him for help because he doesn't accept PMs from "normal" users.
sdfee said:
I can't find a download link for the 5.0.5.4 CWM. It's everywhere down
Maybe a try with the stock recovery could help. But there is no downloadlink for it too.
I think that arco knows the solution, but he seems very busy. I can't ask him for help because he doesn't accept PMs from "normal" users.
Click to expand...
Click to collapse
Using stock recovery as base will limit you only to non touch version !
The only way you can get a working cwm 6.0.3.2 is to clone repo from arco and sync it to lastest cwm from CM 10.1 m3 branch !
alireza7991 said:
Using stock recovery as base will limit you only to non touch version !
The only way you can get a working cwm 6.0.3.2 is to clone repo from arco and sync it to lastest cwm from CM 10.1 m3 branch !
Click to expand...
Click to collapse
Okay. It sounds very intresting. But I did never something like that. How can I synch my cloned repo from arco with CM? Where can I find the right branch? There are so many repos at https://github.com/cyanogenmod
Am I wrong there?
I have only a Windows computer so I don't know how many steps of building it I can do.
Sorry for my helplessness. It is so many to learn. But I want to learn it step by step.
heres the file for cwm 5.0.5.4
sdfee said:
Okay. It sounds very intresting. But I did never something like that. How can I synch my cloned repo from arco with CM? Where can I find the right branch? There are so many repos at https://github.com/cyanogenmod
Am I wrong there?
I have only a Windows computer so I don't know how many steps of building it I can do.
Sorry for my helplessness. It is so many to learn. But I want to learn it step by step.
Click to expand...
Click to collapse
First you need a linux distro ( you may use a virtual machine too )
Then you need Linaro Tool Chain ( or any other toolchains ) + Android SDK . now follow instructure from buffo to builf cwm.after building I think you will have a 6030 then you need to merge cm10.1 branch to get a 6032
Hi!
As a lot of people out there, I'm really waiting for one thing: a cifs.ko kernel module to allow my ouya add CIFS/SMB network shares.
It should be interesting to compile it, because we could have all our stuff around our network (in my particular case, on my NAS).
I found out, that there is a possibility to compile it from the Ouya kernel's public source: https://github.com/ouya/ouya_1_1-kernel as it has the cifs code on github, so I supose that it shouldn't be hard to compile it (I'm not so good compiling the kernel).
Is anyone working on this module?
I'm waiting for this module aswell
So... nobody is working on it? :crying:
I'll whip up a kernel with support tomorrow.
Sent from my SCH-I545 using Tapatalk 4 Beta
invisiblek said:
I'll whip up a kernel with support tomorrow.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Any news on this?
Kaos2K said:
Any news on this?
Click to expand...
Click to collapse
I *had* compiled a kernel with support for it but when i synced the current commit now it wont compile cleanly....nor will reverting back to the previous commit fix it ( comes up with the same error )
HTCdemon said:
I *had* compiled a kernel with support for it but when i synced the current commit now it wont compile cleanly....nor will reverting back to the previous commit fix it ( comes up with the same error )
Click to expand...
Click to collapse
Ouch. I wish i had the knowledge to help you with that :/
Hopefully someone much more savvy than I can put this together
moku160 said:
Hopefully someone much more savvy than I can put this together
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2347214
done
IncognitoMan said:
http://forum.xda-developers.com/showthread.php?t=2347214
done
Click to expand...
Click to collapse
thx this helps
IncognitoMan said:
http://forum.xda-developers.com/showthread.php?t=2347214
done
Click to expand...
Click to collapse
nice! any plans for adding init.d support as well? i need my usb stick to be auto mounted at startup or otherwise my link2sd-apps won't work...
I have a question...
is it possible to install cif modules without use a custom rom?
Hi I have working on this some time and it should work, I'm not a real developer and don't have big knowledge. This is ported from Wileyfox porridge.
I'm posting this here because I don't have a PC to try to build on it (I have single core celeron with 512mb RAM, belive me or not) and also my phone's bootloader is still locked because I don't want to break warranty yet because I had some problems with very low R/W speeds. So if there is anyone who know what should be done and would like to try to build ROM or help with device tree, please feel free to do that.
NOTICE: If you have model other then 8GB K350nds you should edit values of partition sizes in BoardConfig.mk Better solution will be if I known difference in size of partitions for each model, and even than I'm not sure what attribute from /proc/cmdline I should compare to get it right (in init_mm1v.cpp)
Device tree https://github.com/ProfessorWoland/android_device_lge_mm1v
You'll also need common tree https://github.com/LineageOS/android_device_cyanogen_mt6735-common
About kernel if you try to build ROM:
Kernel source is published by LG here http://opensource.lge.com/osSch/list?types=ALL&search=k350
But also there is kernel on Lineage OS repo https://github.com/LineageOS/android_kernel_cyanogen_mt6735
It should work also if you just add muse6735_m1v_m_defconfig file from your kenel source to /arch/arm/configs . Or at last i think that is our _defconfig because it's only one with anything which can be related to our device (m1v)
I bought this phone cheap so I'm going to try to compile today
joeeboogz said:
I bought this phone cheap so I'm going to try to compile today
Click to expand...
Click to collapse
Nice, but I doubt it will work at first try since I made this without any real knoweledge..
And there is still problem where we can't flash anything without soft brick because of some signature or whatever else checker. Probably in lk (little kernel) partition so we need a good reverse engineer to make check function allways true and don't kill phone in process..
joeeboogz said:
I bought this phone cheap so I'm going to try to compile today
Click to expand...
Click to collapse
Any success?
Professor Woland said:
Nice, but I doubt it will work at first try since I made this without any real knoweledge..
And there is still problem where we can't flash anything without soft brick because of some signature or whatever else checker. Probably in lk (little kernel) partition so we need a good reverse engineer to make check function allways true and don't kill phone in process..
Click to expand...
Click to collapse
Sent from my LGE LG-K350 using XDA Labs
bynamnshan said:
Sent from my LGE LG-K350 using XDA Labs
Click to expand...
Click to collapse
You wanna say something?
Does it works?
Santiago Pucheta said:
Does it works?
Click to expand...
Click to collapse
Not in a useful way, it compiles ROM but we don't have a way to test it, however even if we do I think it wouldn't work since even from kernel sources from LGE it can't compile working kernel idk why, since kernel doesn't have anything to do with tree, I tested it via 'fastboot boot ___' command.