[Q] 2nd init and kernel question - Barnes & Noble Nook Tablet

Good day folks,
Alright so now that 2nd init is the way to go for roms on the NT, I have a couple of questions that some of you more knowledgeable can answer.
My understanding of Init is basically a hook that takes over once the Kernel initiates the startup sequence that runs right after the first init.
And since NT has a locked bootloader based on means we can't change the kernel, and since the current kernel doesn't support HA, in essence if an ICS ROM is created it wont' support HA unless B&N Releases an updated Kernel/Rom based on ICS itself and which supports HA, correct? or can HA be enabled even if the kernel doesn't support it?
I'm looking into getting that Tablet for my wife, as she wants an e-reader and I want her to have a tablet with the full android experience, Kindle Fire's 8GB of storage and no expansion is why I decided to go with NT, and the budget is 300$ . So I've come to the conclusion that the NT is the best choice for the budget, was going to go with Iconia A100, but I've heard read bad things about it's screen, I don't really care about angled viewing as it's for a 1 person use/viewing, but i read that the NT has the better screen, especially that she plans on doing some reading on it, it's important she gets a good screen.
Thank you,
Rodi

Khar00f said:
Good day folks,
Alright so now that 2nd init is the way to go for roms on the NT, I have a couple of questions that some of you more knowledgeable can answer.
My understanding of Init is basically a hook that takes over once the Kernel initiates the startup sequence that runs right after the first init.
And since NT has a locked bootloader based on means we can't change the kernel, and since the current kernel doesn't support HA, in essence if an ICS ROM is created it wont' support HA unless B&N Releases an updated Kernel/Rom based on ICS itself and which supports HA, correct? or can HA be enabled even if the kernel doesn't support it?
[...]
Thank you,
Rodi
Click to expand...
Click to collapse
I think that's true. But I think a compatible kernel can be used, just like CM7 on Motorola devices: it's GB with the Froyo kernel. That mean that not all the feature will run out of the box, but maybe we can have a good rom.
Btw, it's early to talk about ICS right now.

Related

New gTablet On It's Way!

