Related
OK so my G Tablet is on the way and I've been reading and came across a comment on another forum that the ROM's that exist are built on the original stock software and that the most recent update may be causing problems with CWM? I will be getting my G Tablet on Wednesday, should I not do the update if I am going to be flashing a custom ROM? Thanks in advance!
drum747,
I believe everyone should make their own decisions. But if you ask me -- I'd tell you to simply stick with a stock G-Tablet right now.
When you get yours and go to Settings/About you can see the version -- something
like 1.1.xxxx -- probably 3588. If not, just about as soon as you get wifi connected
it will offer you an OTA (on the air) update to 3588. That's the current working version, and compared to the crud we had back last November it really isn't bad software.
It will lack the Market and some other things...you may have to be patient there.
But you can still side-load apps and download apps directly from a number of places.
But we are waiting. Our devs have found that there is software for a possible
Update 3991. The hope is that OTA 3991 will come down in the next few weeks.
If so, at 3588 stock you will be in perfect shape for that update. And then once you
have worked with it a while, you will be able to decide whether to stick with it -- or look at other options.
It seems like everyone who come in here looks at the ROMs available like a "all-you-can-eat" buffet. The immediately start flashing ROMs and moving around software
until something goes wrong and they are stuck. Indigestion!
With a good 3588 tablet, you can read and interact here and find out the biggest and
the best, and you can learn what you need to that when you are ready you can
move up to whatever you want without problems.
Do what you want. Enjoy the G-Tablet. I think it pretty darn good!
Rev
I agree.........
Stick with the most current stock version 3588. The next update officially available from viewsonic should be very soon, but I don't think it will be 3991 as advertised
3558 was different than what it started as, or it would seem based on what I have gathered from reading old threads.
ale
You know, I have a Droid X and have really enjoyed rooting it and trying different ROM's and was really looking forward to the same type of experience on this tablet. What is the advantage of waiting until the next update? Can't I update, do a full backup and go back to that if I want? Once I install a different ROM, I am then stuck at whatever update and no further updates? Is that why you are saying to wait? Are you saying there will be even better ROM's down the road based on the new update that is coming? Or just that the new update coming might have all the things we would like?
The next update might have some cool stuff... might even be as good or better than the custom stuff here... maybe...
Question is... did you buy the tablet to use it for media consumption or tinkering?
Answer that and you'll know what to do. Just don't forget to make nvflash to factory stock your best friend ;-)
A little of both I guess. Part of the reason I chose this tablet over others is because of the support and customization (and price!) I will try to wait for the next update before I tweak it (if I can!) Heh!! Thanks for the responses guys!! I appreciate the input!
K J Rad said:
The next update might have some cool stuff... might even be as good or better than the custom stuff here... maybe...
Question is... did you buy the tablet to use it for media consumption or tinkering?
Answer that and you'll know what to do. )
Click to expand...
Click to collapse
This is without the best quote I could image. Tinkering without first using the tab and getting to realize it's not a giant phone is the first step I think everyone should understand.
And if you do tinker then you should expect it to have opportunities (problems ).
drum747,
Not addressing your abilities or anything about you.
But read all the crash and burn threads on this forum.
IMHO, to many people are trying to do to much too fast and are
messing up their tabs and have to be bailed out.
I'm just saying be cautious, move slowly and carefully and
don't get into trouble.
However, my advice still stands. If you move on to other
ROMS, etc. now, you will cut off access to offline updates.
Then you will have to go back to stock, etc. And
sometimes going back is as much as problem as going up!
It still would be easier to stay stock now and if an update
doesn't come down soon -- you will have read and learned
and be ready to make choices.
IMHO.
Rev
IMHO... if it ain't powering your pacemaker then learn how to nvflash and have fun.
Be part of the revolution or watch it happen... ;-)
Thanks guys! I get what you're saying!
Sent from my DROIDX using XDA App
K J Rad said:
... learn how to nvflash and have fun.
Click to expand...
Click to collapse
QFT.
nvflash is not hard to get working. With a properly set up nvflash procedure and all the info on these forums, the gTab is an unbrickable as it gets.
updates
I upgraded to the vegan 7, gingerbread, how do I go back to the original stock to get the latest updates from viewsonic when update arrives?
Second that
I absolutely agree to stick with the stock ROM and play for a while. The 3588 update is very stable and usable when you change to Classic Home. I have been using it till now, side loading apps and enjoying a lot without having to worry about custom ROMS and such.
The people who are saying stay stock for the updates are glossing over the fact that the Vs updates will just make the stock UI suck a little less.
Before I bought my G tab I had never had any experience with tablets or smart phones or even android for that matter. I have flashed 4 or 5 roms onto my tablet without incident, no boot loops, no dead tab, no anything that anyone would consider a bad experience. I'm using Vegan 5.1.1 for the record, for the third time.
Read a few of the reflash to stock with nvflash threads to prepare yourself in case something does go wrong, but there is no reason to stay stock on this tablet theres to much dev goodness and too much customizationability ( is that even a word?) not to try different things.
Roxxas049 said:
The people who are saying stay stock for the updates are glossing over the fact that the Vs updates will just make the stock UI suck a little less.
Before I bought my G tab I had never had any experience with tablets or smart phones or even android for that matter. I have flashed 4 or 5 roms onto my tablet without incident, no boot loops, no dead tab, no anything that anyone would consider a bad experience. I'm using Vegan 5.1.1 for the record, for the third time.
Read a few of the reflash to stock with nvflash threads to prepare yourself in case something does go wrong, but there is no reason to stay stock on this tablet theres to much dev goodness and too much customizationability ( is that even a word?) not to try different things.
Click to expand...
Click to collapse
Yeah I think it all boils down to what the individual wants and is willing to risk..this forum makes it easy and there are plenty of options to try just always prepare for the unexpected and dealing with the experimentals expect anything to happen!!
Who am I kidding?! There is no way I will be able to wait for the next update. I already have a ton of files set up to load on my G tablet. I will be Modding within hours of my full charge! Guess its just my nature! Thanks guys!
Butch, thanks I will be reading everything to make sure I do it right Thanks for the advice everyone!
Sent from my DROIDX using XDA App
Closing Word...
Everyone that has contributed to this thread--
I have tried to voice the side of conservatism and restraint and
good judgement in this thread. My intention was not to hurt any
feeliings or pick on anyone or rain on anyone's parade.
But if you read what's going on in these forums, there are a lot
of folks having problems. A lot of them are in over their heads and
some have been careless and others made honest mistakes.
I know for my part, I have been working hard to try to help folks
find the tools and make the decisions to get back on track. I'm sure
I have made mistakes and my opinions are mine!
But I speak for myself in saying that even though I am semi-retired
and have more time than most -- I can't keep up this pace. And I've
heard others of the helpers say the same thing.
I also call your attention to the "TwoTapsX" thread and the fact that
the moderators are aware of the problems people are having. Roebeet
has put together a splendid ROM that many think will be the next
generation of G-Tablet software. But because of the complexity of the
mods folks already have had in the tablets, and because of the human
factors listed above -- a lot of folks have messed up their tablets.
In My Humble Opinion: Somebody has got to say that in spite of all the
"opportunities" for mods in these forums -- folks have got to start
exercising more restraint, more good judgement, more common sense in
what they do.
The devs and the folks who are helpers here can't be expected to carry the
load of keeping everyone up and running with the current problem rates. I
sometimes don't agree with the moderators, but this time I see their point.
We users have a good thing here, but if it keeps being abused......
********
Having said that, I am done here. I wish you well.
Rev
/EOT
Just an update. Within an hour of booting up I had installed CWM and Vegan. It was an easy process and now I love my g tablet!
Sent from my DROIDX using XDA App
Welcome! Enjoy the koolaid... ;-)
Nice responce
Just received my TF201 Asus Transformer Prime today.
http://i40.tinypic.com/21dlpc9.jpg
I'm looking for a method in rooting the device.
I'm aware that RazorClaw is suppose to work on the device but could anyone confirm that it there are no bugs which would possibly brick the device etc?
PS. This is my first tablet / android device so please bare with me.
Thanks In Advance!
Where'd you order from?
clankfu said:
Where'd you order from?
Click to expand...
Click to collapse
Supercom, in Canada
I'm not rooting till ics comes ota
I think you will be fine rooting that way. There is a site that reviewed th tfp and they used that root method and they said it went well with no issues.
What the hurry ?
It might not be a bad idea to wait until the unit is burned in, and you are satisfied that everything is working perfectly before mucking around (i.e. rooting). Then, if you have problems, you can more certain that the problems are attributable to the rooting.
Enjoy your Prime
Could anyone brief me with the cons of rooting the device? :|
Research first, especially with this being your first android tab. Don't be over anxious n go bricking your device..lol.
Was there an immediate notification for an update after you opened it? Razor claw supposedly doesn't work after Asus pushed a system update. It was rooted prior to update on in-store demo model.
What's reason for eagerness to root so quickly? There are no custom roms or anything out yet. It's not 3G so no tethering. If you root and uninstall system files/bloatware you won't be able to do OTA update to Icer Cream Sandwich. Which means you will have to wait till someone here makes a version, which might not for a while.
Sorry that this is off topic, but does the color you ordered seem true to the advertised pics?
Expliciate said:
Could anyone brief me with the cons of rooting the device? :|
Click to expand...
Click to collapse
Good thing we have search engines....
1. Technically voids warranty and may not allow OTA updates.
2. Possibility of a brick if you don't know WTF you're doing.
Huummmm... cons of rooting..... hummm... don't rush, still thinking.... possible OTA update issue, very unlikely, but still possible I guess; most of the time the OTA will just erase the root.... uummmm yeah, that's about all I can think of.
Also, guess there's a very small chance of a soft brick... but I would tend to think that the root will either take, or it wont... but there's still a chance I guess.
IMO, the benefits far outweigh the "possible" consequences.
Wish I had mine, I do it in a heart beat.
RussianMenace said:
Good thing we have search engines...[/url]
Click to expand...
Click to collapse
Riiiiight. Thanks
These days when there's a one-click for everything...it's very hard to jack anything up. Now, going in manually...there's always risk of operator error.
Swiftks said:
Huummmm... cons of rooting..... hummm... don't rush, still thinking.... possible OTA update issue, very unlikely, but still possible I guess; most of the time the OTA will just erase the root.... uummmm yeah, that's about all I can think of.
Also, guess there's a very small chance of a soft brick... but I would tend to think that the root will either take, or it wont... but there's still a chance I guess.
IMO, the benefits far outweigh the "possible" consequences.
Wish I had mine, I do it in a heart beat.
Click to expand...
Click to collapse
With this being his first tablet and Android device period, seems like he wants to root just for the sake of saying he's rooted. You know very well what happens to a lot of new people to Android that just jump in and want to root w/o thoroughly doing the homework first. Lmao
demandarin said:
With this being his first tablet and Android device period, seems like he wants to root just for the sake of saying he's rooted. You know very well what happens to a lot of new people to Android that just jump in and want to root w/o thoroughly doing the homework first. Lmao
Click to expand...
Click to collapse
That's true... since it is his first Android device, he might want to let someone a little more experience take the lead, just in case...
ATM, other than de-bloating there is very little reason for root.
Does anyone know by any chance the official release date of ICS?
I'm aware that it has been "released" to certain phones like the Samsung Galaxy, but when would it be made available to the Asus Transformer Prime? o_o
RussianMenace said:
ATM, other than de-bloating there is very little reason for root.
Click to expand...
Click to collapse
Yeah, no other reason... except de-odexing, themeing, TI Backup, freezing, editing database files, changing VM Heap size, installing custom scripts, overclocking/undervolting custom kernels, disabling startup processes.... that's just off the top of my head.
Expliciate said:
Does anyone know by any chance the official release date of ICS?
I'm aware that it has been "released" to certain phones like the Samsung Galaxy, but when would it be made available to the Asus Transformer Prime? o_o
Click to expand...
Click to collapse
No Official date yet but could be by end of this month or mid Jan. It literally could be anyday. Just keep a lookout on an update notification popping up. Or even go to settings and about. Then click on system or whatever to see of it searches and finds an update for your device.
Expliciate said:
Could anyone brief me with the cons of rooting the device? :|
Click to expand...
Click to collapse
Everybody says root root. The new roms come out fast... I did it with my original tf and roms don't come out that fast especially if Asus is going to push ICS soon. I'd wait a while especially since a lot of potential devs won't get their unit for several weeks or months!
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
what is your question specifically?
just curious about what they are and do basically.
kevinallen4325 said:
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
Click to expand...
Click to collapse
I'll try and help.
First you must ROOT your phone. This basically grants you access/permission to FIDDLE with a lot of things you can't normally. I use the word *fiddle* loosley, meaning you can install root tools (like overclock) custom Roms, change system settings, flash themes... the list goes on. It's kind of like the equivalent to "jailbreaking"
Rooting is the "first and foremost"... basically do this first. and all other things follow.
kevinallen4325 said:
just curious about what they are and do basically.
Click to expand...
Click to collapse
Well the sticky in the main forum really is a good place to start, as all these terms are defined there:
http://forum.xda-developers.com/showthread.php?t=1483113
As well as step-by-step instructions how to root. That should get you started!
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It is much more than that. I wrote this out before, so I will copy it again:
People have problems when rooted because they are not careful or do not know what they are doing. Rooting gives you (to put in Windows terms) full Administrator rights to your phone. With this right comes responsibility, so you must be careful and do research. This is why rooting also voids the warranty. The phone is now open for the user to do whatever they want, and circumvent any restrictions put on the phone by the manufacturer (including those in place to prevent harm to the device). But like a computer with Admin rights, rooting allows you to install any application, any "OS theme", and tweak the hardware to do what YOU want with it, not what the manufacturer wants.
So please be sure to READ READ READ all you can before you start!!! You don't want a $600 phone coaster. Just browse the forums for a couple weeks and learn from the posts.
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
Android isn't like iOS. I had an iPhone for four years before my Note and I know where you coming from. What the other guy was saying is that rooting can be viewed similar to jailbreaking, but it is kind of completely different. You don't need to be rooted to use themes (or most of the stuff on Cydia). Rooting allows you to back up apps, flash custom ROMs, etc. Otherwise, you most likely don't need root.
tbran said:
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
Click to expand...
Click to collapse
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
kevinallen4325 said:
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
Click to expand...
Click to collapse
Trust me, if you go the root and custom rom way, you will never install an official update. not because you can't, but because it will be leaked and debloated months before it is official.
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
I rooted my Note a couple days ago and am still trying to figure out the benefits of doing so. I guess just spend time reading through this forum for the answers. That's what I am doing, but so far I see no benefit at all. The phone does all I want it to do so far. Maybe I am missing something.
Also, When i run quadrant, the scores are consistently lower after rooting the device then they were before. Not sure why though.
You are correct that the Note and newer phones may need no help. Not like two years ago. But, the big advantage to rooting even if you don't want to flash roms is Titanium Backup for app mgt and nandroids or full image backups--imho. The other like mentioned is earlier os releases. I have had ICS on my N1 for quite awhile and is still not on most new phones.
Ken
kevinallen4325 said:
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
Click to expand...
Click to collapse
If you are sure you are rooted, a dialog box with a little Android head wearing an eyepatch will pop up asking if you want to allow the application to have root access. You must allow it here.
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
ljwobker said:
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
Click to expand...
Click to collapse
Depends on how you used SafeStrap. If you ONLY installed in the stock rom, then an update likely would do it. If you installed safestrap a second time from the working rom-slot as well, then updates won't work, because the BL & Kernel CANNOT be flashed.
The best thing is to remove all wifi connections with "forget network", then go into safe strap & activate stock rom. Then go back to the boot options & delete the rom-slot you created. Boot back into stock partition, uninstall Safestrap & then reconnect to wifi & check for updates.
I would HIGHLY recommend you follow my directions about forgetting nearby, if not all, wifi networks. If you turn wifi off in a slot, but not in stock, or vice versa, it can cause boot issues , as well as wifi issues.
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
EniGmA1987 said:
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
Click to expand...
Click to collapse
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
GSLEON3 said:
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
Click to expand...
Click to collapse
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
EniGmA1987 said:
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
Click to expand...
Click to collapse
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
GSLEON3 said:
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
Click to expand...
Click to collapse
lol. I am glad you know your FACTS. No need to act so butthurt.
Hi all. I am hoping for some very basic advice. I got a Kindle HDX 7 a few days ago. I have not connected it to wifi yet to avoid automatic updating of the firmware. When I go to settings>device>system update it tells me that my current firmware version is 13.3.0.5 installed on Jul, 30, 2013. From all I have read that is a good thing if I want to root my device.
The big question I have is if I actually should?
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
-Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
-How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
-How would I keep my device from upgrading automatically after rooting?
-Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
I would appreciate if the experienced rooters amongst you could advise me on this. Thank you!
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
snorklm said:
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
Click to expand...
Click to collapse
This is entirely doable, not all builds are buggy.
snorklm said:
Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
Click to expand...
Click to collapse
Not completely, but since root is what you are after currently, go to the dev section and check out the roundup on the rooting tool. Read through the posts.
However, it is simple for you to root. You can go to towelroot and do it that way. Regardless, I suggest reading the dev threads to see some of the other options. Also, there is some good info in the rollback, now what? Threads in this section.
snorklm said:
How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
Click to expand...
Click to collapse
All it does is give you the option of allowing root permissions to an app. Root in it of itself is perfectly harmless. It won't change the function of the device at all if you do not utilize this new power. However, if an app (or you), change the wrong file, it could be devastating.
snorklm said:
How would I keep my device from upgrading automatically after rooting?
Click to expand...
Click to collapse
There are some block updates threads. Probably the easiest is to use the kindle fire xposed plugin (I think that still works). Be careful with xposed. It does allow you to make changes which can make your device unstable.
snorklm said:
Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
Click to expand...
Click to collapse
Yes, and achieving root access is looked at as a security hole by Amazon. You also will be missing out on new "Features." This could include KitKat. Although, you can flash the new software with TWRP which if done correctly will be stable, but that will require a lot more reading. It is really only the custom builds which are unstable. They are buggy because they are not quite finished. Head over to the dev section to find out more. In the end, it all comes down to what you plan to do with it, and how much you plan to learn along the way.
Good luck,
Leko
Sent from my KFTHWI using Tapatalk
Hi Snorklm - welcome to the forums. The title of your post made my day
If you haven't already read through the response from Leko. Hits all the important points and mirrors what I was going to write (beat me to the punch).
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
I know you were hoping for a step-by-step tutorial. While that may become reality someday I suggest you spend an evening reading through the forums before deciding on a course of action. Yup, a ton of information is old/confusing but there is no one right answer for everyone. Ask questions along the way. Lots of folks are happy/willing to help if you've done your homework.
Good luck!
lekofraggle said:
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
Click to expand...
Click to collapse
Thanks for the overview and answering my questions! I'm still iffy on the whole process but I'm going to do some reading before I decide if this is for me .
Davey126 said:
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
Click to expand...
Click to collapse
Thanks for the reply. I'm especially grateful that you name-dropped some specific recommendations because it gives me a starting point to research. I have already read about TWRP (though as of yet I have no idea how to install it) and I will definitely take a look at HDX Toolkit.
I am probably going to try rooting while keeping an eye on the stock Android variant. I'm not sure if I'm ever going to be brave/clever enough to dare try that though. Bricking my device would seriously make me cry .
I have one more question about the Firmware versions (well, I probably have several, but this is the only one I remember right now.) I have seen somewhere on this forum that you can also upgrade the amazon firmware manually until you have the version you want instead of getting pushed to the newest one from amazon itself. Is that correct? If yes, which is the best version to stop on while still being able to root and keeping the option of stock Android open? I ask because I would like to strike a balance between a reasonably upgraded OS and one I still can do stuff with without getting nannied by amazon.
Here is where I recomend you start reading.
http://forum.xda-developers.com/showthread.php?t=2986004
This is the link for the thor twrp.
Here is how a normal device works.
You gain root permissions, and then if you mess up, you jump into a recovery and fix things. You probably (definitely) will lose some data, but you learn, curse, and move on with your life.
However, the bootloader of the Kindle hdx is locked. This means that if you cannot boot right, and you cannot get to recovery, you have a 200 paperweight.
Now, on the old firmware, brilliant people found a way to unlock (sort of) the bootloader. So, you have a pretty universal reset switch. This is why the recommendation is there to grab twrp. It really is helpful if you have a hankering to tinker. In reality there is less of a risk of bricking the device with it. Once you have it, then you can update to the newest firmware (in theory) if you do so the right way, you still keep twrp.
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
I hope this helps.
~Leko
Sent from my KFTHWI using Tapatalk
Edit: whether you go the easy route, and choose towelroot (just google it or go to towelroot.com for that route), the more involved twrp, or something in between, I highly recommend you learn what adb is and how to use it. The hdx toolkit comes with the drivers and it is not too difficult to use, but it is essential if you get into a sticky situation. Here is the toolkit link.
http://forum.xda-developers.com/showthread.php?t=2665683
lekofraggle said:
I hope this helps.
~Leko
Click to expand...
Click to collapse
Yes, this helps. Thank you! :good:
lekofraggle said:
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
Click to expand...
Click to collapse
@snorklm - you can go up to 13.3.2.6, secure root and still retain the option to later install TWRP and a different ROM without having to engage Amazon for a downgrade (you will still have to roll your device back to an earlier FW before installing TWRP but you can do this yourself). Note the 13.3.x.x series is based on the previous version of Fire OS (which in turn is based on Jellybean) but it remains perfectly serviceable. A lot is happening with more recent Amazon firmwares which ultimately may allow other ROMs and recoveries to be installed without having to downgrade to 13.3.x.x. Keep an eye on the forums.
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
I don't mind about the warranty as I think I will not break my Kindle Fire some how, just care about the services from Amazon Prime.
Actually I already contact Amazon service to roll back to version 3.2.5 and I'm waiting for the instruction email. My plan is going to root it, play around with the device then if something doesn't satisfy me, I will do un-root.
Would anyone show us the real advantages of rooting Kindle Fire here? As far as I know basic users just root their device to install Google Play Store which can be done on other un-rooted ones (like the method of Imma Wake) I still like Amazon service for Movies streaming so I'm a bit confused of what to do next, keep update it accordingly or give Rooting a try
Please share more your stories here.
Thank you
leoclark said:
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
Would anyone show us the real advantages of rooting Kindle Fire here?
Thank you
Click to expand...
Click to collapse
I ran with 3.2.6 (rooted) for nearly a year before installing a different ROM. I was able to obtain most apps from either the Amazon store or 1Moble. The primary reason I rooted was to squash various Amazon services that launch at boot and consume resources in the background (CPU, memory, battery). Goodreads, FreeTime and numerous communication services to name a few. I also wanted to install Xposed for a few modules I find especially handy and block OTAs to retain maximum flexibility. I side loaded many gapps but never installed the play store and associated services. Also Opera (never liked Silk). I retained my Prime privileges and for the most part enjoyed the mostly stock tablet as Amazon intended. Ultimately I began to miss some purchased apps not available elsewhere and longed for Apex or Nova. Other launchers can be made to run on Fire OS but the experience isn't as fluid. There is also something to be said about having a fairly consistent UI across my various Android devices.
While Fire OS isn't horrible I recommend rooting (when possible) and blocking OTAs to maximize current/future options As others have pointed out the act of rooting generally does not introduce instability unless the method used to exploit a vulnerability has side effects or the conditions for root are not fully met. There are some risks as you now have the power to brick your device. SuperSU (or similar privilege manager) is your friend and should keep you out of trouble if used judiciously.