update-binary is included in the update.zip files to help process the edify install script.
I would like to look at the source code to verify something about the EMMC lockup/superbrick bug.
Would appreciate if someone could give me a pointer, preferably accessible online without needing to pull the source repository.
Ok, I found the source:
http://androidxref.com/source/xref/bootable/recovery/updater
Sfhub you could always ask in the irc channel where a couple devs hangout
Sent from my SPH-D710 using Tapatalk
sfhub said:
Ok, I found the source:
http://androidxref.com/source/xref/bootable/recovery/updater
Click to expand...
Click to collapse
You are a serious machine. You're on top of every leak, you even ask and answer your own questions. What can you not do? lol
Thank you seems so inadequate for all that give to this community. Know that your hard work is very much appreciated.
Related
I compiled aosp from source and flashed the rom on my phone through rom manager. I used the binary files from here: http://forum.xda-developers.com/showthread.php?t=1421188 and used the tweak to stop the recovery image from compiling. After flashing and upon booting I get this weird band going horizontal with the screen. I've attached a screen shot and was wondering if someone knew what I di or didn't do to cause this issue.
edit: I finally ran the exact script and pulled my prop files from an aosp rom 4.03 rom on my phone. If you're following the guide on cdma be prepared to extract the files you need or pull them from a git repose of a rom that's working on your phone. I tried the binaries posted in the cdma development section but they didn't work for me. Just some food for thought.
did you accept the agreement using the path for the source or what you did?
NICEGYPT said:
did you accept the agreement using the path for the source or what you did?
Click to expand...
Click to collapse
I'm not sure I know what you mean.
Any reason why this isn't in the Compile thread?
EddyOS said:
Any reason why this isn't in the Compile thread?
Click to expand...
Click to collapse
Is there a compile tread on XDA other than here: http://forum.xda-developers.com/showthread.php?t=1386615&page=15 ? I posted in the Q & A section because the moderator wanted people to post their questions here. I hope I can get some help with this issue either way. Thanks
I think in this case it might be worth posting in that thread, or at least link this thread in there as more people will then see the issue you've got
EddyOS said:
I think in this case it might be worth posting in that thread, or at least link this thread in there as more people will then see the issue you've got
Click to expand...
Click to collapse
Thanks.
10 char
Can someone teach me how to make a Kernel for GSM Just with Recovery and Root I know there's Doom's and Keirans But They Dont boot Correctly for me when I press Power only Stock and ICS does.
I know its hard once its done then I have Knowledge for the Future.
Making a kernel isn't a walk in the park. Just because you can compile something, doesn't make you a developer. I can compile CM7/9 fine but I haven't dared look at some of the source code yet.
Its something you need to learn slowly, try rom and app development first.
Sent from my R800i using Tapatalk 2
KeiranFTW said:
Making a kernel isn't a walk in the park. Just because you can compile something, doesn't make you a developer. I can compile CM7/9 fine but I haven't dared look at some of the source code yet.
Its something you need to learn slowly, try rom and app development first.
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
And where would you learn to do that?
Sent from my R800i using XDA
I'd say learn by doing. Grab some kernel sources from Github and try compiling them. If they don't compile, Google around and ask until you get it compiling successfully.
The first big challenge in kernel compiling is getting the right environment setup; getting the right OS/dependencies/toolchain is the first hurdle. Then look into the kernel sources and see what's going on.
Github is a great place to learn, as you can see people's changes and comments, to understand why they made changes.
Atarii said:
I'd say learn by doing. Grab some kernel sources from Github and try compiling them. If they don't compile, Google around and ask until you get it compiling successfully.
The first big challenge in kernel compiling is getting the right environment setup; getting the right OS/dependencies/toolchain is the first hurdle. Then look into the kernel sources and see what's going on.
Github is a great place to learn, as you can see people's changes and comments, to understand why they made changes.
Click to expand...
Click to collapse
Thanks Im not too Keen on Making a ROM all time or etc.
I just wanted to know how just for the future. Also My Xperia Bricked I have to go to O2 today lol.
I came across this guide, but I'm not able to understand it.
http://www.yumapk.com/How-to-update-B-N-NOOK-Simple-Touch-to-Android-4-4-Kitkat.html
Someone is able to verify and possibly explain it better?
Its a spam auto generated webpage. No volume key on our devices.
zonyl said:
Its a spam auto generated webpage. No volume key on our devices.
Click to expand...
Click to collapse
Too bad.
But after reading the webpage, it did look too good to be true.
Yeah when I used to moderate at AF we used to see this a lot, reading it shows it talking about HTC specifics such as RUU which stands for rom update utility and s-off which toggles signature verification off so you can write unsigned code to the system. Really people, the ONLY way that the os can ever be updated is if B&N released source, that's not going to happen and even if it did it still might not be enough because of e-ink specific code that might be under a NDA. :banghead:
OB
Sent from my SPH-D710VMUB using Tapatalk 2
Thanks for reply, we could not organize a petition to convince B&N to release the source?
helmen said:
Thanks for reply, we could not organize a petition to convince B&N to release the source?
Click to expand...
Click to collapse
I'm gonna say definitely no, because Barnes and Noble is breaking away from Nook. They don't seem to want to have anything to do with Nook anymore.
helmen said:
Thanks for reply, we could not organize a petition to convince B&N to release the source?
Click to expand...
Click to collapse
No need for a petition. Here is the source for v1.2.
Nook2 1.2
David0226 said:
No need for a petition. Here is the source for v1.2.
Nook2 1.2
Click to expand...
Click to collapse
Cool, but uh...
What do we do with this file?
thenookieforlife3 said:
Cool, but uh...
What do we do with this file?
Click to expand...
Click to collapse
A tgz file is a gzipped tar file (UNIX/Linux). I know Winzip will be able to extract it, though it takes two steps. Once you extract it you will have to source code for Nook firmware v1.2. What you do with that is up to you because it is way beyond me.
~David
PS The file would be much easier to work with in Linux or you could extract it to your Window machine using cygwin.
David0226 said:
A tgz file is a gzipped tar file (UNIX/Linux). I know Winzip will be able to extract it, though it takes two steps. Once you extract it you will have to source code for Nook firmware v1.2. What you do with that is up to you because it is way beyond me.
~David
PS The file would be much easier to work with in Linux or you could extract it to your Window machine using cygwin.
Click to expand...
Click to collapse
Yeah, I know about the whole .tgz file thing. Been working in this department for a couple years.
But I also don't know what anyone's going to do with that source code!
thenookieforlife3 said:
Yeah, I know about the whole .tgz file thing. Been working in this department for a couple years.
But I also don't know what anyone's going to do with that source code!
Click to expand...
Click to collapse
I don't know either. helmen asked about the source code, I knew where to find it, so I posed it. Perhaps helmen or others might be able to do something with it.
David0226 said:
I don't know either. helmen asked about the source code, I knew where to find it, so I posed it. Perhaps helmen or others might be able to do something with it.
Click to expand...
Click to collapse
I think he wanted Barnes and Noble to post a source code for the Nook Touch to use Android 4.4.
Am I right, or did I misunderstand?
thenookieforlife3 said:
I think he wanted Barnes and Noble to post a source code for the Nook Touch to use Android 4.4.
Am I right, or did I misunderstand?
Click to expand...
Click to collapse
Well, perhaps I misunderstood. There certainly isn't source code to use Andriod 4.4 on the Nook as B&N never intended that. However some android developers might be able to take the most recent source code, which I posted, and figure out a way to make a new version of Android run on it. (I personally think 4.4 would be a real stretch, but if somebody could figure out the eInk driver situation, 2.3 might be a possibility.) I don't know if the source for the eInk drivers would be in the source code (I doubt it) but if they are, someone might be able to use this.
~David
David0226 said:
Well, perhaps I misunderstood. There certainly isn't source code to use Andriod 4.4 on the Nook as B&N never intended that. However some android developers might be able to take the most recent source code, which I posted, and figure out a way to make a new version of Android run on it. (I personally think 4.4 would be a real stretch, but if somebody could figure out the eInk driver situation, 2.3 might be a possibility.) I don't know if the source for the eInk drivers would be in the source code (I doubt it) but if they are, someone might be able to use this.
~David
Click to expand...
Click to collapse
Ah, I see. Well, thanks for the conversation and the source code (not that I can do much with it, though - ADB and modifying the framework-res.apk are more fun for me! )
Hello fellow XDA members, I recently purchased a Le Pro 3 and a Le S3 during the flash sale and would like to use Cyanogenmod on my devices. I was wondering if anyone on this forum has ever ported a ROM before as I have not, and only know about the CM porting guide and opensource.le.com for the kernel source. If anyone has any tips or would like to assist me in porting CM13 to the Pro 3 please reply to this thread or PM me. Thanks, and let's hope LeEco releases the source soon!
Love to help but this isn't my department ????. But we should probably see more support in a couple more days once they start arriving here
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
dr4stic said:
Just out of curiousity, what exactly had you hoped to achieve with this post? If you're interested in porting, ideally you should at least be able to build a rom (for another pre-existing device)... and then you'll have to hunt down help on the CM forums and then eventually IRC.
Talking about this on XDA is pointless.
Click to expand...
Click to collapse
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
limitlesscodes said:
The purpose of my post was to see if anyone in the XDA community had experience porting a ROM to a new device, and if they'd be interested in helping me. I have read through a few guides and understanding building a ROM, but am struggling to find what I must "merge." From what I've found so far, I'll need to edit/merge the directories in /system/libs and edit the kernel?
Click to expand...
Click to collapse
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
dr4stic said:
No, it's far more complicated than that. You'll need a copy of the kernel for sure, but you'll also need a device definition. You can use the op3's device as a template, it's probably the best example of an msm8996 device you can have.
You really should be checking into the CM forums. CM people are pretty uppity about not supporting things on XDA. They also don't tend to help. Even as a developer I find it difficult sometimes to get their attention. Your best bet is to go to them if you want their help. Good luck.
Click to expand...
Click to collapse
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
limitlesscodes said:
Yeah, I understand. I also found out that it will be about a month until LeEco officially releases all of the source.
Click to expand...
Click to collapse
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
dr4stic said:
Where did you get that information from? They "accidentally" released kernel sources not too long ago and seemingly withdrew it. I got a copy of them and that's what I've been working with. I don't have a device to verify if any of it works.
Click to expand...
Click to collapse
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Not a lot. I've identified the CAF tag the sources are based on and have been working to separate the relevant LeEco mods from the less relevant ones. I've also been attempting to remove the leeco specific things from the drivers that i'm keeping since they're a horrible mess and CM won't be able to make use of them anyway. I've also been finding the appropriate open versions of the drivers and taking the latest ones instead.
The mods from LeEco seem to be a mess, the dmesg output I got from a user on the chinese model (the x720) had segfaults from the modifications just after boot. The logcats are so full of errors I was unable to get the user to send me a full logcat from boot.
Interestingly enough, the chinese system rom looks like it came from a Le Max2. This makes sense since it's LeEco's first msm8996 device, and the Le Pro3 is the second one. I imagine the kernel sources work across a number of the 8996's.
Can you send me the link to where you got the open drivers.
limitlesscodes said:
I asked on this forum. Also my S3 is coming tonight, and my Pro tomorrow. I have a copy of the Pro 3 kernel source as well but as of now don't know what to do. What have you worked on so far?
Click to expand...
Click to collapse
Please share the sources.
Sent from my LEX727 using Tapatalk
ceo.mtcl said:
Please share the sources.
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
here
limitlesscodes said:
here
Click to expand...
Click to collapse
Thank you so much!
limitlesscodes said:
here
Click to expand...
Click to collapse
This is not a International version? Its USA version? Where is the International source code?
Here's a mega mirror in case the drive link goes down.
https://mega.nz/#!7Ek3HYaB!1H0WibOjwlg1P0vaaJ2qcrAAsl-PjruB9-_X1ECqfnw
Wish i could help more, but it looks like the kernel source is in there too, perhaps that means a fully functional cm13 rom that works AT LEAST as well as the stock rom. VERY EXCITE!
+1
I'm also waiting for CM13.
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
:good:
csyann said:
I'm also waiting for CM13.
Click to expand...
Click to collapse
giogio1 said:
:good:
Click to expand...
Click to collapse
Waiting for CM 14.1
http://opensource.le.com
I'm having trouble building Lineage15.1, I believe it might be an error when building the kernel but i have replaced the source for the kernel and continue to receive errors. Could anyone help me narrow down the issue?
This is a paste bin link to the log file
https://pastebin.com/RwnNHshR
VulKenZ said:
I'm having trouble building Lineage15.1,.........
Click to expand...
Click to collapse
I've never built a ROM myself but, there's a handful of guides that are helpful and to obtain some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3551484
https://forum.xda-developers.com/showthread.php?t=3655407
https://forum.xda-developers.com/showthread.php?t=3735674
https://forum.xda-developers.com/showthread.php?t=2455005
https://forum.xda-developers.com/showthread.php?t=2223690
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Thank you
Ibuprophen said:
I've never built a ROM myself but, there's a handful of guides that are helpful and to obtain some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3551484
https://forum.xda-developers.com/showthread.php?t=3655407
https://forum.xda-developers.com/showthread.php?t=3735674
https://forum.xda-developers.com/showthread.php?t=2455005
https://forum.xda-developers.com/showthread.php?t=2223690
Good Luck!
Click to expand...
Click to collapse
Thank you for the quick reply and guides! I have successfully built LineageOS before but only recently have I been having this problem with Ninja. My heap size is plenty big enough and i have tried almost every other common fix with ninja.