Stock Kernel [boot.img] - Google Pixel Guides, News, & Discussion

Introduction
Hey guys! I've noticed that a lot of people have been asking lately about where they can find the stock kernel. I know everyone could just download the factory image and get it themselves, but I'm also aware that not everyone can do that at a moment's notice. So I've decided to upload just the boot.img that you can flash via TWRP or fastboot! So this is the boot img you can get directly from Google, no mods or anything!
The Goods
https://1drv.ms/f/s!AiNBPlglrGbG9wEl_Y1dinGAGJah
Inside the link there will be folders with the build number and month it was released so you can know what you're downloading.
Enjoy!

You're right that it's not a big deal to get this yourself but little download links like this can really save someone in a low reception pinch. Thanks.
To head off future questions I would recommend including the build number from which this came as well as the correlating Android version number and intended market (US, Europe, VZW, etc.). Definitely don't say "it's the latest" since that will become outdated every month.

cntryby429 said:
You're right that it's not a big deal to get this yourself but little download links like this can really save someone in a low reception pinch. Thanks.
To head off future questions I would recommend including the build number from which this came as well as the correlating Android version number and intended market (US, Europe, VZW, etc.). Definitely don't say "it's the latest" since that will become outdated every month.
Click to expand...
Click to collapse
Thanks for the tip. I renamed the folders inside the link so they will contain the month and the build number!

Related

[Q] Why can't we compile our own 2.2 OS?