I just purchased a Viewsonic G Tablet from Amazon for $299...I have heard great things about it and have done some research. I was going to get a used ipad 1st gen for about the same price but I really want to root & do a lot of customizing more than what the ipad allows...
I have read the articles on rooting/flashing ROMS for it. I already have a OG Droid rooted running UD3.1.1 and loving every minute of it! I want to do something similar with the gTab.
I have looked into ROMS to flash onto the gTab & it seems two stand out the most: CM7 and VEGAn....I am somewhat familiar with CM7 since when I was looking for ROMs for my Droid it was one of the more popular ones. VEGAn I don't know much about but it seems the reviews are mostly high praise for speed & battery life...I would like options like on UD (overclocking, etc)
For anyone who has a G Tablet what ROMs are you using & why? Any others I should look into (I know about TnT Lite but it is retired so I prefer not to use that one. I am waiting for Honeycomb to become more stable before trying it...that is the main one I want to strive for!
Any other tips I should know about the G Tablet?
Thank You!
CM7 is a great (stable) 2.3.3 build for the GTab. It does offer some nice OC options (thanks to pershoot's kernels) as well as all of the customization you'd expect from a CM rom.
I ran Vegan Ginger for a while and IT IS FAST!!! I'm not entirely sure why I switched to CM7, but I've considered going back from time to time.
I was running the Calkulin+Clemsyn Froyo combo for a while (http://forum.xda-developers.com/showthread.php?t=1024120) and that ran very well for me also. It is a more stock looking ROM, with fewer standard Android options. That's not necessarily a bad thing, but as Android develops, 2.2 just isn't as exciting as it once was. That ROM also benefits from full hardware graphic acceleration; a feat that is still a work-in-progress for GB builds.
Overall, I like CM7. It's not quite as zippy as Vegan Ginger, and not as stable as the Froyo build.
My 2 cents.
EDIT: I remember now. I went to CM7 because it supports the Netflix app.
If your goal is to get to HC, when it's bugs are worked out, then it would benefit you to go with a 1.2 bootloader Rom. Brilliant Corners is the Vegan 5.1.1 ported to bootloader 1.2. Once you're ready for HC, you won't need to back out to stock in order to flash it...
It's not difficult to back out to stock, but why make more work for yourself if you don't need to.
TJEvans said:
If your goal is to get to HC, when it's bugs are worked out, then it would benefit you to go with a 1.2 bootloader Rom. Brilliant Corners is the Vegan 5.1.1 ported to bootloader 1.2. Once you're ready for HC, you won't need to back out to stock in order to flash it...
It's not difficult to back out to stock, but why make more work for yourself if you don't need to.
Click to expand...
Click to collapse
I heard of Vegan but not Brilliant Corners? Would you happen to have a link? I am all for making things easier so if it's a good ROM I will be more than willing to give it a go. Yes HC is my main wish for this tablet...why have a tab without honeycomb?
chef_w said:
CM7 is a great (stable) 2.3.3 build for the GTab. It does offer some nice OC options (thanks to pershoot's kernels) as well as all of the customization you'd expect from a CM rom.
I ran Vegan Ginger for a while and IT IS FAST!!! I'm not entirely sure why I switched to CM7, but I've considered going back from time to time.
I was running the Calkulin+Clemsyn Froyo combo for a while (http://forum.xda-developers.com/showthread.php?t=1024120) and that ran very well for me also. It is a more stock looking ROM, with fewer standard Android options. That's not necessarily a bad thing, but as Android develops, 2.2 just isn't as exciting as it once was. That ROM also benefits from full hardware graphic acceleration; a feat that is still a work-in-progress for GB builds.
Overall, I like CM7. It's not quite as zippy as Vegan Ginger, and not as stable as the Froyo build.
My 2 cents.
EDIT: I remember now. I went to CM7 because it supports the Netflix app.
Click to expand...
Click to collapse
+1 on this - I was about to type out the same thing basically... very happy with CM7. Haven't tried the nightlies yet, but I may soon.
mikespe said:
I heard of Vegan but not Brilliant Corners? Would you happen to have a link? I am all for making things easier so if it's a good ROM I will be more than willing to give it a go. Yes HC is my main wish for this tablet...why have a tab without honeycomb?
Click to expand...
Click to collapse
We're not allowed to post links ot other forums, but googling "Brilliant Corners G-Tablet" should get you where you need to be. it was a project of Roebeet, the developer of TNT lite, and a corroberator on Vegan 5.1.1. Basically, he took all of the older 1.1 roms that he worked on and ported them to the 1.2 dev branch, suspecting that 1.2 was going to be the future of development. Once you've found the forum that his rom's are now on, you can read up on some other posts to get other options for the 1.2 branch. Clemysn and Pershoot have been assisting in kernel development and tweaking. On 1.2, there are many more options of Roms to run, from Adam roms, Zpad, etc, since they use similar bootloaders.
I rooted my g with the Vegan 7 - VERY stable and easy to work with. The instuctions are on this site with the downloads
TJEvans said:
We're not allowed to post links ot other forums, but googling "Brilliant Corners G-Tablet" should get you where you need to be. it was a project of Roebeet, the developer of TNT lite, and a corroberator on Vegan 5.1.1. Basically, he took all of the older 1.1 roms that he worked on and ported them to the 1.2 dev branch, suspecting that 1.2 was going to be the future of development. Once you've found the forum that his rom's are now on, you can read up on some other posts to get other options for the 1.2 branch. Clemysn and Pershoot have been assisting in kernel development and tweaking. On 1.2, there are many more options of Roms to run, from Adam roms, Zpad, etc, since they use similar bootloaders.
Click to expand...
Click to collapse
Oh I'm sorry for asking for a link...I'm on so many forums and each one has different rules...actually after i asked for the link I did do a google search & found the site...the only thing is their rule of 3 posts before being allowed to download or post a new thread! I really don't know what to post yet since this part of android is new to me & I haven't explored enough to ask/comment on questions...LOL.
I have read that the Honeycomb ROM is VERY close to being upgraded to Beta which is awesome! I may just go right to HC...The 2 things I read that are "issues' are the G-sensor and accessing specific emails in Gmail. But it is supposed to be VERY quick & awesome....except for booting...I heard that was kind of slow...
We'll see. My gTab was shipped yesterday from Chicago & is coming to Western NY via Priority Mail so I am hoping before the weekend...
Thanks again for the help everyone!
It's only natural to ask for links, don't apologize. What's unnatural is not being allowed to help people by posting one
I'm not even sure I posted 3 times before using that site...if anything, just find a post and make a general comment, or ask a question. I'm over there 2, as are most people that either currently are, or were regular mambers of this site. they'll understand if you want to get your post count up so that you'll have access to the files.
As far as Honeycomb, there is suspicion that some of the issues are due to lack of OpenGL drivers from Nvidea. supposedly they can be correced in kernel development, but hte kernel base is different than anything else we are using right now. Clemysn even said it was difficult and gave him headaches.
for instance, the mail issue...it's been reported that there is a way to get the messages to show, but that you can't "see" where to touch to access it. the lack of OpenGL shading is not letting the graphics display properly. It's my hope, that once OpenGL is taken care of, that this will be a 100% working, stable release of HC for us. There isn't one Rom out yet for the g-tablet that has working, official hardware acceration support from Nvidea. HC would be the first, if anyone can get it working.
to use an analogy, what we have are 12 cylinder supercars, but the manufacture only provided a way to get spark to 4 of them.. some developers have figured out how to expand that to 8, but we're still not realizing the true potential of this engine. It may go as fast as it should, with tweaks, but it sometimes doesn't sound, or look very pretty doing it.
Go ahead up to HoneyComb Alpha3.0.1 by Roebeet and dev teams!
If you don't mind to have some bumps during the dev, flash to HoneyComb BoS Alpha3.0.1... sweetest thing...now I feel Gtablet worth for every penny I spent!
Search for that because I know this forum doesn't allow to post the full URL of other forums!

[Q] Best rom to use with lapdock?

Hey everyone, I just ordered one of those refurb lapdocks for $99 USD ($28 shipping to alberta
And I was wondering What was the best rom to use for a good lapdock experience
im using bell 2.3.4 cwm zip right now, is there a better rom/ webtop combination to use then stock?
In all honesty, the lapdock experience was rather shoddily put together by Motorola in the first place. Most ROMs do not come pre-packaged with webtop for this reason. I'm not so sure how effective trying the webtop on custom ROMs is without owning a lapdock myself (yet). From my understanding, HDMI mirroring has been a viable option for many. I hope to own a lapdock soon in hopes of contributing to improving the experience.
Im going to be using it mostly for very light word pro, music movies/TV shows and light browsing, Do I need a full debian distro for that or can I use the android apps with the lapdock for that stuff?
In your case, I would test drive purely stock ROM first to establish what to expect of the webtop environment. I don't think you would run into any problems with what you are going to use it for, but should you find something missing you might want to explore custom alternatives.
Be aware that most kernels available lock the CPU at its maximum speed in the lapdock environment. I can't remember if faux123 fixed this in his stopgap kernel or not, but that is the only big issue that comes to mind with custom ROMs
SirFork said:
In all honesty, the lapdock experience was rather shoddily put together by Motorola in the first place. / I'm not so sure how effective trying the webtop on custom ROMs is without owning a lapdock myself (yet). / I hope to own a lapdock soon in hopes of contributing to improving the experience.
Click to expand...
Click to collapse
???
Sent from my MB860 using XDA App
I'm using stock ROM, rooted, along with Webrop2sd. I have xfce4 launcher with Open Office, Gimp, and rdesktop. Couldn't be happier with my phone / PC.
Above configuration took a fair amount of trial and error to get stable and flawless, but I am thrilled with the result.
Td
tjdmobile said:
I'm using stock ROM, rooted, along with Webrop2sd. I have xfce4 launcher with Open Office, Gimp, and rdesktop. Couldn't be happier with my phone / PC.
Above configuration took a fair amount of trial and error to get stable and flawless, but I am thrilled with the result.
Td
Click to expand...
Click to collapse
I have a similar set up. If you take the time to set up your phone/lapdock like this, it's pretty cool stuff! My friends are amazed at the things this phone can do, then they look at thier iphone and shake thier head in disgust...LOL!
Have fun with it!
SirFork said:
In all honesty, the lapdock experience was rather deeply integrated with the stock ROM by Motorola in the first place. All non-stock-based ROMs do not come pre-packaged with webtop for this reason....
Click to expand...
Click to collapse
Fixed that for you.
I use the stock ATT 4.5.91 ROM. Everybody knocks Blur, but I can't give up webtop and some of the other niceties that come with the stock ROM.
stewartsoda said:
Fixed that for you.
I use the stock ATT 4.5.91 ROM. Everybody knocks Blur, but I can't give up webtop and some of the other niceties that come with the stock ROM.
Click to expand...
Click to collapse
Hi, I know this thread is a year old but im looking at rooting my atrix 4g and want a rom that works with the lapdock properly, do you still recomend the same rom or have you moved on?
cheers Joe
numnutss said:
Hi, I know this thread is a year old but im looking at rooting my atrix 4g and want a rom that works with the lapdock properly, do you still recomend the same rom or have you moved on?
cheers Joe
Click to expand...
Click to collapse
Posting the same question multiple times is against XDA rules.
Nothing has changed, or else there'd be a bunch of threads/posts about it. You still can't use native webtop (the modified ubuntu one) on anything but the original stock GB ROM.
ravilov said:
Posting the same question multiple times is against XDA rules.
Nothing has changed, or else there'd be a bunch of threads/posts about it. You still can't use native webtop (the modified ubuntu one) on anything but the original stock GB ROM.
Click to expand...
Click to collapse
I was hoping to get a reply from the 3 individuals who i had quoted, who have been in the same position as me in the past!

webtop hack - debian/ubuntu

nothing for linux hack webtop for Razr!?
I click this thread with such high hope... T_T
Just wait a couple of hrs......
I hope this means what I think it means...!!
!!!!!
YES.
Waiting for good news..
I am stinky with anticipation on this!
I've started to work on it. I should release a preliminary version tonight or tomorrow, it depends on my dear ****ty ADSL connection
Okay, I said "just wait a couple of hours" making you all think it would have been out today, but I was working on the overclock module so I've been a lil' bit late. I've posted it so that some other dev will examinate the situation and write the needed few lines of code for making it to work as expected.
Sounds very good Kholk, don't overrush... Your already working so much on custom tooling for the RAZR!!!
But you made me very curious!
b.o.n.s said:
Sounds very good Kholk, don't overrush... Your already working so much on custom tooling for the RAZR!!!
But you made me very curious!
Click to expand...
Click to collapse
Right? Both his o/c and his webtop app!
Wait, does that make me bi-curious??
Opening a thread for Webtop Mod, I wanna know what do you expect from it prior giving it to you, so I can set it as you all want.
is possible to have a dump of original webtop!?
some one have try the hack for Atrix/photon?
If you want a dump of the original webtop, download the Fastboot ROM in the ROMs thread.
The WebTopMODs for ATRIX/Photon shouldn't work as expected as they're meant to be used with Tegra2 (VFP), not with OMAP4. They're different.
Mine is meant to be used on OMAP4, its binaries are compiled with full OMAP4 support.
Chromium on Razr Webtop?
I've gone through your Netty enhancement (very impressive results, I might add!) and am thrilled with the results so far... BUT, upon installing Chromium using the apt-get functionality, I'm running into errors - something along the line of the application not properly reporting the timestamp back to the system. End result is that the application runs perfect for about a minute or two - then the system kills the app.
Have you had any success in getting Chromium running? That's by far my #1 want at the moment.
(And note - I'd post this in your development thread for the mod, but the system won't let me do so until I reach 10 posts... I think that's a feature.)

[Q] [OPINION CHECK] VERY VERY Fundamental FLAW in Secure boot chain -TODO or NOT do

>>>> 22Jan2012: linboothkvc v1.0 source released in my linboothkvc thread. It works successfully on Omap3 and Omap4 based devices including NookTab. And with minimal changes/love can work with any rooted arm based linux device <<<<
>>>> 17Jan2012: Kernel module SUCCEEDS on NookTab to reboot into NIRVANA - NO NEED to BREAK the default SECURE BOOT CHAIN and NOTE THAT EVEN THIS CAN WORK ON ANY ROOTED DEVICE and not just NT, with minimal love so ENJOY <<<<
>>>> 16Jan2012: My kernel module based path (linboothkvc) to running custom kernels and roms is almost done, except for a __small part__ to get it running on NT now - IF ONLY PEOPLE HAD WAITED ...., we could have reaped the potential benefit in future, Why not !!!! why not ....WHY NOT !?!?. NOTE that it can allow one to run custom kernel/roms WITH OUT MODIFYING ANY CRITICAL PARTITIONS provided one sets it up properly/appropriately. Source for beta version available in my linboothkvc thread, for the interested developers/experimenters for now ... <<<<
>>>> I may not respond to the posts on this thread currently, because I am trying to get a alternate option called linboothkvc using kernel modules up and running (which will occupy my free time), which AVOIDS the NEED for this flaw in the first place for most of the people out there (i.e Custom ROMS with different kernels). However over the weekends, I will go thro all the posts on this thread <<<<
>>>> 14Jan2012: Initial pre-alpha version of kernel module path based source code uploaded to my linboothkvc thread for those still interested to experiment
http://forum.xda-developers.com/showthread.php?t=1427610
<<<<
Hi All,
If you have been following my posts over the last few days
NOTE: To people frustrated with UART requirement - I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then do note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all. AND THAT By holding off now, we can _potentially_(Risk is always there) reap the benifit with next years NEXT GEN Nook Tab+ or what ever they call it.
a) I have implemented 2ndihkvc, which follows the same fundamental concept as 2nd-init, but achieves it in a simpler way (Needed because some of the calls used in original 2nd-init doesn't work on NookTab, or have unnecessary dependencies (in this given context, otherwise they are good in them selves) which can be avoided with my simpler method)
b) I have provided the NOP Bypass method of running a modified Ramdisk and also 90% a modified kernel, provided UART access is there.
c) There is still the power of linux KERNEL MODULES to EXPLOIT. (Haven't had time on that yet).
If you ask me, this should cover all category of people. Be it people who want to run custom Roms, or people who want to experiment with Kernel and or other low level stuff for the fun of it.
There is a 4th method which will allow one to achieve (b) above with out requiring UART access or even uSD (potentially . If one reads between the lines from all my posts till date, the answer is hidden in there. Only that I haven't spelt it out directly or in the face. The reason is because It is a fundament flaw (rather there are potentially two at two different levels - one relatively simple and one relatively bit more involved - One I know for sure, another I have to dig bit more) in the way things are done currently in the secure boot chain on this device as well as potentially other devices with same or similar SOC (and or different SOC but with similar boot chain s/w components.
SHOULD WE BE WASTING i.e providing a solution which uses it, when there is already 2ndihkvc and NOP Bypass over UART and also the Linux KERNLE MODULE ROUTE to cater to most peoples needs.
Because if we do, then even the Device manufacturers and their partners will come to know about it and can easily fix it in their Newer/NextGen devices. While if we withhold it for now, we may be able to get access to it on their Next generation Devices with hopefully Arm A15 core or .... (NOTE: Depending on the boot sequence ROOT access may or may not be required for this).
The reason I am asking now is because, few people are asking my help on certain things and the reality is I know that the concept for which they want my inputs/guidance, can be applied at a more fundamental level here (or even at the same level), but that I have not ventured into it because of my delimma above.
NOTE: People who wanted my inputs/guidance wrt uSD, you all know who you are, I know the flaw to achieve what you want to achieve, but it is more powerful than what you all are currently thinking of doing/ ristricting yourselves to (You all have one input/... in there wrt devices . Unless let me think thro further and see if something can be done differently, with out exposing the flaw I have in mind to help you achieve what you want, otherwise i.e if there is nothing else I can come up with, and in turn if you people experiment further and are able to come up with the solution on your own, I would suggest that hold off on it for few days, think thro all the implications keeping what I have mentioned in this thread, and then take a call one way or the other.
Please provide your thoughts on this after thinking thro the options already available on NookTab (root access, kernel modules, UART UBoot access and inturn 2ndihkvc and NOP Bypass or equivalents)
Based on all the feedbacks as well as bit more thinking from my side, I will take a call on this.
Forum moderators I know this is the development portion of the forum, but I wanted feedback from Developers also that is the reason why I have posted here. But beyond that I leave it to you, whether you want this to continue here or move it out.
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
cfoesch said:
UART access is not sufficient, as it is required during every reboot of the device if we wanted to have a custom kernel and ROM. This is simply an unacceptable state of affairs. (Say, my tablet turns off while on holiday, or at the airport. What then am I to do? Let is sit and wait off until I can get back home to my UART equipment in order to reboot?
The idea that the UART work around is sufficient is a nice one, however it is wrong.
---
Oh also, it's just a matter of time before they patch the u-boot in the Nook Tablet anyways... so it's not like this UART method is going to stick around forever anyways.
Click to expand...
Click to collapse
Hi
I understand the restrictions of UART access, but a lot of ROMS can be done with 2ndihkvc or equivalent methods and with out needing a Custom kernel. If someone is talking about Custom/New kernel for Android 4.0 (ICS). Then note my statement (in NOP BYPASS thread) on POWER of KERNEL MODULES in Linux, IT CAN BE USED TO ACHIEVE what you want to achieve, only that it requires bit more effort, which I or some one else has not put currently... thats all.
By holding off now, we can potentially reap the benifit with next years Nook Tab+ or what ever they call it.
Im not a Developer but I've got a few questions. NOP requires to open up your device, so I think probably 95% won't open their device for ICS and I think since the device had a dual core CPU we should get ICS roms. Now my actual question how does your 2init work or how do you install it on our device? But great work so far keep on.
Sent from my SGH-T989
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
PM me about the flaw, I'll see if we should have it outed yet or not (sorry guys, but if it's a decent exploitable flaw and we have other methods, I'm pretty sure I'm with hkvc on it.)
xdahgary said:
Just out the flaw now. Someone else might reveal it and you won't get the credit.
Don't you want a Wikipedia entry saying that you found this flaw? lol.
Click to expand...
Click to collapse
Not worried for 2 reasons,
a) It doesn't bother if my name comes or not. I am exploring just for the fun of exploring.
AND MORE IMPORTANTLY,
b) Actually I have already revealed the flaw in my NOP Bypass thread, indirectly, if only, one reads carefully all my lines as well as between them. Only that I have just replaced one or two of the steps with a different steps thats all for now.
If someone else find the same flaw, he will realise the same, if he reads my posts once again with his new knowledge.
What an awesome idea, we can have a root for the Nook Tablet+ or whatever else in a years time!
...
So, um... what do I do now with my Nook Tablet? It's a piece of garbage now, I guess, so, I'll just return it since it's still within the Holiday return period? I suppose I'll just have to wait for the Nook Tablet+ to have a custom ROM running on my Nook... ("But you can UART hack it!" ... *sigh* I've already explain that that is not sufficient. The UART hack is a stop gap, and should only be stopped at if that is the absolute only option available.)
And I mean no disrespect to xIndirect, but why should he be the lone gatekeeper of what exploits and hacks are out there for the Nook Tablet? I would rather see this exploit before making a decision as well, but I don't think it fair that someone should have privileged access to the exploit. Either release it to everyone or DON'T SAY ANYTHING IN THE FIRST PLACE.
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Indirect said:
cfoesch, I have no plans to be using the exploit shown for myself. I am not going to be the "lone gatekeeper" I just want to know what it is before I give my full opinion. Chill.
Click to expand...
Click to collapse
If you buy a plot of land and the seller has accidentally left seeds there and isn't coming back for them, do you grow a garden on your current plot of land, or do you decide not to plant them and hope that the next time you buy a plot of land they might forget some seeds again?
I would rather tend the garden I own than hope for a better plot of land with seeds I may never have.
Cheers!
-M
XDA member since 2007
Sorry if my post is offtopic, I just want to help with development.
My SE Xperia x10 came worh a locked bootloader and devs figured out how to make a bootable recovery (xrecovery) based on CWM, may be with an adaptation for the NT we can get the world of custom roms, even with locked bootloader this crappy phone got cuatom kernels by bypassing the bootloader, hope this give little ligth to you guys the real Developers.
If this post is garbage mods please delate it.
Sent from my BNTV250 using xda premium
Hello, I beleive if there is a software way to get ICS + maybe overclocking it should be tried first as this IS what most people are waiting for. That's the big dream they got. If someone knows how to implement that, then please by all means do so ..
P.S. you said so much where to look for the flaw in your posts that if I was a programmer from B&N I'd know where to look like everybody else. Assuming they are not complete morons they can already figure it out too. Can they plug the hole or not? Is it oversight or permanent design flaw ? We'll see. Best way to keep a secret is to " keep it secret " , ie not talk about it at all. Especially if soft mod ICS, hw acceleration and overclocking already available.
Sent from my LG-P500 using Much Love
First of all hkvc +1 for your efforts.
I voted yes, the NT developers can read between the lines in your posts as well.
Whats life without risks once in a while
Hi All,
I understand very well that even BN devs will be looking and potentially can figure out and fix it. That is the risk, but at one level I don't mind taking the risk and see if it works out to my/our advantage (i.e the bug being still open in a new device (From BN or any other Vendor)) or disadvantage(the bug is either way fixed).
Also the flaw can affect ANY DEVICE (Not just NOOK TAB) using similar secure boot chain not just NookTab, that is also one reason why I am bit wary of releasing the info or a implementation which uses it just like that.
I will share my finding with few people on the forum/outside in few days time so that even If I loose interest in this, there will be few people with the required knowledge (i.e if they haven't already figured out on their own by then (and released something or not ...)).
Also I haven't taken a final call on this yet. I am in a delima, so getting all your opinions also before I decide.
Time permitting I will also attack/explore the KERNEL MODULE PATH in a few days time, so that people don't have to depend on this flaw in the first place, but use the wonderful world of Linux Kernel Modules to achieve what they want.
LexS007 said:
Motorola Defy was locked bootloader too, may be to try and run port Defy bootmenu for Nook Tablet?
source: github.com/CyanogenDefy/android_external_bootmenu
Click to expand...
Click to collapse
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
absolutely YES, we r all xdaers, right hehehe. Thanks all devs especially hkvc for the efforts
hkvc said:
Hi,
With my modified 2nd-init (2ndihkvc), you can run bootmenu or any other user space mechanisms already on NookTab
Click to expand...
Click to collapse
It's very good. Thanks!!!
First off, not a dev but read religiously.
2nd, release it if the people who would take advantage of it agree. The rest of us say "great,woohoo!" But I must admit, I can't take advantage of it. But I certainly don't want to make a hardware uart to boot custom roms.
That being said, if its more complicated to install with a different method, that's fine. As long as it doesn't include a soldering iron.
But if it were easier to make a custom rom, or open up more capabilities of the kernal or whathaveyou, well that would attract more developers to make roms, etc. and so on and so forth.
Btw. Yes, exploit may exist if outedin a later tablet, but you found this one.... I have faith the next flaw will be found in the next one too.
A bird in the hand is worth two in the bush.
Posted from my B&N Nook Tablet... rooted of course!
jotekman said:
A bird in the hand is worth two in the bush.
Click to expand...
Click to collapse
I would say this summarizes everything I want to say on the topic.

[Q] Photon ICS/JB ROMs with Froyo kernel - why?

I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Dark Reality said:
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Click to expand...
Click to collapse
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
tatperson said:
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Click to expand...
Click to collapse
Try not to think of it in terms of Android versions, but rather, Linux Kernel versions. I believe it is because the 2.6.32 kernel is considered near perfect in terms of stability. Many Linux distributions use that kernel when they want to offer an extremely stable experience to their user base. For bleeding edge features but less stability, most distributions will use version 3+ of the Linux kernel. My guess is that since it is a standard of sorts because of being well-tested, it's just easier to rely on until we are provided with a later version. Just my two cents.
And why wait for Google release of Android 5.0? Why won't we do it ourselves.
tatperson said:
Because of the lack of what the devs need. We would need to wait for the official Atrix/Photon ICS leaks to get those kernels
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Click to expand...
Click to collapse
Well, that would make sense if we had the GB kernel, 2.6.35. We have the Froyo kernel, and, AFAIK, there's not even a Froyo ROM for the Photon. Why would there be? It's a Gingerbread phone.
Acvice said:
Try not to think of it in terms of Android versions, but rather, Linux Kernel versions. I believe it is because the 2.6.32 kernel is considered near perfect in terms of stability. Many Linux distributions use that kernel when they want to offer an extremely stable experience to their user base. For bleeding edge features but less stability, most distributions will use version 3+ of the Linux kernel. My guess is that since it is a standard of sorts because of being well-tested, it's just easier to rely on until we are provided with a later version. Just my two cents.
Click to expand...
Click to collapse
This makes sense, and I understand what you mean about Linux kernel versions. I understand the kernel is modular. Once when I was trying Ubuntu, I got a kernel update. Didn't affect anything, just had to reboot. Couldn't tell what it changed.
Also, I just noticed that AOKP Build 8 uses kernel 3.0.1, according to the screenshot on the left. Kinda torn on trying AOKP. On one hand, I'm not a "pink unicorns" kind of guy. On the other, the default wallpaper and status bar icons are nice. Another AOKP ROM featured a pretty cool textured status bar. But when I asked what AOKP had over CyanogenMod, the only answer I got was "swagger". In fact... well, that's a completely different topic. New Topic button, here I come. Hopefully the powers that be will see this as valuable conversation, not spamming up the boards...
//edit: AOKP screenshot lies, it uses the same kernel as the rest (screenshot is of another device, to be fair).
Dark Reality said:
Well, that would make sense if we had the GB kernel, 2.6.35. We have the Froyo kernel, and, AFAIK, there's not even a Froyo ROM for the Photon. Why would there be? It's a Gingerbread phone.
This makes sense, and I understand what you mean about Linux kernel versions. I understand the kernel is modular. Once when I was trying Ubuntu, I got a kernel update. Didn't affect anything, just had to reboot. Couldn't tell what it changed.
Also, I just noticed that AOKP Build 8 uses kernel 3.0.1, according to the screenshot on the left. Kinda torn on trying AOKP. On one hand, I'm not a "pink unicorns" kind of guy. On the other, the default wallpaper and status bar icons are nice. Another AOKP ROM featured a pretty cool textured status bar. But when I asked what AOKP had over CyanogenMod, the only answer I got was "swagger". In fact... well, that's a completely different topic. New Topic button, here I come. Hopefully the powers that be will see this as valuable conversation, not spamming up the boards...
Click to expand...
Click to collapse
AOKP has more features than cyanogen, and dont mind the pink unicorn. Its only a boot animation. And the AOKP team changed it here recently so it really doesnt look as obtrusive as it used to. CNA happens to be my personal favorite.
Well, I kept the boot animation from CM10, which I really like, so whatever ROM I stick with will probably just use that, unless I find something better.
Using AOKP now. A little annoying that I can't add lock slider items, but I can live with it. I see what they mean by swagger -- it's a toggle. I think it's like "Awesomeness Detection" in Rockband 2. That is, a toggle option that does nothing but confuses the user or makes them think they're doing something special. A placebo. But in reality there is no code to it. (I'm assuming about AOKP. Harmonix confirmed this about Rockband 2 -- 3 years after the game shipped.) But yeah, boot animation is fine for now (if a little small). And I'm actually using an AOKP wallpaper. It's the one with the shadow of the guy with the swords. Pretty awesome. (Is that what UnicornPorn.apk is? The wallpapers?)
Curious about CNA but I'm going to give AOKP a few days to settle in. Battery is a big thing for me though.
its actually a nvidia thing, i imagine a quick google search between linus and nvidia will tell ya how he feels about them ;P. (if you dont believe me the transformer lineup has 2.6.39 as its ICS kernel)
you can use any kernel version you want so long as it has all the proper stuff in it, the big thing most people overlook tho is not a lot of people look at the linux kernel and see all the commits. which if you are making kernels i highly suggest you do as there was some awesome battery saving stuff in 2.6.38 as well as some overall speedups.
the version number changing is used to signify a stable release. like 3.0 or 3.1, 3.2 etc.
its entirely possible (hell sometimes needed for some kernel sources) to take what the OEM provides take the corresponding linux kernel (in this case 2.6.32) and overlay the oem code. the reason why most dont do it is cuz it takes a long time. once you have the linux tree merged with your device specific files you can then backport patches much easier.. and at that point you could have a 3.x kernel using the same 2.6.32 stuff from the oem. wont help you overall on booting and fixing camera etc in ics but it will give ya plenty of improvements in just the kernel itself
Dark Reality said:
I've asked in two ROM threads and nobody seems to know... why do the ICS and JB ROMs all use the Froyo kernel? According to Wikipedia's article on Android history, ICS uses Linux kernel 3.0.1 and JB uses 3.1.10. However, both JB ROMs I've tried (Paranoid Android 1.95 and joker's CM10 0.1.1) use 2.6.32.9, which the article says is the Froyo kernel. Shouldn't we at least have the 2.6.35 kernel Gingerbread comes with? Why Froyo?
Just wondering. I'm not even sure why it matters, or if it matters. A fellow geek just thought it was weirder than having 102% battery when fully charged, so I figured I'd ask.
Click to expand...
Click to collapse
well from a laymen point of view i run and love most of th3bills roms(PORTS) from jokersax.com and considering my mopho(photon) is over a year old and getting almost 7000 antutu and 4000+ quadrant scores(which makes a new GALAXY NEXUS STOCK LOOK SLOW)...i don't care what kernel when im blazing like that.lol If its kicking azz dont fix

Categories

Resources