Related
So, now that the 2.2 update has been announced by B&N for the middle of the month I am trying to figure out what to do. Should I block the update and wait to see how 'open' it is? I'm sure that the development community will be able to root it if it is locked down but I just wonder how long that will take. What are most people doing? I am leaning towards letting it update automatically.
Me personally...gonna give the new update a try. If it isn't up to snuff...back to CM7. Since the nook is hardwired to boot from uSD no worries about if B&N try to lock the OS down. I highly doubt they will make it to hard anyhow. They know they have a large section of users who want root access...
Sent from my NookColor using Tapatalk
Since I could not be more pleased with rooted nc I have blocked the OTA and I will wait to see how the push is evaluated by others. To my way of thinking that will also allow time for the development of new rooting processes. what is missing.... a microphone, decent speaker output and a camera, with the possible exception of increasing usable volume, no push is going to fix anyway.
Sent from my LogicPD Zoom2 using XDA App
Just my personal opinion, but I really hate push OS updates for android devices. I'd rather apply an update myself. Even though I doubt that B&N will block our rooting, there is that small chance of rooted 2.1 not being compatable with the update itself, for whatever reason. You also have to remember that the B&N 2.2 update will not be true 2.2. You will only have access to their own market, so very limited apps. The ultimate upside to this update will be the new kernel for the devs. Hopefuly it will solve some of the problems that continue to keep Nookie Froyo and CM7 80% complete. ie. sleep death, wifi and bluetooth stability, USB host.
The choice is yours to make, but I would block OTA updates. You can always sideload the official update anyway.
That begs the question: how do you block OTA updates? I couldn't figure it out on my auto-nootered stock NC.
Sent from my LogicPD Zoom2 using XDA Premium App
marcusau2 said:
So, now that the 2.2 update has been announced by B&N for the middle of the month I am trying to figure out what to do.
Click to expand...
Click to collapse
Just a clarification. This is what has been announced in a formal press release:
"NOOK Color will get even better this Spring when a major update to the device’s firmware will offer customers access to explore exciting new applications, e-mail and many other requested features."
http://www.barnesandnobleinc.com/press_releases/2011_march_25_nook_color_better.html
Froyo was not mentioned - so the update may or may not include froyo. "Spring" is anytime between 3/21 and 6/21. I discount anything from HSN.
Be interested if there is another reference to the update from BN.
if you have CWM insstalled, then from what i hear, updates get blocked.
bluewhite79 said:
if you have CWM insstalled, then from what i hear, updates get blocked.
Click to expand...
Click to collapse
CWM is Clock Work Manager? Could you please explain what it is and what it does to block updates? I have read what I can about it but have not found an explanation that I can understand.
All CWM does is allow u to install/update clockwork recovery without the need for a cpu....cwm blocks ota(s) only if a non stock recovery is on ur phone
Sent from my T-Mobile G2 using XDA App
in my case i will stick with cm7. i do not believe stock will get any better, however i do not use bn software at all
fpga_guy said:
Just a clarification. This is what has been announced in a formal press release:
"NOOK Color will get even better this Spring when a major update to the device’s firmware will offer customers access to explore exciting new applications, e-mail and many other requested features."
http://www.barnesandnobleinc.com/press_releases/2011_march_25_nook_color_better.html
Froyo was not mentioned - so the update may or may not include froyo. "Spring" is anytime between 3/21 and 6/21. I discount anything from HSN.
Be interested if there is another reference to the update from BN.
Click to expand...
Click to collapse
It was published back in December that it is Froyo based by Ars Technia. Why would they say it is Froyo when it is not, it is Froyo based Nook ROM. Most Nook owners (besides the ones on xda) have no idea what Froyo is anyway.
Sent from my SGH-i917 using XDA Windows Phone 7 App
If I've flashed new roms to the emmc will the update happen or is this only for rooted stock Rom users?
Sent from my Inspire 4G using Tapatalk
Anything other than stock or rooted stock that isn't set to block updates will be the only ones to do an automatic update. If you're on the modded Roms: nookie froyo, cm7, hc, etc you would have to download and flash it manually. Or alternatively restore to stock and let it update.
chrzanek_ said:
in my case i will stick with cm7. i do not believe stock will get any better, however i do not use bn software at all
Click to expand...
Click to collapse
Couldnt have said it better my self.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
Disregard B&N.
Install CM7. It's actually really good now. It's even got bluetooth.
I'd love to use something other than rooted stock, but I enjoy the Nook magazines, so I'm eager to see what the update brings.
Sent from my LogicPD Zoom2 using XDA Premium App
cshehan said:
Anything other than stock or rooted stock that isn't set to block updates will be the only ones to do an automatic update. If you're on the modded Roms: nookie froyo, cm7, hc, etc you would have to download and flash it manually. Or alternatively restore to stock and let it update.
Click to expand...
Click to collapse
I am autonootered 3.0 mostly because I enjoy the stock ereader functionality. I have also installed quite a few apps and launcher pro. Will an automatic OTA update affect my apps or launcher functionality? If so, his can I easily block it?
Sent from my Nook Color using XDA premium
Hi All,
My Moto X (1st Gen) is about 4 months old. I'm contemplating on rooting the phone. Is it worth the effort or should I patiently wait for the Lollipop update to come in (whenever that is!). I used a lot of custom roms in my old Nexus 4, so missing the excitement of a new rom. just a bit indecisive at the moment. Would love your opinions on this.
arjun2058 said:
Hi All,
My Moto X (1st Gen) is about 4 months old. I'm contemplating on rooting the phone. Is it worth the effort or should I patiently wait for the Lollipop update to come in (whenever that is!). I used a lot of custom roms in my old Nexus 4, so missing the excitement of a new rom. just a bit indecisive at the moment. Would love your opinions on this.
Click to expand...
Click to collapse
I am using the Moto X for nealry 9 months now. Never thought of rooting it as I didnt find any bloat here like the Touchwiz
I am honestly very tempted by the ROMs out there. And I don't know why but I'm definitely noticing some performance lag. Tried everything but not seeing a lot of improvement.
Sent from my Moto X using XDA Free mobile app
Before you go contemplating this question, figure out if you'll be able to root your phone in the first place.
Then instead of asking this question, ask whether or not you should unlock the bootloader. It's the only way to maintain root since 4.4.4 patched the vulnerabilities used to attain root.
There are reasons why I would root like Tasker(full functionality),a custom kernel or UI changes
I rooted my X so I can play with gravity box and other stuff. Unrooting and relocking the bootloader isn't hard to do and that's what I'll do once Lollipop comes out for my phone. (Already factory reset my phone once from custom Rom).
TheBoiledDogs said:
I rooted my X so I can play with gravity box and other stuff. Unrooting and relocking the bootloader isn't hard to do and that's what I'll do once Lollipop comes out for my phone. (Already factory reset my phone once from custom Rom).
Click to expand...
Click to collapse
You are going to re lock your bootloader to take Lollipop?
Travisdroidx2 said:
You are going to re lock your bootloader to take Lollipop?
Click to expand...
Click to collapse
I meant to say return to stock recovery. I read somewhere that you can't get OTA with a custom recovery, Rom and rooted.
TheBoiledDogs said:
I meant to say return to stock recovery. I read somewhere that you can't get OTA with a custom recovery, Rom and rooted.
Click to expand...
Click to collapse
Gotcha, that is true. Stock recovery and stock system and you are good to go.
I personally root all my devices for better control. However, I personally don't use Roms because I want a stock experience and that includes boot animation and themes. The only Roms I have ever kept on my phones were ARHD and Paranoid Android. If neither are available, I go with Xposed.
I am still running OE2 rooted on my device, and I was wondering with all the new versions up to 6.0.1 thats hit these phones, Have the ability to be rooted?
I still sense "no" from other threads. If thats the case, I think ill stay on the year+ old OE2.
Was just wondering. thanks.
No root yet to SM-G925a on 6.0.1
if you absolutely need root then stay on oe2, but marshmallow is faster and battery saver compared to that. much difference. plus the new security updates keeps the phone more secure.
Sent from my SAMSUNG-SM-G925A using Tapatalk
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Q9Nap said:
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Click to expand...
Click to collapse
Factory firmware for Shamu was 5.0. Thats what it shipped with. Their was never a 4.X for Shamu.
As for 4.4.4, anything is possible. Will you be able to find a dev willing to work on it? Most likely not. Makes no sense other than the challenge of it. Might be a project you can take up yourself if you like. There are tons of tutorials, information, and devs around to give advice.
Q9Nap said:
This probably sounds like a crazy question, but wondering whether it would be possible to build/run AOSP 4.4.4 on Shamu?
The factory firmware for Shamu is 4.4.4, so it should be possible afaik.
The only reason I can think of for why it wouldn't work is proprietary binaries, as 5.0 are the earliest available.
Click to expand...
Click to collapse
sure, its possible.. do you havd a kitkat driver for the n6 to make it work? if not, then itll never work. btw, google never released the drivers.
christianpeso said:
Factory firmware for Shamu was 5.0. Thats what it shipped with. Their was never a 4.X for Shamu.
As for 4.4.4, anything is possible. Will you be able to find a dev willing to work on it? Most likely not. Makes no sense other than the challenge of it. Might be a project you can take up yourself if you like. There are tons of tutorials, information, and devs around to give advice.
Click to expand...
Click to collapse
Yes, Shamu shipped with 5.0, but there is a 4.4.4 factory firmware file that is available for use by repair centers.
I've tried it, and it is a very minimal build. It isn't worth using as a daily driver at all.
I'm sure I could repo sync and compile aosp 4.4.4, but I don't want to take the time and effort if it won't work lol.
Besides the lack of 4.4.4 proprietary binaries, there is also no official 4.4.4 kernel source, so I'm basically wondering if it could work with 5.0 proprietary binaries and kernel source?
simms22 said:
sure, its possible.. do you havd a kitkat driver for the n6 to make it work? if not, then itll never work. btw, google never released the drivers.
Click to expand...
Click to collapse
Right, the lack of 4.4.4 drivers and kernel source are my main concern as far as whether it would work.
I'm wondering whether it would be possible to extract the necessary driver files and kernel from the factory buid?
Q9Nap said:
Right, the lack of 4.4.4 drivers and kernel source are my main concern as far as whether it would work.
I'm wondering whether it would be possible to extract the necessary driver files and kernel from the factory buid?
Click to expand...
Click to collapse
theres no kitkat driver, period. if there is, google has it. no, you cant extract a past driver from a newer os.
simms22 said:
theres no kitkat driver, period. if there is, google has it. no, you cant extract a past driver from a newer os.
Click to expand...
Click to collapse
I have a 4.4.4 pre-release build from Motorola; would it be possible to extract the drivers and use its kernel/boot image?
Pre-release build of what from Motorola? Unless that pre-release build is specifically for the Nexus 6, you won't be able to use its kernel with the device.
*removed*
Q9Nap said:
I have a 4.4.4 pre-release build from Motorola; would it be possible to extract the drivers and use its kernel/boot image?
Click to expand...
Click to collapse
nope. drivers are very device specific. it has to be a nexus 6 driver, or you will not get any of the software to work with the hardware and with the physical device.
simms22 said:
nope. drivers are very device specific. it has to be a nexus 6 driver, or you will not get any of the software to work with the hardware and with the physical device.
Click to expand...
Click to collapse
Ok, I'll say it again; I have official 4.4.4 Motorola firmware for the Nexus 6. See the build.prop in the previous post.
Is it possible to extract the drivers and kernel from this and include in AOSP 4.4.4?
It is factory test firmware and isn't really viable to use as a daily driver, which is why I want to use parts from it to build AOSP.
Q9Nap said:
Ok, I'll say it again; I have official 4.4.4 Motorola firmware for the Nexus 6. See the build.prop in the previous post.
Is it possible to extract the drivers and kernel from this and include in AOSP 4.4.4?
It is factory test firmware and isn't really viable to use as a daily driver, which is why I want to use parts from it to build AOSP.
Click to expand...
Click to collapse
you can try, thats the best that i can say..
As @simms22 already said, you can try it. However, according to the build.prop, ro.product.model is an XT-1080,which is a Droid Ultra. The hardware for the Droid Ultra is completely different from the N6, with specs more applicable to a Samsung Galaxy S3, and thus its drivers and kernel will both be different. Neither will work on the Nexus 6.
I'm sorry, but I highly doubt this is a genuine Nexus 6 pre-release ROM. Posting the build.prop is insufficient proof, as the build.prop can be easily edited to have it say whatever you choose. You'll have to find another way to persuade the audience.
I'm not trying to persuade anyone, lol. I'm just asking whether it's theoretically possible or not.
You are welcome to have access to the full firmware if you like, sheesh.
Why would I bother faking a build.prop?
It's not, as the Droid Ultra hardware is totally different. As to why anyone would want to fake a pre-release ROM, your guess is as good as mine. But at least you provided something when asked, unlike one guy in the S4 forums who claimed he could reset the Knox efuse after it was tripped, something not even Samsung can do.
Strephon Alkhalikoi said:
It's not, as the Droid Ultra hardware is totally different. As to why anyone would want to fake a pre-release ROM, your guess is as good as mine. But at least you provided something when asked, unlike one guy in the S4 forums who claimed he could reset the Knox efuse after it was tripped, something not even Samsung can do.
Click to expand...
Click to collapse
This is not for droid ultra. Yes, one line in the build.prop says xt1080, but everything else says shamu. Apparently, xt1080 was the working model number during testing.
For you and any other doubters, here ya go:
https://drive.google.com/file/d/0B-53iD-71B3iMElKNWdybC1aanc/view?usp=sharing
Wow, this thread is hilarious.
First off, there is no such thing as a driver that is linked specifically to a version of Android. The driver is between LINUX and HARDWARE.
While newer versions of Android may be more demanding of the kernel, they are not intrinsically tied together. You can run Android 2.0 on Kernel 4.6 if you want. Nothing is going to stop you from doing that.
Now the place where you could run into some stickyness, is in the **hardware abstraction layers**. These are not the drivers. These are the bits of code that talk Android API on one side, and Linux on the other side. Most of the HALs are open source, so could be converted if need be.
Most of the HAL changes are things being added into the new versions that didn't exist in the old. As a result, in most cases, you could take a 5.0 HAL and stuff it into a 4.4 system image -- and it should work.
But the big question is.... why would you ever want to do that? 4.4 is obsolete and dead. LEAVE IT BE!
doitright said:
Wow, this thread is hilarious.
First off, there is no such thing as a driver that is linked specifically to a version of Android. The driver is between LINUX and HARDWARE.
While newer versions of Android may be more demanding of the kernel, they are not intrinsically tied together. You can run Android 2.0 on Kernel 4.6 if you want. Nothing is going to stop you from doing that.
Now the place where you could run into some stickyness, is in the **hardware abstraction layers**. These are not the drivers. These are the bits of code that talk Android API on one side, and Linux on the other side. Most of the HALs are open source, so could be converted if need be.
Most of the HAL changes are things being added into the new versions that didn't exist in the old. As a result, in most cases, you could take a 5.0 HAL and stuff it into a 4.4 system image -- and it should work.
But the big question is.... why would you ever want to do that? 4.4 is obsolete and dead. LEAVE IT BE!
Click to expand...
Click to collapse
This is the kind of response I was looking for, thank you!
Yeah I know KK is obsolete; the main reason I am interested, besides theoretical curiosity, is the holo dark ui; really don't like the bright material white ui, and the material dark ui doesn't look that great either.
I know I can use cmte, layers, or substratum to install a dark ui theme, but I haven't found a theme yet that doesn't have issues and/or inconsistencies, and they don't look as good as og holo dark imo.
Anyway, it definitely sounds like more trouble than it's worth, lol.
Soo....3 weeks ago i was searching for a phone to replace my aging Kirin 650-powered Honor 5C and i was going to buy another Huawei (and also getting ready to be disappointed again by their half-assed software support for mid-tier devices and a GPU processing power equivalent to my Casio Scientific Calculator) until my eyes were locked on a super great deal. A 190-ish USD for a 128 GB Mi A2.
I was so excited back then but after a while i just realized a few things with the latest update (first pie update, im kinda scared installing the second pie after claims of bricking devices lol) which are
1. The camera app is meh
2. It doesnt shoot in RAW (My rooted 5C got it, thanks HassanMirza and other peeps on developing the superb Elite ROM on this device)
3. The portrait mode sucks major ass like it only detects objects thats at the center of the frame (sucks when youre using the rule of thirds)
4. And gosh whats with these white dots when im using manual mode with long shutter speed
I just felt like this superb hardware (this phone snaps superb pics btw) is being bogged down with a meh-than average software. Its not bad but when you found settings like "Picture Quality" and "low, med, high" you'd be thinking like, am i a joke to you xiaomi? Also I like how Huawei's camera app are more technical and in-depth, but i wanted some more "meat" on the processing power (i prefer sd 660 than the kirin 710)
So i was so tempted to install Gcam
In which we will end this rant (sorry) and get back to my topic which is; Should i lose OTA and root this phone? Because idk why i would like to have my warranty (i only do this to out-of-warranty devices only) and this pure android is as good as pure water, or pure whatever that you like, its so good fast and 90 percent bug free. But i also want the features that those custom rom (especially pixel experience UwU) so should I wait for future updates where hopefully Xiaomi will enable Camera2API by default? Or should I succumb on my own impatience-ness and root/unlock/flash my 3 week old Mi A2? What will i gain if i unlock? and what will i lose?
oh also i broke the screen on this baby yesterday, came of from my t-shirt pocket when i was trying to tie my shoes. So um wear cases/Screen protectors guys, gorilla glass 5 is just a marketing gimmick smh
BeWaryBeCautious said:
In which we will end this rant (sorry) and get back to my topic which is; Should i lose OTA and root this phone? Because idk why i would like to have my warranty (i only do this to out-of-warranty devices only) and this pure android is as good as pure water, or pure whatever that you like, its so good fast and 90 percent bug free. But i also want the features that those custom rom (especially pixel experience UwU) so should I wait for future updates where hopefully Xiaomi will enable Camera2API by default? Or should I succumb on my own impatience-ness and root/unlock/flash my 3 week old Mi A2? What will i gain if i unlock? and what will i lose?
Click to expand...
Click to collapse
You can Root your phone and have OTA at the same time. As long as you stick to the stock rom and don't make changes to the system partition, OTA will be intact.
The only caveat is, you have to take some extra steps before updating your phone. There is a great guide on Mi A2 Lite's forum for proper Magisk installation with OTA intact.
I have not flashed a ROM on this one so I don't know how is the experience there. I have been running custom ROMs on every device I have owned but the A/B partition and temporary TWRP and all the extra steps are a lot for me. I would rather use Magisk modules to replicate the features I want on the stock ROM itself.
I bought this phone to stick with stock plus all mods I usually do. I was always with custom roms, I thought why not a phone with good specs great camera and regular stock updates. When I bought it pie had just arrived. It lasted 3 4 weeks then back to my beloved pixel experience. The difference was big. PE is way ahead of buggy stock. Ok not the easiest phone right now for twrp and flashing roms with a b slots but with a little reading you can do it... Gcam was huge difference as well both in stock and in PE. So my suggestion is yeah totally you have to go for custom rom. Only to get rid of the dull color of the lcd on stock is enough
Sent from my Mi A2 using Tapatalk
Sp_Ark said:
I bought this phone to stick with stock plus all mods I usually do. I was always with custom roms, I thought why not a phone with good specs great camera and regular stock updates. When I bought it pie had just arrived. It lasted 3 4 weeks then back to my beloved pixel experience. The difference was big. PE is way ahead of buggy stock. Ok not the easiest phone right now for twrp and flashing roms with a b slots but with a little reading you can do it... Gcam was huge difference as well both in stock and in PE. So my suggestion is yeah totally you have to go for custom rom. Only to get rid of the dull color of the lcd on stock is enough
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Partitions? Umm care to explain what exactly it is? Like I did heard A/B partitions but I never got a hang of it. Before this I've only dealt with phones that has microsd expansions so I never heard of A/B partitions.
Yeah I'm diving deep into the PE forum right now Hahahah. But when you said it's not the easiest to twrp, what do you mean? I mean what should I expect when I'm going to flash a custom recovery on this phone? (apart from not bricking etc2 usual stuff)
Thanks for your response btw
BeWaryBeCautious said:
Partitions? Umm care to explain what exactly it is? Like I did heard A/B partitions but I never got a hang of it. Before this I've only dealt with phones that has microsd expansions so I never heard of A/B partitions.
Yeah I'm diving deep into the PE forum right now Hahahah. But when you said it's not the easiest to twrp, what do you mean? I mean what should I expect when I'm going to flash a custom recovery on this phone? (apart from not bricking etc2 usual stuff)
Thanks for your response btw
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=78890796
Sent from my Mi A2 using Tapatalk
Sp_Ark said:
https://forum.xda-developers.com/showthread.php?p=78890796
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Gee
Oh and also I've read about custom recovery not working properly after the Pie update *sigh* idk if it's true.
And it seems that it's easier to mod after switch to 6X rather than in A2.
Well idk I still have warranty on this phone, I think I'll just wait until everything just matures out. Thanks for the info by the wayy
Sent from my Mi A2 using Tapatalk
You dont need to root, you can just boot with a patched boot.img, run the appropriate commands to enable camapi via adb and reboot without tampering with ota relevant partitions
is it better to unlocked bootloader in mi a2 or just keep it locked?
I'm just concerned if phone got bootloop after update and phone's bootloader is not unlocked.
btw if bootloader's unlocked, can we receive ota and install it?
thanks!
dyobetem said:
is it better to unlocked bootloader in mi a2 or just keep it locked?
Click to expand...
Click to collapse
IMHO there occurred valuable reason to have "jasmine" with unclocked bootloader: many "loyal" users of "jasmine" got their phones bricked with infamous January patch (10.0.3.0), while those who had unclocked bootloader could easily flash back more-or-less stable 10.0.2.0.
For those that have unlocked bootloader and critical and remain on the stock ROM is your Playstore Play Protect Certification Device is Certified or Uncertified?
IjazCI said:
Uncertified
Click to expand...
Click to collapse
Thanks. Do you find any restrictions in downloading any sort of apps from playstore?