Let me start by saying I'm fairly new to Android, and that this probably should go in a general Android forum, but since I'm a Fascinate user, this seems appropriate to me. I've searched, but haven't found a real explanation, and I'm not one to take things as fact without a reasonable explanation.
So it seems like everyone is waiting for an official 2.2 release for the Fascinate, flashing 2.1 ROMs but not capable of upgrading to 2.2+; but I'm wondering why we can't just compile our own OS for our phones? Android is a Linux-like OS, and I know Linux users would never stay on an old version if a newer (better?) version was available. I'm talking down-and-dirty tweak-every-option-by-hand Slackware here. Is the source available for download? If so, why can't we do something with it? Is something in the phone completely locked and unhackable? Is it the fear of having a $500 paperweight? Is it difficult to regain Verizon network connectivity?
Again, forgive the noob question, and thanks in advance for any help you can give me!
http://forum.xda-developers.com/showthread.php?t=792986
http://forum.xda-developers.com/showthread.php?t=883004
http://forum.xda-developers.com/showthread.php?t=882946
There is currently work being done by jt, birdman, and the other skew of developers trying to develop a working AOSP version of 2.2/2.3. The biggest struggle that they have encountered was the RIL (Radio Interface Layer) binaries. Samsung produced some bogus complex proprietary binaries with no properly working source code. Because this phone is CDMA and not GSM, we can't simply use galaxy s files.
Anyways, the point is that there is work being done to bring it to our phone. They have a working AOSP 2.1 that is currently in alpha stage. Jt basically built his own RIL for this phone to get it working.
If this RIL works, we may end up with 2.3 sooner than later.
eulipion2 said:
Let me start by saying I'm fairly new to Android, and that this probably should go in a general Android forum, but since I'm a Fascinate user, this seems appropriate to me. I've searched, but haven't found a real explanation, and I'm not one to take things as fact without a reasonable explanation.
So it seems like everyone is waiting for an official 2.2 release for the Fascinate, flashing 2.1 ROMs but not capable of upgrading to 2.2+; but I'm wondering why we can't just compile our own OS for our phones? Android is a Linux-like OS, and I know Linux users would never stay on an old version if a newer (better?) version was available. I'm talking down-and-dirty tweak-every-option-by-hand Slackware here. Is the source available for download? If so, why can't we do something with it? Is something in the phone completely locked and unhackable? Is it the fear of having a $500 paperweight? Is it difficult to regain Verizon network connectivity?
Again, forgive the noob question, and thanks in advance for any help you can give me!
Click to expand...
Click to collapse
You obviously have not searched hard enough, as this has been discussed in many places. I would suggest you start by searching this forum (edit: or seeing the links and posts above).
I will say, however, that recent achievements by (edit: the developers mentioned above) have made your suggestion quite possible. If you want to get a taste of what is to come, see the aosp alpha sticky located in the development section. The rom still has bugs, but it is a giant step forward for the Fascinate.
Sent from my Galaxy-S Fascinate
Florynce said:
http://forum.xda-developers.com/showthread.php?t=792986
http://forum.xda-developers.com/showthread.php?t=883004
http://forum.xda-developers.com/showthread.php?t=882946
Click to expand...
Click to collapse
^^^^^
10char
I must add/point out that the work these guys are doing could easily pave the way for Cyanogenmod- and other well-featured roms to be compiled/ported and used on Fascinate as well.
I've read the above links, but they didn't really quite answer my question. I guess I'm wondering why a Linux-based OS isn't acting/being treated like a Linux-based OS.
Let's say I go out and buy a new computer today. I want to put Linux on it. I get the machine home, download my distro of choice and make an install cd. As I'm installing, I configure the installation either for my specific hardware or I can use a generic profile if my hardware isn't listed.
Now say a new version of the Linux kernel comes out. I can upgrade without having to wait for a version for my hardware. Or if I install MyDistro v1 when I get my machine, and MyDistro v2 comes out the next day, I don't have to wait for someone to develop a version to work with my hardware.
So my question is more of a why can't we upgrade our distro like other Linux variants? Is it because there's no generic replacement for the Samsung RIL? If I were to download the source and do a generic build, or even a specific one, I wouldn't be able to install it because...?
Sorry to be a pain, but I genuinely have no clue. Again, thank you for the insight!
2.2 will boot on the I500 just nothing works. If you would like to help http://opensource.samsung.com/
The source code can be found there. Please feel free to help the development along.
I suggest you read through the reply's to your question and pay special note to those bringing up the RIL as that seems to be the biggest hurdle right now.
I think maybe the answer you are looking for is that it is possible to do it, it's just extremely difficult because Samsung's open source is very shoddy and isn't based on AOS, which is what is used for most other phones.
Since the developers don't have a build that works, they have to work from the ground up with AOS and get every last feature on the fascinate working without using Samsung's code (TouchWiz, widgets, etc).
The links they gave you explain most of it but you have to sift through the posts. There is a dev named jt (amongst others) who is working on a ROM that is upgradable based on AOSP and it looks very promising.
edit: It's also worth noting that when I say "not based on AOS" I mean that it is proprietary software used by Samsung-only phones and is not coded by Google. It still, of course, is based on Android OS. It would be akin to a ROM coded by Samsung for their phones rather than generic ROMs that could be downloaded by other phones.
Perfect, thanks!
Try thinking of it as buying an Ubuntu laptop from dell. Sure its " Ubuntu" but not stock. It so full of bloat and badly written drivers that aren't supplied openly for the user that it would be hell trying get the latest version of ubuntu to run on it.
Sent from my SCH-I500 using XDA App
For clarification.... so I can wrap my brain around this. Is this situation kinda like having bought a new computer that's running an os, but has no installed device drivers and nowhere to download them from, so they have to be written by hand?
Edit: that last post came thru while I was writing this one, I think it basically answers my question...
So what the devs on here are trying to do is develop a "generic" profile that can work on our phone (as well as others?), creating a solid base to allow users to upgrade and change at-will without having to wait for official releases?
See, that's the part I'm having a hard time with. No generic profile built into the OS to use in the absence of a hardware specific one?
LoverBoyV said:
Try thinking of it as buying an Ubuntu laptop from dell. Sure its " Ubuntu" but not stock. It so full of bloat and badly written drivers that aren't supplied openly for the user that it would be hell trying get the latest version of ubuntu to run on it.
Click to expand...
Click to collapse
On a sidenote, I bought a Dell netbook witih Ubuntu. Didn't waste time with Ubuntu, but I chose it because I didn't want MS to get money from a license fee. Installed Mac OS X on it the day it arrived
Ya know, I tried to do the same thing with my inspiron 1525 notebook, with snow leopard 10.6.3 since I have a spare hard drive. Spent a whole day with numerous guides, trying this n that. Got it to actually boot to the desktop once, bit as I was putting the drivers in, it went into KP and from that point on, I could never even reinstall back to the desktop again.
Well, Samsung is giving us a simple/reliable update to Froyo with unique functionality, as soon as possible.
Source: (Twitter, About 12pm 1/2/2011 from Samsungtweets via Cotweet - http://twitter.com/Samsungtweets/samsung-usa )
Samsungtweets We are working to make the Android 2.2/Froyo upgrade available to all U.S Galaxy S owners as soon as possible.
Samsungtweets We want Galaxy S owners to have simple/reliable upgrade. We r running tests due to complexity/unique functionality
EDIT: gave more specific time and source of tweets. Post is meant to be objective, without definition of ASAP for this context.
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
Well, Samsung is giving us a simple/reliable update to Froyo with unique functionality, as soon as possible.
Source (Twitter, 6 hours ago):
Samsungtweets We are working to make the Android 2.2/Froyo upgrade available to all U.S Galaxy S owners as soon as possible.
Samsungtweets We want Galaxy S owners to have simple/reliable upgrade. We r running tests due to complexity/unique functionality
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
I'm not sure if this is meant to be funny or not haha. Are those recent tweets?
Sent from my SCH-I500 using XDA App
They seem to post the same things over and over, of course this is also because people constantly ask when is froyo coming, and every time they say there is no definite date. It is coming soon that that is all they will say; yelling, moaning and crying isn't gonna make it come any sooner, just sit back and it will eventually come.

Kine One(m) and original Kin One ROM

Does anyone know where to get the latest rom from the original KIN run? The one that still includes the option for exchange email accounts?
I've tried google, and usually my googlefu is strong but it seems not with this. the latest build seems to be v1 build 2814.0
Also, from what I can see it would work, I'd just have to turn off the cloud stuff using the hidden menu afterwords... or am I wrong?
Thanks
This is actually one of the main problems. If we could get our hands on an actual rom from one of the KINs we would be in pretty good shape, and would be more likely to make progress.
Have you found any rom for a kin? If you have please let us know.
No, although I was only looking for an older rom build.
I'm probably going to call Verizon to try and get them (badger them) to give me an older ROM, since the phones are basically worthless to me without the Exchange email client... Unfortunately, when I looked up the Kin specs, all the sites I checked listed that feature.
Right now I'm hoping that I can either get an older rom on the phone (somehow) or that the newly announced HP Veer comes out on Verizon (also unlikely, since its Tech specs page only lists gsm and not cdma, etc).
I'll see what I can do about getting a ROM first though.
Well, I tried Verizon, and then Sharp.
After the hours on the phone, it appears that:
a.) Verizon could give me an older ROM, if I could somehow get ahold of the right person... since they reason they gave me for not doing it is "As the original equipment manufacturer, Sharp wouldn't let us do that."
b.) Sharp immediately says they have nothing to do with the phone after making it, and only Verizon can help me out.
So with that being a dead end, I can only see 2 options:
1.) Get the info from nvidia that lets us create roms for their tegra stuff (kin one is tegra as well, I believe) and then dump the current rom using their tools and modify it. I don't really think this will be possible, since I'm not an OEM, but I find it more likely than #2.
2.) Get ROM builds and tools from Microsoft. Given how... microsoft... Microsoft is, I really doubt this will be possible.
So, next week I will try #1 (calling them, if possible), followed by #2... but it really looks like its up to the people here to figure out how to dump the phone's current ROM. Given that it has a usb port (and people have gotten some access to the system), I believe its possible one way or another.
Seeing that our current attempts to do something good with the phone had no success yet, i must ask.
Are any news on this topic? I guess we can even just take the "tools" part or drivers, we can skip the rom things .
Maybe Conflipper can help us? It appears he was in the news digging through the original Kin, finding a possible foundation for an instant messenger.
www(dot)phonearena(dot)com/news/Instant-messaging-client-coming-to-the-Microsoft-KIN-handsets_id11919
(sorry add periods between - can't post outside links yet)
Maybe he knows something that might kick start the hacking process?
*** I'm not a regular - I'm sorry I missed Conflipper's retirement ... ***
johnkussack said:
Are any news on this topic? I guess we can even just take the "tools" part or drivers, we can skip the rom things .
Click to expand...
Click to collapse
Sorry, been busy and only news I have on this front is depressing, so I didn't get around to updating quickly.
Can't get anything out of anyone, basically. nvidia wasn't helpful, microsoft wasn't helpful, verizon wasn't helpful, sharp wasn't helpful.
With Verizon, Microsoft, Sharp, it was more like a giant circle... each company would tell me that they couldn't help me, but the next company could, etc.
Calling nvidia just told me to fill out the developer application, but that didn't go anywhere.
It makes me sad because these phones would be awesome if we could actually customize and update them... although I guess there will eventually be replacements running android or something.
HP Veer (webOs) is nice, but it looks like it will be an ATT device, so...

Bad updating experience with Samsung

Hello guys, how are you doing?
I just wanted to share with you my own opinion over how Samsung deals with updates to a Galaxy Note 10.1.
Actually, many users have reported software bugs in Galaxy Note 10.1 and Samsung confirmed many like the bug of clipboard. But the bad part is Samsung ignorance of bug fixing. It is good that we will receive 4.1.2 update with premium suite preinstalled, but it is bad that we did not receive a bug fixing package!
It has been several months since the launch of the Note 10.1 that many owners of the product started to get frustrated of the bugs. I cannot copy an article and save it as note in S Note app or share it in Facebook!
Besides, Samsung released JB 4.1.1 update to some regions, stopped then started releasing 4.1.2 in the time users still have the buggy 4.0.4 for many months in several countries, if not most! Even though 4.1.1 has stability issues, Samsung shall fix current bugs of 4.0.4 before caring to release a major 4.1.2, as this needs a quite long time by Samsung for a frustrating bug to remain!
Software is as important as hardware. I do not care for receiving a new major update with hundreds of new features, as we will receive it soon or later! But for me, a stable software with only two features is far far better than a buggy one with hundreds of cool features that I am unable to use!
Samsung used to release improvement packages and push them to their software update server for their products, but it is really strange why this is not the case for Note 10.1!
Sent from my GT-I9300 using xda app-developers app
You write that you are still on N8000XXLGA.
Sorry man, but it is your fault if you chose not to update by flashing the newest firmware.
Thanks to Samsung, Samfirmware and XDA, you have this option.
Other big companies, for example Acer, LG, will not even give you this.
So why do you not update?
tweetatoo said:
Hello guys, how are you doing?
I just wanted to share with you my own opinion over how Samsung deals with updates to a Galaxy Note 10.1.
Actually, many users have reported software bugs in Galaxy Note 10.1 and Samsung confirmed many like the bug of clipboard. But the bad part is Samsung ignorance of bug fixing. It is good that we will receive 4.1.2 update with premium suite preinstalled, but it is bad that we did not receive a bug fixing package!
It has been several months since the launch of the Note 10.1 that many owners of the product started to get frustrated of the bugs. I cannot copy an article and save it as note in S Note app or share it in Facebook!
Besides, Samsung released JB 4.1.1 update to some regions, stopped then started releasing 4.1.2 in the time users still have the buggy 4.0.4 for many months in several countries, if not most! Even though 4.1.1 has stability issues, Samsung shall fix current bugs of 4.0.4 before caring to release a major 4.1.2, as this needs a quite long time by Samsung for a frustrating bug to remain!
Software is as important as hardware. I do not care for receiving a new major update with hundreds of new features, as we will receive it soon or later! But for me, a stable software with only two features is far far better than a buggy one with hundreds of cool features that I am unable to use!
Samsung used to release improvement packages and push them to their software update server for their products, but it is really strange why this is not the case for Note 10.1!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Agreed, I had to resort to manually flashing the German JB update to "fix" the PDF import problem on my Canadian N8010. I feel sorry for the average customer that bought the Note but doesn't know how (or even think) to flash a firmware.
This is why Samsung will remain a second-rate manufacturer of mobile devices: ineffective software QA and silly update rollout schedules.
Samsung is known for slow firmware updates, mostly due to the most customization of android in the world. Second-rate manufacturer? Not sure about that my friend. You are smart enough to Google Samsung.
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Likewise i fail to see why XDA Developers has so many users wanting Samsung update path posting .
First job i do is remove Kies and OTA .
jje
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Haha... so true... hehe... I like your humor...
The note isn't my first Android tablet, but it is the best that I've owned to date. My first Android tablet was an Archos 101. In addition to poor quality control that led to dead USB ports and speakers on multiple units while under warranty, the company's constant push of half-backed updates drove me and others away from that brand. You need to test code changes to make sure one "fix" doesn't break something else. Archos engineers didn't test updates thoroughly and rushed out updates that created additional issues. I quit updating that tablet. Thank goodness Samsung is more diligent. No OS is perfect and some of the things we might be unhappy with really are deliberate design features that Google incorporated into JB (or, in your case ICS). I would also suggest that you update to JB, you'll gain valuable features with the s-pen. At this point in time, I am happy with stock JB. I will probably root it soon (I wanted to use it on stock JB for a while before rooting). Eventually, I may flash one of the custom ROMs developed by the talented developers on this forum. The great thing about the popularity of Samsung products is that the popularity generates more developer interest, a big win for adventurous owners willing to root and flash.
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Having to do all that is, to me, what is required from buying a second or third-rate product. I wouldn't buy a car, for example, and be happy to expect that I need to change the spark plugs or some nonsense when I bring it home.
I mess around with R/C cars and I have in the past bought crappy cars because I enjoy tinkering and making them better, but I don't want or expect to do that with a mass market product lol.
skadebo said:
Having to do all that is, to me, what is required from buying a second or third-rate product. I wouldn't buy a car, for example, and be happy to expect that I need to change the spark plugs or some nonsense when I bring it home.
I mess around with R/C cars and I have in the past bought crappy cars because I enjoy tinkering and making them better, but I don't want or expect to do that with a mass market product lol.
Click to expand...
Click to collapse
Nice analogy er, maybe not...... Thing is, no one is forcing you to update/upgrade/tinker. An update message pops up from time to time on the device and you click ok and it installs. That is as simple as it gets. That's NOT what we are talking about here though. We are talking about folks getting their flossy in a twizzie because a newer version of the OS is available and it hasn't been pushed to their device yet.
I have never seen anything written anywhere on the terms and conditions of any device I have bought that states I am entitled to get any upgrade to OR should expect to be updated to the latest software. In fact, iirc it says that on occasion an update may, yes MAY become available for the device and to either follow the onscreen instructions or visit (insert website here) for instructions on how to update.
Now to get back to the point, peeps EXPECT TO GET THE LATEST UPDATE, but they don't want to follow the instructions to do it. These instructions are usually made as simple as 1-2-3 so that even the technologically challenged can follow them. Turns out they ain't simple enough for some though and then the moaning and bleating begins, followed by the blaming. My device is stuffed, Samsung is rubbish, this cheese toastie is mouldy etc, but you never hear anyone saying, aargh fecked it up but it was my fault, I was born with two left brains or life is like a box of chocolates lieutenant Dan!
Sorry for such a long post. But I hope it helps clear things a tad
Riki1kenobi said:
Nice analogy er, maybe not...... Thing is, no one is forcing you to update/upgrade/tinker. An update message pops up from time to time on the device and you click ok and it installs. That is as simple as it gets. That's NOT what we are talking about here though. We are talking about folks getting their flossy in a twizzie because a newer version of the OS is available and it hasn't been pushed to their device yet.
I have never seen anything written anywhere on the terms and conditions of any device I have bought that states I am entitled to get any upgrade to OR should expect to be updated to the latest software. In fact, iirc it says that on occasion an update may, yes MAY become available for the device and to either follow the onscreen instructions or visit (insert website here) for instructions on how to update.
Now to get back to the point, peeps EXPECT TO GET THE LATEST UPDATE, but they don't want to follow the instructions to do it. These instructions are usually made as simple as 1-2-3 so that even the technologically challenged can follow them. Turns out they ain't simple enough for some though and then the moaning and bleating begins, followed by the blaming. My device is stuffed, Samsung is rubbish, this cheese toastie is mouldy etc, but you never hear anyone saying, aargh fecked it up but it was my fault, I was born with two left brains or life is like a box of chocolates lieutenant Dan!
Sorry for such a long post. But I hope it helps clear things a tad
Click to expand...
Click to collapse
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Your advices are sick my friend. For me, I did flash many firmwares of other regions onto my devices. But in the same time, good may be overwhelmed by bad things. These 1-2-3 steps were sometimes helpful and other times disasterous! For example, I have flashed many firmwares before on my Galaxy S i9003, Galaxy S II i9100, and my latest Galaxy S III.
For unknown reason, my Galaxy S III got bricked and went into a boot loop. It was not a noticed hardware failure neither it was a corrupt Odin package, but for some reason, a hidden hardware failure has become obvious following the flash. Samsung has reported that the motherboard was completely damaged and that unofficial firmware flashing of different CSCs was the cause. It could be also a manufacturing error. Whatever it is, I was lucky that Samsung did not void my warranty as it was rooted at that time with the flash counter > 0.
Besides, I have more than five Samsung Galaxy devices in the house, and they look to me as their software geek!! Whenever an update is released, I cannot say always to them yes, and let me flash things to you!!!!
Besides, why am I supposed to flash the German one? For the learning hub that does not work in my country? Or for Music and Video hubs that are also forbidden in my Country?! And why does Samsung have all these software variability? Why does not they make a united software with custom configurations based on country; like Apple?! Apple used to release the update worldwide with blocking un-allowed features based on country chosen!
I love to update using OTA; AS SIMPLE AS THAT, apart from all the BLA BLA BLA you have said!!!
no one is forcing you to upgrade, after all it's your tablet and you can do whatever you want, i am still on ICS and plan to stay that way for a while because i feel personally it's stable for me and works, i don't really care about new features i will hardly use, best thing is to root and then you can decide if you want to upgrade your tablet at a later date or not, the option is still there with odin.
i too also prefer uk firmware because some features that are on the uk firmware won't specifically be on the german firmware, different regions different features.
tweetatoo said:
Besides, why am I supposed to flash the German one? For the learning hub that does not work in my country? Or for Music and Video hubs that are also forbidden in my Country?! And why does Samsung have all these software variability? Why does not they make a united software with custom configurations based on country; like Apple?! Apple used to release the update worldwide with blocking un-allowed features based on country chosen!
Click to expand...
Click to collapse
HUYI said:
i too also prefer uk firmware because some features that are on the uk firmware won't specifically be on the german firmware, different regions different features.
Click to expand...
Click to collapse
Hehehe The biggest joke of all is that the UK version is INCLUDED into the German version. You just need to change csc and you have the UK firmware, not a firmware LIKE the uk firmware but THE UK firmware.
Some people just prefer to complain instead of moving a finger themselves.
Just flashed premium bugs 4.1.2... not bad so far! Well woth the upgrade from ics unless you use the gallery, as that isn't fixed!
tweetatoo said:
I love to update using OTA; AS SIMPLE AS THAT, apart from all the BLA BLA BLA you have said!!!
Click to expand...
Click to collapse
Then stop being a complainawhinger then and just wait for Samsung to deliver your update to you OTA. While you're waiting for it I'll continue to try and help people wanting to update to the latest version, with my sick, but helpful advice, :good:
Riki1kenobi said:
Then stop being a complainawhinger then and just wait for Samsung to deliver your update to you OTA. While you're waiting for it I'll continue to try and help people wanting to update to the latest version, with my sick, but helpful advice, :good:
Click to expand...
Click to collapse
haha we need more people like you Riki1kenobi... some fun but helpful post... :laugh:
people should not get easily offended over some jokes the man was just trying to help... and as JJEgan said i also can't understand why so many xda members here are waiting for ota updates... i understand that xda is the place to look for all things android but really the 1st step you should do is not rely on kies and learn some odin and flashing..
but hell we're all in one community... there are always some whiners and whatever kind of people and that just adds to the fun of being here on xda..
Riki1kenobi said:
Nice analogy er, maybe not...... Thing is, no one is forcing you to update/upgrade/tinker. An update message pops up from time to time on the device and you click ok and it installs. That is as simple as it gets. That's NOT what we are talking about here though. We are talking about folks getting their flossy in a twizzie because a newer version of the OS is available and it hasn't been pushed to their device yet.
I have never seen anything written anywhere on the terms and conditions of any device I have bought that states I am entitled to get any upgrade to OR should expect to be updated to the latest software. In fact, iirc it says that on occasion an update may, yes MAY become available for the device and to either follow the onscreen instructions or visit (insert website here) for instructions on how to update.
Now to get back to the point, peeps EXPECT TO GET THE LATEST UPDATE, but they don't want to follow the instructions to do it. These instructions are usually made as simple as 1-2-3 so that even the technologically challenged can follow them. Turns out they ain't simple enough for some though and then the moaning and bleating begins, followed by the blaming. My device is stuffed, Samsung is rubbish, this cheese toastie is mouldy etc, but you never hear anyone saying, aargh fecked it up but it was my fault, I was born with two left brains or life is like a box of chocolates lieutenant Dan!
Sorry for such a long post. But I hope it helps clear things a tad
Click to expand...
Click to collapse
I absolutely, totally agree with you. People see something new and they just WANT to update, because we are consumer whores.
However, I needed to update to fix the notorious PDF import problem in S-Note (as noted in first post in this thread). Basically, if I wanted to import PDFs from school into S-Note, S-Note would crash. This only happens to specific versions of the N8010 firmware (Canada being one of them).
I don't come looking for fights etc. as a lot of people do, I just speak (sometimes shout!) the truth.
Different regions /countries have different legal requirements which I suspect is one of the big delays for some regions. If you want everything done for you (OTA) , be patient and stup reading forums lokking for the latest updateor you will never be happy.
Of course you could also encourage your government to remove some of the restrictions, but for that I think you will be waiting much longer! I for one am amazed the updates get out as quickly as they do, re-evaluating every rom in every country for legal issues has to be a very expensive nightmare. Samsung is a big international company, ignoring regional laws is not really an option.
Sent from my GT-N8010 using xda premium
I have lost my hope that New Zealand will be able to get JB Update. So now after reading many threads for months I am plunging into this forum to know how I can update my machine.
My tablet
Model Number
GT-N8000
Baseband version
N8000XXALI3
Android version
4.0.4
1. Please suggest me which firmware is going to be suitable for my tablet
2. If tomorrow NZ firmware is released and I be able to flash it manually will it be back to normal for OTA upgrades ?
Thanks
l. Put German Jellybean
2. Yes
Sent from my GT-N8000 using XDA Premium HD app

Fx0/Madai Kernel: Version WTF?

The kernel source that LG posted on their opensource distribution site is not the code for the latest shipping version. Is that cool? Do they have any responsibility to provide the source for the newest version the shipped?
I wonder if the code they released matches earlier versions even. If only I could track down a rip of the system & boot images from the original version that shipped in Dec. 2014. Or even for the version after that. If anyone has one of those laying about, thanks, yo.
I have no idea, but that doesn't sound right.
Are you looking to unlock the bootloader so people can flash updated FFXOS ROMs to the device?
Saijin_Naib said:
I have no idea, but that doesn't sound right.
Are you looking to unlock the bootloader so people can flash updated FFXOS ROMs to the device?
Click to expand...
Click to collapse
Actually, I think I was wrong. Gah! I didn't realize that the prima_wlan stuff could be included included from outside the kernel tree. A qcom opensource repo is maybe where they built it from maybe?
> unlock the bootloader
No problems there, the Fx0 is wide-open. Like other LG devices, once you clear the CAF you gain Fastboot, and from there this device is splayed all day. You lose Download Mode, but since neither Mozilla or LG have seen fit to provide any of the usual KDZ images for that, I can't see any downsides. Maybe if they decide to update the Fx0 it would get used? I think it'd update in recovery instead though, yes?
Still want rips of Japanese system partition though. I wonder if the hiddenmenu is also stripped from those versions with v2.1 also? I want that hiddenmenu.
I have no idea. I'm not familiar at all with setting up a repo or anything. I've only ever build the ZTE Open repos provided by Mozilla, haha.
Oh, that is promising. What is the CAF?
Are you looking to get your Fx0 up and running with nightlies? If things actually work, I might grab one from eBay as a development/testing device as well.
Saijin_Naib said:
I have no idea. I'm not familiar at all with setting up a repo or anything. I've only ever build the ZTE Open repos provided by Mozilla, haha.
Oh, that is promising. What is the CAF?
Are you looking to get your Fx0 up and running with nightlies? If things actually work, I might grab one from eBay as a development/testing device as well.
Click to expand...
Click to collapse
Err, I meant LAF, its the partition on some LG devices where the Download Mode boot image lives. I've been spending a lot of time with my head buried in Codeaurora(CAF) repos, it's on the tip of my tongue.
Are you looking to get your Fx0 up and running with nightlies?
Click to expand...
Click to collapse
I already have to some extent. I should have a fully-functional test build any day now. Been codeblocked by some frustrating commits from Mozilla lately, broke my crap like 3 damn times in the last week. Refining the whole build setup now, trying to minimize reliance on prebuilt stuff, building as much as can, hence the interest in the pronto_wlan module, which I assumed was something that was exclusively build in the kernel tree (as seen on other LG devices), but apparently there's a CAF repo for that. Anyway, yeah.
culot said:
Err, I meant LAF, its the partition on some LG devices where the Download Mode boot image lives. I've been spending a lot of time with my head buried in Codeaurora(CAF) repos, it's on the tip of my tongue.
Click to expand...
Click to collapse
Ah, good to know. I'm a bit saddened to see that the prices on the Fx0 have gone up since just this past weekend. These must be getting more and more popular...
As an aside, you wouldn't happen to be knowledgeable about how to root the LGE LGL15G (LG Sunrise, 4.4.2, TracFone). I bought one as a beta testing device and as an Android Tablet/Wi-Fi toy, but there is no space on it due to the included bloatware O_O
culot said:
I already have to some extent. I should have a fully-functional test build any day now. Been codeblocked by some frustrating commits from Mozilla lately, broke my crap like 3 damn times in the last week. Refining the whole build setup now, trying to minimize reliance on prebuilt stuff, building as much as can, hence the interest in the pronto_wlan module, which I assumed was something that was exclusively build in the kernel tree (as seen on other LG devices), but apparently there's a CAF repo for that. Anyway, yeah.
Click to expand...
Click to collapse
I was reading on the Mozilla wiki that they've been doing some code cleanup to transition FFXOS to B2G, and to make it so the community can maintain it. Apparently, they've been a bunch of busy bees debranding everything and settling dependencies. Is this why your builds have been busted?
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
I'm torn between getting one for grabbing yet another ZTE Open and smashing my face against the wall trying to get it to fully work with nightly builds.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Saijin_Naib said:
Ah, good to know. I'm a bit saddened to see that the prices on the Fx0 have gone up since just this past weekend. These must be getting more and more popular...
As an aside, you wouldn't happen to be knowledgeable about how to root the LGE LGL15G (LG Sunrise, 4.4.2, TracFone). I bought one as a beta testing device and as an Android Tablet/Wi-Fi toy, but there is no space on it due to the included bloatware O_O
I was reading on the Mozilla wiki that they've been doing some code cleanup to transition FFXOS to B2G, and to make it so the community can maintain it. Apparently, they've been a bunch of busy bees debranding everything and settling dependencies. Is this why your builds have been busted?
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
I'm torn between getting one for grabbing yet another ZTE Open and smashing my face against the wall trying to get it to fully work with nightly builds.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Click to expand...
Click to collapse
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
Click to expand...
Click to collapse
Considering how much proprietary LG stuff is on the Fx0, I doubt it. Dunno. Since FxoS is transitioning to B2G is there even a need for a official dev device? I have no idea really.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Click to expand...
Click to collapse
Just the usual LG-specific hiddenmenu stuff. It seems like it was included in the initial release version for the Fx0... but from there, I don't know. Too bad I can't find any of the previous versions anywhere. Somebody must have them, somewhere.
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Click to expand...
Click to collapse
I have no idea what that is. Tell me more!
root the LGE LGL15G
Click to expand...
Click to collapse
No, I don't know anything about that. I did try one once, seemed like a decent value for the $15 or so it was selling for.
culot said:
Considering how much proprietary LG stuff is on the Fx0, I doubt it. Dunno. Since FxoS is transitioning to B2G is there even a need for a official dev device? I have no idea really.
Click to expand...
Click to collapse
Drat. I was hoping they (LG) had opened up some of the binary blobs in their source release. I guess you're right in that there is no need for an official dev device, but much like with LuneOS, I think there is a need for a "supported" target/reference device that sets the baseline for functionality. I was hoping the Fx0 could be this device, but with your evaluation of it being still a highly closed, it sounds like a poor choice.
culot said:
Just the usual LG-specific hiddenmenu stuff. It seems like it was included in the initial release version for the Fx0... but from there, I don't know. Too bad I can't find any of the previous versions anywhere. Somebody must have them, somewhere.
Click to expand...
Click to collapse
I've never seen this menu. Do the new Fx0 devices sold on eBay have this OS image installed, or is it something that was only shipped on the KDDI carrier sold devices?
culot said:
I have no idea what that is. Tell me more!
Click to expand...
Click to collapse
The Blaze initiative was a path Mozilla were looking to take FireFoxOS on by allowing the OS to be customized and tweaked much like the desktop browser. The device would have the ability to call up the DevTools to edit the code of any running webapp to modify the appearance and functionality of the program. From what I had read, this would extend to even privileged/system apps. In this manner, the user could add something to say the Messages app (like a timestamp for how late a message arrived), change the background color of the messages thread, etc. These add-ons could be submitted to the Marketplace for certification and download. Also, it was likely that users could directly share these modifications by Sharing activities including Email, SMS, etc.
There was also talk of migrating over various XUL add-ons from the desktop browser that would be compatible with FFXOS. That alone would have made the platform borderline unstoppable, as the possibilities for expansion of utility, safety, and aesthetics would be nearly endless.
All of this being said, I can't currently find the articles about this initiative anymore. I'll keep looking.
culot said:
No, I don't know anything about that. I did try one once, seemed like a decent value for the $15 or so it was selling for.
Click to expand...
Click to collapse
I got mine for $9.99, and it benches out to being fairly comparable to the Moto E, which is not a bad performance point to be at for around $10. Shame it is SIM-locked and very difficult to root and take the garbageware out of.
Saijin_Naib said:
I've never seen this menu. Do the new Fx0 devices sold on eBay have this OS image installed, or is it something that was only shipped on the KDDI carrier sold devices?.
Click to expand...
Click to collapse
It looks like maybe the hiddenmenu was removed with a FxOS v2 update that added the ability to edit APNs, something that had to be done in the hiddenmenu previsouly. Maybe...
Ah, crap, I was wrong: the hiddenmenu, along with a ton of other LG & KDDI stuff, was stripped out of the international/unlocked version, leaving it a slow, featureless shell. It's disgusting actually. I feel acutely slighted. It's amazing the difference between both the speed and the features of the Japanese and unlocked versions. Apparently in Japan this is actually a decent phone. Too bad the international/unlocked peeps got the shaft.
And here I thought FxOS in general was just slow and terrible: turns out that was just result of the hatchet job pulled on the unlocked variants of the Fx0.
I wonder if it would be possible to overcome the mozfree issue that prevents the old libs from working on newer B2G?
Gah! I feel angry.
Hey. Do you still want the original jap 2.0 images?
aflaton said:
Hey. Do you still want the original jap 2.0 images?
Click to expand...
Click to collapse
If you have a retail firmware, it would be much appreciated.

Custom ROMs?

I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
tele_jas said:
They're waiting on a full image of the ROM to be released, with all the img, radio, ect.. and other files needed to make it work. Once that drops form ZTE, it's on like some 80s video game reference.
Click to expand...
Click to collapse
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
mhodak said:
Noob question: Cannot these be taken from images that were extracted from the phone already? Does rom provide that much more?
This is a genuine question, isn't rom just a packed and zipped version of what is on the phone?
Click to expand...
Click to collapse
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
xgerryx said:
I was pretty sure that once we got root and bootloader access that this could be done just as you said here. No need for drivers or proprietary anything...although the camera API will be a problem, but I think it's possible right now. I was just wondering why no one has the desire to attempt it. Did the weird release and shipping debacle for the grey phones really make everyone avoid the phone and hamper dev this much? Sort of disappointing if that is the case.
Click to expand...
Click to collapse
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
mhodak said:
This worries me as well. It appears that there is only one person actively working on a custom ROM. Although things can pick up later, this does not bode well for the future.
Click to expand...
Click to collapse
My thoughts are differently, base on the many issues people are running when trying to get back to stock and the fact they there's 2 B20 versions around (B20 Stock & B20_boot) make things a Little harder to do, like for sample,
I have the B20_boot version and as you can see I uploaded a backup with Xposed debloated and Rooted (I can consider that backup/ Custom ROM) but stock B20 can't use that backup as far as I know... I can easily release a flash able zip base on my backup but (Xposed,Debloated,rooted) but I bet only 5% of the user are using b20_boot.
So till find a way or just way till ZTE release a firmware image we are going to be little stuck with just CM which is getting more stable every day/week
xgerryx said:
I have been waiting a while to post this because posts like this always get killed, but for a phone with a factory-available bootloader unlock, I am surprised we don't have a modded stock ROM to try out yet. TruPure on the Moto x Pure was awesome, although it altered very little. I know CM is being worked on but given some of the responses in that thread, it could be quite a while.
So aside from that observation, is anyone actively working on something like that and if so, can you post here and let us know how things are coming along? I know we all would be appreciative of the effort.
Click to expand...
Click to collapse
First, the Moto X Pure was widely available. It was not shipped out in smaller batches once a month. When it was released, it was available for everyone to purchase. For the Axon 7, the first batch and second small batches of phones sold out during pre-order, and the third batch hasn't even shipped yet. (and it hasn't received a wide release in Europe yet either, think they just had one small batch)
Also, the Moto X Pure had bootloader unlock available at launch. The Axon 7 did not get a bootloader unlock method until August 11th, less than a month ago. (and at this time, there is no bootloader unlock for the European or Chinese models, just the North American model)
And just as a reminder, the Moto X Pure launched in early September. Dev for CM12.1 started in late September. The first custom ROM, an alpha of CM12.1, was released a month later, in the beginning of October.

Categories

Resources