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! )
Related
edit: problem solved, patch attached. i also made an update.zip with the new kernel, see here.
there is a vncserver for android out there. so far it works fine, but there is no keyboard or mouse control for the host (android). this being a kernel limitation it can be patched. unluckily for us the patch is available only for the magic kernel version 2.6.23, not for the hero kernel version 2.6.27. i would kindly ask all the developers out there to have a look at the links below, and at least comment about the possibility to "port" (don't know the right expression) the patch to the heros kernel, or teknologists version. i can do the compiling and testing myself, just need someone to have a look at the patch, this is way beyond my skills for now. just compiled the teknologist kernel successfully, as my first compiled kernel ever!
the vncserver project
the patch
htc kernel source
teknologist kerne git
thank you in advance.
i think i managed to apply the patch manually, once i looked into it it turned out that there where only a few lines in 3 files, plus one completely new file, so it seemed pretty easy. yet to be tested, but first i figure out why the kernel won't boot at all, not even with teks sources...
so stay tuned for the kkernel, with full vnc support!
kendong2 said:
i think i managed to apply the patch manually, once i looked into it it turned out that there where only a few lines in 3 files, plus one completely new file, so it seemed pretty easy. yet to be tested, but first i figure out why the kernel won't boot at all, not even with teks sources...
so stay tuned for the kkernel, with full vnc support!
Click to expand...
Click to collapse
I thought Tek's kernel was based on the GSM hero kernel, not the CDMA one, which might be one of the reasons.
thecodemonk said:
I thought Tek's kernel was based on the GSM hero kernel, not the CDMA one, which might be one of the reasons.
Click to expand...
Click to collapse
uhm, i have only the gsm hero, no cdma in germay...
anyway, i forgot the --base 0x19200000 in my script, so the boot.img was faulty. it is working now, fbvncserver recieves keyboard inputs, but mouse does not do anything
maybe i can figure that out somehow, already posted in google code of the project.
i will release an update.zip this afternoon, containing the kernel and fbvncserver for easy installation, but now i gotta get some sleep
kendong2 said:
i will release an update.zip this afternoon, containing the kernel and fbvncserver for easy installation, but now i gotta get some sleep
Click to expand...
Click to collapse
who needs sleep anyway here's the kkernel-1.0
could one of the mods please set a [SOLVED] in front of the titel? if i am supposed to do this myself please tip me of how, i don't get it...
Great work. Will you share the Patch ?
kendong2 said:
could one of the mods please set a [SOLVED] in front of the titel? if i am supposed to do this myself please tip me of how, i don't get it...
Click to expand...
Click to collapse
You can do it editing your first post
i will, was going to do it tonight anyway, please be patient for a few more hours...
Lox_Dev said:
Great work. Will you share the Patch ?
You can do it editing your first post
Click to expand...
Click to collapse
patch is there. thx, i think i forgot to click on "go advanced" when i tried...
kendong2 said:
patch is there. thx, i think i forgot to click on "go advanced" when i tried...
Click to expand...
Click to collapse
Great thks a lot for the patch. I'll apply it to next community kernel release.
There's a fork of android-vnc that works without patching, android-vnc-server (both kbde and touch events).
rejser said:
There's a fork of android-vnc that works without patching, android-vnc-server (both kbde and touch events).
Click to expand...
Click to collapse
lol although it makes my work on the patch completely obsolete it sounds really good. i will look into that this evening, thanks for the hint.
nevertheless, it was interesting to find out how kernel-compiling and cross-compiling works, i actually had fun doing it
too bad, doesn't work for me
console output shows that keys are received, but no action
rejser said:
There's a fork of android-vnc that works without patching, android-vnc-server (both kbde and touch events).
Click to expand...
Click to collapse
thx for the hint, doesn't work for me either though... gonna try it with another kernel, but not before next week, having the gf over the weekend... no kernel baking then
Anyone know where can download the source code of nand version libhtcgeneric-ril.so? Thanks!
herrickwong said:
Anyone know where can download the source code of nand version libhtcgeneric-ril.so? Thanks!
Click to expand...
Click to collapse
There isn't a NAND version of this file.
I'm curious as to why you haven't PM'd me yet. Do you not want to work with the other devs?
arrrghhh said:
There isn't a NAND version of this file.
I'm curious as to why you haven't PM'd me yet. Do you not want to work with the other devs?
Click to expand...
Click to collapse
This user is working for The Independent Android Developer.
vinceweis said:
This user is working for The Independent Android Developer.
Click to expand...
Click to collapse
Yea, I'm well aware of that. Trying to get him away from the dark side and see the light .
(He's obviously got some kernel code chops... he got BLAC booting on NAND, pretty much on his own.)
arrrghhh said:
Yea, I'm well aware of that. Trying to get him away from the dark side and see the light .
(He's obviously got some kernel code chops... he got BLAC booting on NAND, pretty much on his own.)
Click to expand...
Click to collapse
Would love to have him here. The more, the merrier.
Herrickwong, Hasn't HYC always made all of his changes open and available for all to see? You should be able to find all of his commits.
As I understand it, NAND has been using their own hacked up RIL, they haven't adopted mine yet.
highlandsun said:
As I understand it, NAND has been using their own hacked up RIL, they haven't adopted mine yet.
Click to expand...
Click to collapse
on frx6 yes but our frx7 is using it (not yet released). Thanks to you who made it nand friendly. The old one was not friendly at all :-( ..
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.
hey people ,
can i edit the source code of stock htc m8 rom ?
Omar97 said:
hey people ,
can i edit the source code of stock htc m8 rom ?
Click to expand...
Click to collapse
If you have to ask this question, you probably don't know enough to do it.
What exactly do you want to accomplish?
redpoint73 said:
If you have to ask this question, you probably don't know enough to do it.
What exactly do you want to accomplish?
Click to expand...
Click to collapse
actually am not the one who gonna do this but a friend asked me for that and he wants to edit some things in the source code that's all
Omar97 said:
actually am not the one who gonna do this but a friend asked me for that and he wants to edit some things in the source code that's all
Click to expand...
Click to collapse
You can change whatever you want in the source code. That is one reason why HTC makes it available. But you need to know how to compile it, troubleshoot, etc.
I'm not a developer, so I can't talk any more specifically/technically than that. But that is the basic concept.
I'm also not sure if "source code" means what your friend thinks it means. Or is he just talking about modifying the ROM?
redpoint73 said:
You can change whatever you want in the source code. That is one reason why HTC makes it available. But you need to know how to compile it, troubleshoot, etc.
I'm not a developer, so I can't talk any more specifically/technically than that. But that is the basic concept.
I'm also not sure if "source code" means what your friend thinks it means. Or is he just talking about modifying the ROM?
Click to expand...
Click to collapse
he want to edit the source code of the stock htc's rom
Omar97 said:
he want to edit the source code of the stock htc's rom
Click to expand...
Click to collapse
Then I already answered the question.
redpoint73 said:
Then I already answered the question.
Click to expand...
Click to collapse
Thank you for your answer !! :good:
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