Rom Update Guidance - Fire TV Q&A, Help & Troubleshooting

I've gotten hold of an Amazon Fire TV that was already rooted, but has a very old Stock Rom on it.
It currently has software version: 51.1.0.1_
The newer versions of the the custom ROMS state don't install unless you have had version 51.1.4.0 and you just can't skip to it.
Can I install version 51.1.4.0_514006420? without any issues since my stock FW appears to be old. It doesn't list any pre-requisites on the page so I assume that it safe, but just want to make sure. Then after I install that firmware I should be able to load the latest, correct?
Does anyone have a link to a tutorial to updating the rooted firmware before the BOOT Menu requirement, or is the procedure essentially still the same?
Thanks for the advice!

Alvisaar said:
I've gotten hold of an Amazon Fire TV that was already rooted, but has a very old Stock Rom on it.
It currently has software version: 51.1.0.1_
The newer versions of the the custom ROMS state don't install unless you have had version 51.1.4.0 and you just can't skip to it.
Can I install version 51.1.4.0_514006420? without any issues since my stock FW appears to be old. It doesn't list any pre-requisites on the page so I assume that it safe, but just want to make sure. Then after I install that firmware I should be able to load the latest, correct?
Does anyone have a link to a tutorial to updating the rooted firmware before the BOOT Menu requirement, or is the procedure essentially still the same?
Thanks for the advice!
Click to expand...
Click to collapse
Read, read and re-read before you start installing anything or you will be regretting it .
start here:
http://www.aftvnews.com/start/

Alvisaar said:
I've gotten hold of an Amazon Fire TV that was already rooted, but has a very old Stock Rom on it.
It currently has software version: 51.1.0.1_
The newer versions of the the custom ROMS state don't install unless you have had version 51.1.4.0 and you just can't skip to it.
Can I install version 51.1.4.0_514006420? without any issues since my stock FW appears to be old. It doesn't list any pre-requisites on the page so I assume that it safe, but just want to make sure. Then after I install that firmware I should be able to load the latest, correct?
Does anyone have a link to a tutorial to updating the rooted firmware before the BOOT Menu requirement, or is the procedure essentially still the same?
Thanks for the advice!
Click to expand...
Click to collapse
Honestly as nice and sweet as the amazon fire is.. I don't think it is a "long term" solution for cheap android to home setups.. because as long as it remained locked like that (and we can't work around it) it's not a long-term solution.. (just cause you could root your device doesn't mean that it won't break.. and your root is gone )I've been following the development of phone hardware for hdtv's for a long time.. (stupid SMARTtv's suck what a waste of hardware!) the reason why I bought amazon fire is because all the other products out there.. (and there's plenty!)
Many have had over-heating issues.. and that's one thing that makes amazon's nice.. nice remote, no over-heating! (low price) So I wouldn't bank on it being around.. if people want stock android.. and I would have preferred that as well..
And now intel is selling a windows 8.1 stick with a additional usb port for storage.. hdmi version.. it's pricey at $150.. but maybe when it's $50.. it'll be worth it?
So I do think we should see lots more refinements on this technology.. and amazon's the only one who delivered a full usable product with decent spec's.. though I hear roku is much more "stable" in the apps department.. and now finally making one that has more then 512 mb ram..

Related

[Q] Updating beyond Android v 4.0.4 won't block ROOT, right?

Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
EDIT: Phones are brand new- they are STOCK. (Not rooted)
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well liked rom image for the S3 currently? (Stable)
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of what needs to be done, but rusty on the "particulars".
.
WeAreNotAlone said:
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well likely rom image for the S3 currently?
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of want needs to be done, but rusty on the "particulars".
.
Click to expand...
Click to collapse
Are you already rooted? If you update you could lose root I'm not really sure since I'm not on stock but it is easy to re-root it if you have too. And no updating wont permanently block your device from being rooted.
check out this thread: http://forum.xda-developers.com/showthread.php?t=1949687
it has all the official firmwares & pre-rooted official firmwares that are odin flashable
WeAreNotAlone said:
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well likely rom image for the S3 currently?
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of want needs to be done, but rusty on the "particulars".
.
Click to expand...
Click to collapse
These aren't like playbooks or ONE X's. We can flash firmwares and updates through Odin. You are safe bro
j_smith305 said:
Are you already rooted? If you update you could lose root I'm not really sure since I'm not on stock but it is easy to re-root it if you have too. And no updating wont permanently block your device from being rooted.
check out this thread: http://forum.xda-developers.com/showthread.php?t=1949687
it has all the official firmwares & pre-rooted official firmwares that are odin flashable
Click to expand...
Click to collapse
RE: Are you already rooted?
Nope, bone stock. Would like to run the units for about 30-days (Of course that may change, EG Sooner)
Appreciate the links, will check it out.
On a recommendation on a rom, Looking for rom with a high WAF. (Wife Approval Factor)
Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
Lakeshow423 said:
These aren't like playbooks or ONE X's. We can flash firmwares and updates through Odin. You are safe bro
Click to expand...
Click to collapse
Thank you,
After experiencing the "joy" of PlayBook #1 of #4 doing a forced update to a OS version which was not rootable, plus was non reversible wanted to get a feel on what was going on. In the end with the PlayBooks I have (1) unit left that I'm debating to root or not... REASON? There's like (1) person on the CrackBerry forums that has a in-depth knowledge of the QNX OS.... and the info on flashing a "rootable" version of the OS is not well documented. (Info is scattered amongst multiple threads- the (1) poster with a in-depth knowledge posts in a cryptic fashion.
Process seems pretty simple, but there is little "traffic" in the rooting section so that does not inspire confidence in getting answers to problems that may pop up after the "root".
From what I read BlackBerry /RIM closed the loophole that allowed the PB's to be rooted fairly quickly and numerically the numbers of persons who even have a "rooted" PlayBook is few and far between, VS those with Android powered devices. )
Getting back to the Samsung,
As noted above: Looking for rom with a high WAF. (Wife Approval Factor)
Stability is a factor, and "time" tweaking is at a premium.
What rom would you recommend?
PS: Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
(If tethering can be done without rooting, may leave the units stock for about 30-days or so until hardware is proven to be defect free. If you have any info on that, I'd be all ears.)
.
WeAreNotAlone said:
Thank you,
After experiencing the "joy" of PlayBook #1 of #4 doing a forced update to a OS version which was not rootable, plus was non reversible wanted to get a feel on what was going on. In the end with the PlayBooks I have (1) unit left that I'm debating to root or not... REASON? There's like (1) person on the CrackBerry forums that has a in-depth knowledge of the QNX OS.... and the info on flashing a "rootable" version of the OS is not well documented. (Info is scattered amongst multiple threads- the (1) poster with a in-depth knowledge posts in a cryptic fashion.
Process seems pretty simple, but there is little "traffic" in the rooting section so that does not inspire confidence in getting answers to problems that may pop up after the "root".
From what I read BlackBerry /RIM closed the loophole that allowed the PB's to be rooted fairly quickly and numerically the numbers of persons who even have a "rooted" PlayBook is few and far between, VS those with Android powered devices. )
Getting back to the Samsung,
As noted above: Looking for rom with a high WAF. (Wife Approval Factor)
Stability is a factor, and "time" tweaking is at a premium.
What rom would you recommend?
PS: Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
(If tethering can be done without rooting, may leave the units stock for about 30-days or so until hardware is proven to be defect free. If you have any info on that, I'd be all ears.)
.
Click to expand...
Click to collapse
If it's for your wife then I would probably stick with stock so she doesn't complain about minor bugs lol or you could try a touchwiz based rom. Just check out the different roms in the android development & original android development thread and see if you find any that you like
As for tethering I can't help you much since I don't really use it. I did a quick search and found this thread that might be able to help: http://forum.xda-developers.com/showthread.php?t=1988735
If you are wanting to root I would use the root injected rom. The instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1771687
This gives root but fully stock otherwise. It is probably one of the safest ways to root.
Sent from my SGH-T999 using xda app-developers app
ioitall said:
If you are wanting to root I would use the root injected rom. The instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1771687
This gives root but fully stock otherwise. It is probably one of the safest ways to root.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
That sounds exactly like what I, and others than are concerned about "warranty" issues on new phones- baring a total hardware failure would benefit from until the hardware is proven itself to be DEFECT FREE.
Would like to "burn-in" the device, making sure nothing is amiss.
Thanks!
mrRobinson said:
This is a completely stock ODIN flashable ROM with root injected into the system image.
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
Click to expand...
Click to collapse

What am I missing please?

Hello all
I am really hoping someone can explain this to me please. I have recently purchased a Samsung Galaxy Note 2 (N7100) from Vodafone in the UK direct. I was under the impression from this site, and general research on the Net, it has an unlocked boot loader and my experience with it thus far seems to validate that. I want to place a custom ROM on it.
Here is what I have done thus far. The device is rooted and is working fine from that perspective. Root checker and such like all say this is fine. Additionally, it supposedly has the correct and latest version of CWR on it, 6.0.1.9. This was done using the ROM Manager from the Play store. It is the non touch version, at present. However upon booting in to CWR I have no advanced options on the main menu. I would upgrade to the touch version. However, that is not free and whilst I have no issue paying for it, in principle, I am reluctant to, in case I end up in the same position with that version. It does not state what the upgrade version is. It states on the upgrade introduction page, it is also available as a free download from the clockworkmod website. However. after much digging through their website I land up back at the ROM Manager page in the Play store, which quite rightly says it is already installed. The only manual download I can find is for, yes you guessed it, 6.0.1.9 and that when expanded is simple an SU.apk and a few such related files. How that will flash the correct version of CWR with touch enabled etc. is anyone's guess? The device is currently running JB 4.1.2 and was pushed out to my device by OTA update just before XMAS. The baseband version is N7100BUDLL1 and the build number is JZ054K.N7100XXDLL4. The kernel is shown as 3.0.3-679347 and is dated December 11 2012.
I am at a total loss here. I have flashed phones a number of times and have never come across anything so seemingly utterly baffling. Is it actually possible to get a full version of CWR for this build please and, if so how please? I am very reluctant to wipe the phone and install a custom ROM until I can verify CWM is running correctly. Surely I cannot be the first person in the UK on Vodafone to want a custom ROM and the boot loader is supposedly unlocked too?
Yours desperately trying to understand what is actually going on here please. Any help and\or enlightenment will be gratefully received.
Many thanks in advance.
Regards,
Paul Lemonidis.
Use TWRP recovery for Note2 instead of CWM.
Flash it using odin.
nm8 said:
Use TWRP recovery for Note2 instead of CWM.
Flash it using odin.
Click to expand...
Click to collapse
Many thanks for your quick reply. I was wondering about that. I'll give it a try. It seems from what you're saying to ditch CWR as it does not work properly with my device for some reason? Just mine or all UK Vodafone models is my next question. So I am also left asking did CWR's own program to install CWR downloaded the wrong version of it for my model, despite being installed directly from the Play Store? Obviously I chose the correct model in the menu. Do I take it there is no CWR version that will work properly in my device, unless it is just my device, of course? I am just trying to understand what is going on here. It is more the lack of any sensible logic to this I find frustrating, more than actually not being to Flash the phone to be honest. Or is it just a dodgy installation? Although I have tried installing it by ODIN and Rom Manager the result is always the same. Everything says its installed fine but it just doesn't work upon booting in to it??!! I will try the other way now.
Paul-Lemonidis said:
Hello all
I am really hoping someone can explain this to me please. I have recently purchased a Samsung Galaxy Note 2 (N7100) from Vodafone in the UK direct. I was under the impression from this site, and general research on the Net, it has an unlocked boot loader and my experience with it thus far seems to validate that. I want to place a custom ROM on it.
Here is what I have done thus far. The device is rooted and is working fine from that perspective. Root checker and such like all say this is fine. Additionally, it supposedly has the correct and latest version of CWR on it, 6.0.1.9. This was done using the ROM Manager from the Play store. It is the non touch version, at present. However upon booting in to CWR I have no advanced options on the main menu. I would upgrade to the touch version. However, that is not free and whilst I have no issue paying for it, in principle, I am reluctant to, in case I end up in the same position with that version. It does not state what the upgrade version is. It states on the upgrade introduction page, it is also available as a free download from the clockworkmod website. However. after much digging through their website I land up back at the ROM Manager page in the Play store, which quite rightly says it is already installed. The only manual download I can find is for, yes you guessed it, 6.0.1.9 and that when expanded is simple an SU.apk and a few such related files. How that will flash the correct version of CWR with touch enabled etc. is anyone's guess? The device is currently running JB 4.1.2 and was pushed out to my device by OTA update just before XMAS. The baseband version is N7100BUDLL1 and the build number is JZ054K.N7100XXDLL4. The kernel is shown as 3.0.3-679347 and is dated December 11 2012.
I am at a total loss here. I have flashed phones a number of times and have never come across anything so seemingly utterly baffling. Is it actually possible to get a full version of CWR for this build please and, if so how please? I am very reluctant to wipe the phone and install a custom ROM until I can verify CWM is running correctly. Surely I cannot be the first person in the UK on Vodafone to want a custom ROM and the boot loader is supposedly unlocked too?
Yours desperately trying to understand what is actually going on here please. Any help and\or enlightenment will be gratefully received.
Many thanks in advance.
Regards,
Paul Lemonidis.
Click to expand...
Click to collapse
First of all update your firmware. You are vulnerable to sds.
Secondly as for your problem.
Go to cwm page in desktop mode and download the recovery for your phone. Touch or non touch anything would work. Then rename the downloaded file to recovery.img and flash it in recovery option via mobile odin and you are done.
Sent from my GT-N7100 using xda app-developers app

How to root official Lollipop - actual solution

So, the other day I got the 5.0 OTA on my rooted 4.4.2, and I naively updated it, without knowing that:
1 - I'd loose root and my recovery
2 - There's no way to root 5.0
After two days of trying stuff, I finally understood what many people know, I suppose, but I couldn't see it written clearly anywhere, so I thought I'd share. You have to:
1 - Flash back 4.4.2
2 - Root 4.4.2
3 - Flash a custom recovery
4 - Flash a rooted 5.0 from custom recovery
I now have a rooted 5.0
Here. It's not very complicated to do, but maybe it's so obvious for people who know it that they never care to put it like this (I'm not complaining, I actually did find all the information I needed on XDA and learned a good deal of things about my phone on the way so it's cool).
You cant.
DelBoy said:
You cant.
Click to expand...
Click to collapse
Sorry I lack experience so much with the forum that I posted without any content initially so you must have thought that I was asking for the solution. I get that you can't simply root 5.0, but you can actually get 5.0 rooted if your phone has 5.0 non rooted by switching to 4.4.2 first, which is really what people want to do when they ask that question. I have seen your answer before, and almost gave up trying, but I'm glad I insisted. Just saying "you can't" is just being deliberately unhelpful (or not knowing what you are talking about).
GordonFreemanK said:
Sorry I lack experience so much with the forum that I posted without any content initially so you must have thought that I was asking for the solution. I get that you can't simply root 5.0, but you can actually get 5.0 rooted if your phone has 5.0 non rooted by switching to 4.4.2 first, which is really what people want to do when they ask that question. I have seen your answer before, and almost gave up trying, but I'm glad I insisted. Just saying "you can't" is just being deliberately unhelpful (or not knowing what you are talking about).
Click to expand...
Click to collapse
Yeah, there was only name of the thread and word "So"
So I thought you were looking for solution :laugh:
Some more information on how to get there:
To get 5.0 rooted, you need to:
- take note of which 5.0 version you have on your phone and check you can get the bumped image somewhere, if you want to have exactly the same at the end.
- update LG PC Suite or at least the Windows drivers for the G3? Honestly I'm not sure how important this is, since I was playing around for hours and I did that in the process, maybe it's necessary. It is necessary to have the drivers installed at least.
- find the 4.4.2 version of the ROM for your phone (mine was V10e-EUR-XX), versions are different for 16GB/32GB versions.
- flash it with Flashtool (http://forum.xda-developers.com/showthread.php?t=2785089)
- root using your favourite tool (I used one I had on my PC, not sure which version but PurpleDrake should do: http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000)
- find a TWRP image
- flash TWRP (I used this tutorial: http://www.phonearena.com/news/How-to-flash-a-custom-recovery-like-CWM-or-TWRP-on-Android_id53914)
- find the bumped version of 5.0 for your phone (mine is V20e-EUR-XX and I found it on this forum)
- flash it using TWRP
- start the phone and set it up (it should be rooted already)
- install the SuperSU binaries using TWRP
Fun and heavy Titanium Backup freezes ensue! My phone has now 80% battery left 8h after being disconnected from the charger this morning, as opposed to 60% after two hours just after installing the OTA update.
Note: this was done on the unlocked 16GB European D855 version I bought in the UK. Not sure about other versions!
Bonus: in order to improve my battery life, besides Titanium-Backup-freezing the hell of the LG bloatware (I think McAfee and LG Health are the main culprits) and some Google bloatware I don't use (Google Play Apps anyone?) I also disabled knock on by following the advice #8 in this tutorial: http://www.androidauthority.com/lg-g3-problems-517832/
I've read all about the problem with rooting the G3 Stock Lollipop Version.
But there is no info, where I can find out WHY it is how it is.
So, why is 5.0 actually unrootable? And will this change in future?
SlideMouse22 said:
I've read all about the problem with rooting the G3 Stock Lollipop Version.
But there is no info, where I can find out WHY it is how it is.
So, why is 5.0 actually unrootable? And will this change in future?
Click to expand...
Click to collapse
Ummm. Have you tried looking on XDA?
There was a BIG post with details. The technical part is here: link
No, this won't change. Restricting services to their context means that bug in almost any service won't be able to compromise entire system. That's a great security feature, actually.

[Q] Update Fire TV?

Hi,
i'm currently on firmware 51.1.3.0 and i got my FT just lying around here and want to use it.
So my question is, should i upgrade to the latest firmware and just use it or be patient until a root for my version is released because of the efuse stuff?
Is anyone working on a new root method atm?
Raptor270 said:
Hi,
i'm currently on firmware 51.1.3.0 and i got my FT just lying around here and want to use it.
So my question is, should i upgrade to the latest firmware and just use it or be patient until a root for my version is released because of the efuse stuff?
Is anyone working on a new root method atm?
Click to expand...
Click to collapse
I doubt anyone is working on rooting newer firmware, cause they already have their firmware rooted so I doubt they have interest in rooting the newer firmware. Not trying to speak for any devs that have worked on these devices, but that seems to be the way it goes, they have already accomplished their goal of rooting the device so if newer unrootable firmware gets released its not really a problem for them. I am predicting right now that unless a new firmware with major updates gets released that requires you to have stock firmware to update then no newer firmwares will ever get root. I could be wrong, but I doubt it so its really up to you.
porkenhimer said:
I doubt anyone is working on rooting newer firmware ...
Click to expand...
Click to collapse
I have no doubt somebody is working on it. These are self-challenged, self-motivated people. And Amazon threw down the gauntlet.
As to Raptor's first question, you have it. Why not use it?
cant block updates on my router and dont want to update past the fuse update... -.-

New Nexus Owner Seeking Advice

Hi folks! Just received a 2013 Nexus 7 from my fiancé as a birthday gift. I wanted it for quite specific purposes so was hoping I could ask a few questions here and get pointed in the right direction before I start using this thing
I intend to mainly use the tablet for remote play with my PS4 and emulating old console games. Since I want to connect a PS4 controller to it wirelessly I'm told I need to root the device. I'm guessing this is an easy process and there are some guides on the site here?
The main thing I was after advice about is firmware updates. The system came on 4.3 and has already downloaded an update for 4.4.2 but I haven't installed that yet. Is this firmware fine to upgrade to? Any performance issues? I've heard people saying that upgrading their Nexus to 5+ (Lollipop?) has created a load of performance issues and this should be avoided? Also, if I upgrade to a certain firmware version can I lock myself out of being able to root the device? I'm pretty sure all of the apps I was planning on using work no 4.3 so I have no reason to upgrade at all but if I can go safely to a higher firmware that is reliable with no performance issues I may as well?
First time using an Android device so sorry if my questions come off as a little stupid. Also, wasn't sure if I should post this here or if it should be on the Q&A board so sorry if I've got that wrong!
As far as I know, the problems with lollipop were the standard number of complaints that come with any new release. Well, I'm not really positive, but lollipop seems fine to me and I think most people have upgraded by now. I would go for it because I think it's really fun to use.... Plus you can always revert if you choose.
As far as rooting, you never need to worry about not being able to do it... Rooting your Nexus 7 will always be easy. The by-hand method is fun and relatively simple, or you can just use the toolkit in the forum to do it even easier.
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Thanks for all the advice everyone
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
I'm fairly competent with computers (as I should be with a degree in computer science!) but this is all like a foreign language to me. I guess I'm better sticking with the toolkit for now until I'm familiar with all the lingo?
Masteryates said:
Personally, I'd stick go for 4.4.4, as 5, 5.0.1 & 5.0.2 all have a memory leak issue. You may also find more emulator compatability as Kit Kat has been around a year longer than Lollipop. The only downside to KK over L is the battery life is a little worse IMO.
I dont think the memory leak issue is a result of someone not knowing what they are doing etc.
Click to expand...
Click to collapse
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
chunk3rvd said:
Thanks. This is the sort of advice I was after and is why I mentioned what I was planning on using it for. The device has already downloaded 4.4.2 and wants to update to that. Is there a way I can manually go to 4.4.4? I'm worried it will just request an update from the Google server and try to jump straight to a version of 5
Click to expand...
Click to collapse
If you unlock the bootloader then familiarise yourself with ADB and flashing factory images, you can manually flash any version of Android (That has been availible for your device,) manually. You dont need to be rooted to do this.
It also allows you to go back when you've made the mistake of updating, (but does wipe all of your data!)
It ended up offering me the updates incrementally anyway. I went from 4.3 > 4.4.2 > 4.4.3 > 4.4.4 which I'm currently on and will leave it there for now. It's downloaded 5.0.2 but I've skipped the install for the time being
Think I need to do a little reading up before I root the device as I haven't got a clue what some of you are talking about haha. Thanks for all the advice so far though
No problems.
I've had a few Nexus devices and never felt the need to root them. :angel:
yosmokinman said:
^Yeah I'll echo that. Lollipop is good. The people having problems don't know what they're doing. Flash the factory image.
If you want root you can use cfautoroot or simply flash twrp with fastboot then flash the su.zip
Click to expand...
Click to collapse
The majority of problems stem from Qualcomms crappy broken mess Adreno gpu drivers, hence the delayed
rollouts of Android for the Nexus 4 and 7 that both use the Adreno 320, don't be suprised if the Nexus 4 and 7 get a
Android 5.1.1 release instead.
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
madbat99 said:
For ppl new to nexus devices, wugfresh nexus root toolkit is a great tool until you get the hang of adb and fastboot. With a nexus you can always switch between android versions. You can always root, or go back to older versions of android. Updating to newer versions never hurts anything because you can always go back. Its a developers device so its very versatile. Try lollipop if you like, (I love it) and if its not your thing, just flash back to 4.4.4. I love this tablet.
Click to expand...
Click to collapse
You for got to mention the disclaimer if your tab came with 5.x.x out of box you cant go back to KK. Also a lot of us who recently bought Nexus 7, I have 3 that I have acquired, came with 5.0.1 installed are having issues with partitions/memory mounting in recovery. Some sort of revision done in the latest batch sent out. If his tab came with 5.0.1 or higher and has his bootloader at FLO 4.04 he may have problems trying to go back with either bootloops and what not.
masterchiefb117 said:
... with 5.0.1 installed are having issues with partitions/memory mounting in recovery...
Click to expand...
Click to collapse
Seems to be solved in TWRP_multirom_(flo|deb)_20150328 (updated to 2.8.6.0)
See http://forum.xda-developers.com/showpost.php?p=45886569&postcount=1

Categories

Resources