Before I begin, I'd like to say that I do indeed have 8.3.1 firmware. I know there isn't much if any thing out for that firmware. If not, then please answer my questions under the hypothetical situation that I am running an earlier version so that I may have a better understanding of how everything works and apply that knowledge for future occasions. I know there are many other tutorials out for similar devices, but I'd like advice and tutorials as specific as possible for my device. I like details and specifics when I learn different things. I'm meticulous like that. Thank you.
Okay. Apparently I am special like the noob registration video says I am, but I am totally and utterly confused. I am no way savvy when it comes to modifying Android products in even the slightest way, and I request help even though my problem has already most likely been addressed multiple times elsewhere...
As the title of the thread says, I have a Kindle Fire HD 8.9" device running the 8.3.1 firmware, but I don't know where to even begin! I am seeing terms strewn everywhere like "root", "bootloader", "twrp", "go launcher", "CM10", etc. Some hacks bundle different things together, while others require one to manually install the other components yourself whatever they may be. My question(s), as vague as it is, is what in the world do all of these mean, which ones are recommended for my device, and in which order do I install them? I have looked at many tutorials how to do different things for different devices, but they seem to fail to explain all the pre-requisites and/or all the possible alternate paths you could take to further expand on your android experience. If they do, they fail to do it layman's terms where someone like me could even understand.
With all of that said (and asked), I would like to throw out one more question. Is there indeed anything for my device yet? I searched in the device search bar, but it only recognizes the 7" device, not the 8.9". Also, as far as what generation I have if that is even a concern, I don't know how to find out. I'm aware this is probably a handful to sort out and answer, especially in such a way that won't confuse the living daylights out of me, but if one courageous soul manages to do so or at least attempt it, I will be grateful. Thank you in advance.
Hi,
I'm new to this as well, but found the posts below very helpful. HTH.
[REF]All Things About Kindle Fire HD 8.9"
http://forum.xda-developers.com/showthread.php?t=2247428
Frequently Asked Questions - 2nd Generation Kindle Fires
http://forum.xda-developers.com/showthread.php?t=2228539
Related
Hello there! This would be my first post around these parts, although I've owned my Nexus S for around 7 months now and browsed these forums in the past. I'd also like to say that I realize this question might have been asked more than once already, but I've done my due diligence and searched without finding a definitive answer.
Anyway, I've decided that I've gone for too long without being able to flash ROMs, use all those sudo-required tools and whatnot, and I've decided to root my Nexus S so I can get some of the fun I've been missing. Now, don't get me wrong. I'm a software developer and I work with embedded systems for a living, but I just don't want to risk my $500 phone if I can avoid it. What this means is be as technical as you need to be, but I'd rather have the root process be a walk in the park and not an excursion to Mordor.
Anyway, my phone is a Nexus S i9020A(UCKF1, whatever that means), running Android 2.3.6. I've read this and this thread, and while the first looks like what I'm looking for, I recall my brother being able to root his Nexus One in a few clicks and I was wondering if I could do the same for my device. The second thread looks a bit more promising, but all I've found in that thread is mentions of other NS sub-models and not of my own, nor if running 2.3.6 means incurring in any risks.
As you can see, I'd appreciate some help here. Is there a painless, few-clicks method for rooting my specific device? If you have the same device, how did you do it? Do you have any experience with that tool I linked to?
Thanks in advance. If by any chance this has been asked before, do point me in that direction and I'll be equally pleased.
I am fairly lost on the process for updating my nook tablet 16GB to CM7 or CM10. This forum is like an information overload for a noob like me.
Two things I want to accomplish:
(1) Decide on CM7, CM9, or CM10
(2) Once I decide, update my nook
This is going to be a family tablet. Kids (older than 10) might use it a lot. I have read that CM10 is too unstable right now (especially for kids to use). Is this still true? I got the impression from this thread that there may be vast improvements:
http://forum.xda-developers.com/showthread.php?t=1877217
Cam someone tell me which version has the best combination of stability/performance? Is CM10 even close yet? Not crazy about the idea of going with gingerbread.
So, once I have decided, its not clear how I should update my nook. Are there simple instructions somewhere?
I'm sorry if I offend with this post, but it needs to be said - to you and the hundreds of other newbies coming on here with similar questions ...
If you can't figure out the basics of what you need to do by reading the information already posted across the existing threads on your device's forums then you should not even consider trying to do anything other than leave it well alone on the 'Stock' build.
The potential to break your nice, new, shiny device and find yourself in a position where you cannot recover it is high unless you are sure what you are doing, and the benefits really aren't enough for what you are trying to achieve.
SimonTS said:
I'm sorry if I offend with this post, but it needs to be said - to you and the hundreds of other newbies coming on here with similar questions ...
If you can't figure out the basics of what you need to do by reading the information already posted across the existing threads on your device's forums then you should not even consider trying to do anything other than leave it well alone on the 'Stock' build.
The potential to break your nice, new, shiny device and find yourself in a position where you cannot recover it is high unless you are sure what you are doing, and the benefits really aren't enough for what you are trying to achieve.
Click to expand...
Click to collapse
Your post does not offend me. I think I can figure out the basics. That's not a fair assumption about me. The problem is that I am seeing a lot of info on the web, and it is a little difficult for me to separate what I need from what I don't need. I see a lot of different info about which sd card to use or how the sd card needs to be formatted, etc, etc.
I just need one set of instructions that seems to work for most people.
But that only addresses one of my questions. The other question is whether CM10 is mature enough at this point or not?
In short, what I am trying to break out into discussion is simple - we need to figure out a way to reduce user-related/caused damaged devices.
I know we all put our disclaimers in our ROM threads, if you break your device, not my fault, etc. etc.... and before we discuss this I will say it is not our sole responsibility to make sure nobody does something dumb by installing firmware to their devices that may cause issues. What is inspiring this discussion are threads and posts such as this one, and they seem to be popping up more and more:
http://forum.xda-developers.com/showthread.php?t=2056369
http://forum.xda-developers.com/showpost.php?p=35793341&postcount=10
For the benefit of the general community and for people who, quite honestly, have almost no idea what they are doing when installing custom software to their devices, I think there should be a little more clarity and warning to users regarding what they should and shouldn't be flashing on top of their custom/packaged ROMs. And for the record I am in no sense of mind saying this could have been avoided by this user. In an analogical way I would say it is similar to teaching a child how to walk, or not play with light sockets. We cannot simply say, "oh be careful" because most people are careful, their issue is simply that they don't know. As developers we know EXACTLY what is compatible with our ROMs and what is not. This would include firmware, of all types - kernels, radios, build versions and modifications to the framework through flashable zip files in recovery.
More and more I am seeing threads like this one mentioned springing up about boot looping, lost IMEI's, and devices being destroyed because a user is (most likely) unaware of small differences between a device or installation method which if was aware, could have avoided an issues, and could have avoided another thread being posted wondering why "x" issue is happening. Of course there will always be these threads, issues, etc., but I feel like some type of quality control could be done on our part. This is what I propose, and I think we should encourage this among ourselves to avoid issues:
At the very top of our threads, the very top, before they see a download link, before they see a list of all of the exciting modifications amplifying their eagerness to flash, and dulling their eagerness to read, we should implement some "OP structure" so to speak. What I would propose is we all try to lay out our threads in this manner:
1. Name of ROM
2. List of ALL known compatible working (in this order): kernels, UI modifications (themes, etc.), firmwares. I would say that THIS is where our disclaimers should go. Right after telling the user what they should and shouldn't flash. This will strike up awareness on the other end (the user) that anything done outside of this instruction is a risk to the device and can permanently damage the device. This should be stressed even more in a thread where the developer has chosen to implement firmwares, builds/ROMs of other devices. The idea is more warning and thorough explanation of what can and can't be installed on top of our ROMs will in fact decrease user error. It is our responsibility to make an effort to decrease this possibility as much as possible. A quick list of useful information will go a long ways.
3. Recommended installation method as the developer has tested and proven - with a step by step instruction to flash.
People need to see this kind of thing before they see a download link. It will help the forum not be overridden by threads and posts of people wondering why something is broken (sometimes permanently), or not working correctly. This will also help troubleshoot issues as somebody will ALWAYS come back with "x" issue, and the first response by somebody should be "well did you follow all the instruction at the top of the OP?" and right away in a productive manner we are troubleshooting issues.
I believe we can ourselves "do some reading" and follow the work of our fellow developer members who spend tiresome hours building for various devices. Knowing what issues are going on with each other's work and thus knowing what our users are expecting will again only help everyone. Let's promote proper cautious behavior as an initial emotion when seeing a new update to a ROM, rather than the excitement of simply a new update. I know this will help, and it will make it easier on those of us who build and produce the software for our users.
I am curious to know people's thoughts about this idea - a structured method of laying out our threads with instruction and information, then the great things they have to expect after installation is complete. These are computers, not phones, let's treat them as such.
:highfive:
I am copying a thread over to this forum that I wrote up in the S3 section about proper flashing methods that have always worked for me flawlessly. There is never fault in taking extra time to make sure something is done 100% correct the first time, to rule out variables that might have caused "x" issue.
Here is the thread I was referring to. http://forum.xda-developers.com/showthread.php?t=1946701
This will be posted in the dev section as this is where people go to flash ROMs, putting it in QA is useless as that is where people go once they already have an issue.
Chime in boys, I really want to know what people think.
As someone who reads a lot of help i broke my phone posts the simple fact is that a large number of users if not the majority of noobs refuse point blank to read the instructions .
jje
This is also true. What I am getting at is by making information like this the first thing they would see, it would likely help reduce the "flasher flurry" that some people get into simply because of excitement and ignorance.
For those who don't read simply because they choose not to, we cannot help them. I believe there are many people, however, that proceed with caution, but are not informed enough. Simply saying "I am not responsible for your damaged device" is not enough in my opinion. I would revert to the child near the light socket analogy. It is not a enough to say "hey kid, you stick that fork in the light socket you may or may not be electrocuted - proceed with caution." We can do more, and we should.
I don't disagree about the need for this type of thread, but I'm not sure this is the proper section for it. This type of thread could (and probably should) be discussed across ALL android (and maybe even non-android) devices - not specific to samsung, exynos, touchwiz, etc. As well, it's not really a discussion of process, but more a discussion of how to advertise and support a firmware "product."
So, please explain how the OP fits the section guidelines here: http://forum.xda-developers.com/showthread.php?t=2017367
Thank you
Gary
Probably correct there Gary. If it needs to be moved I apologize. Not sure what I was thinking posting it here... it was late... I was tired lol
A simple solution would be to "hide" the download link in OP, so ppl are forced to read at least some of the OP.but there will always be ppl there is out of reach.
garyd9 said:
I don't disagree about the need for this type of thread, but I'm not sure this is the proper section for it. This type of thread could (and probably should) be discussed across ALL android (and maybe even non-android) devices - not specific to samsung, exynos, touchwiz, etc. As well, it's not really a discussion of process, but more a discussion of how to advertise and support a firmware "product."
So, please explain how the OP fits the section guidelines here: http://forum.xda-developers.com/showthread.php?t=2017367
Thank you
Gary
Click to expand...
Click to collapse
I agree gary, I've moved this to XDA general as this would cover pretty much any device, WP or Android.
Greetings,
Just a heads up about this model. Considering this is likely the most popular site for this arena, it is surprising to me that there isn't a specific forum for it. These guys do great work and no disrespect intended, however it is frustrating considering it is the one I, and many others, have.
With that being said, I will share what I have found in my endeavors to get it to where I want it. There may be some useful information in some or all of the other S4 forums, however in order to get what is truly needed, it is usually necessary to go elsewhere. I got some basic understanding of things here, but no true answers to this specific model.
This is the U.S. Cellular version of the Samsung Galaxy S4, SCH-R970. Although some of the tools and procedures found here for other models MAY work, as specific as it is to mod these devices, I personally wouldn't recommend using anything that doesn't particularly pertain to yours. It is very easy to get into a situation where you will need help and it seems there isn't much sympathy toward us when this becomes the case.
The good news is that there are plenty of other places to get what we need. It just takes a bit of research on this specific model. I must admit that I am a bit fuzzy about this stupid "forum etiquette" thing so I will choose not to say anything specific about other ones here, and vise-versa. What I will say though is not to get frustrated if you can't find what you need here. I guess things aren't always easy when we choose to avoid the "big guys" in the cellular carrier business.
What I did find is that if you feel like doing a bit of digging, it is no problem any further than that. I have CM 10.2.0 working just fine on mine, it just took a bit more research and going elsewhere. If doing a web search for "SCH-R970" doesn't get you enough info, try adding "U.S. Cellular" and/or "jflteusc" into your searching and something should turn up.
Happy modding :victory:
r.dunne said:
Greetings,
Just a heads up about this model. Considering this is likely the most popular site for this arena, it is surprising to me that there isn't a specific forum for it. These guys do great work and no disrespect intended, however it is frustrating considering it is the one I, and many others, have.
With that being said, I will share what I have found in my endeavors to get it to where I want it. There may be some useful information in some or all of the other S4 forums, however in order to get what is truly needed, it is usually necessary to go elsewhere. I got some basic understanding of things here, but no true answers to this specific model.
This is the U.S. Cellular version of the Samsung Galaxy S4, SCH-R970. Although some of the tools and procedures found here for other models MAY work, as specific as it is to mod these devices, I personally wouldn't recommend using anything that doesn't particularly pertain to yours. It is very easy to get into a situation where you will need help and it seems there isn't much sympathy toward us when this becomes the case.
The good news is that there are plenty of other places to get what we need. It just takes a bit of research on this specific model. I must admit that I am a bit fuzzy about this stupid "forum etiquette" thing so I will choose not to say anything specific about other ones here, and vise-versa. What I will say though is not to get frustrated if you can't find what you need here. I guess things aren't always easy when we choose to avoid the "big guys" in the cellular carrier business.
What I did find is that if you feel like doing a bit of digging, it is no problem any further than that. I have CM 10.2.0 working just fine on mine, it just took a bit more research and going elsewhere. If doing a web search for "SCH-R970" doesn't get you enough info, try adding "U.S. Cellular" and/or "jflteusc" into your searching and something should turn up.
Happy modding :victory:
Click to expand...
Click to collapse
I believe that the information for this device can be found in the Sprint S4 forums: http://forum.xda-developers.com/galaxy-s4-sprint
LOL
justmpm said:
I believe that the information for this device can be found in the Spring S4 forums: http://forum.xda-developers.com/galaxy-s4-sprint
Click to expand...
Click to collapse
Exactly
noob trying to get some xp and gain some knowledge.
i have the Amazon Kindle Fire 2nd gen running sysv 10.5.1
i have root access (kingroot, newest version. gained access once, then did factory reset, and did it again. kingroot stayed on HD after reset. idk why)
tested both times with es file mngr to ensure true / permissions
removed bloatware and advertisement apps. disabled some start-up processes snagged a couple of cool *root* apps and what not on the first go around.
only gained / access after the "factory reset" to not disturb too much and possibly fubar the whole gig when i'm so close to the goal
ultimate desired state atm is cm-11 (for otter2) TWRP 2.6.3.1 with some cool ass apps and blahblahblah
this is the guide im about to follow https://wiki.cyanogenmod.org/w/Install_CM_for_otter2 with the exception of the cable thing. i feel fairly confident that i can fastboot without it since i have superuser abilities and ive read several places that its doable but much safer and easier with the "sudo" cable. im a big boy. im willing to take a chance but if its not possible without the cable of paramount capabilities then it would be asinine to brick my **** "cuz i figurd it wud werk alright"
Sorry to be so long winded. just trying to be well detailed to make sure you guys know where i'm at in my little adventure.
So finally to the question
i've read two very different opinions on this from multiple people, in multiple threads, on multiple forums, etc.
is fastboot mode or state (however its referred to) achievable on the AKF(2ndGen) v10.5.1 as / without that eversofrustrating cable? like, is there a credible dev out there that says "yeah, dudes. f*** the cable. i just make it sudo whatever i tell it to" not necessarily verbatim but, you're smart, you know what im getting at.
simply put CAN IT BE DONE!?! (really im just trying to flash a rom on something that my wife wont remove my right testicle for bricking just to get a feel before using the fancy new trick discovered for LG G3 VS985. super excited. just the tot to 10 then kdz to 12 whatever whatever has me only slightly perspiring)
thank you for your time patience knowledge and inconceivable willingness to help losers like me who have a linux literacy of the 3rd grade on a good day. you guys are so awesome.
and im not just saying that. i swear
hello,
Welcome to XDA.
I have a KFHD7(1st Gen), the customization process involves installing a 2nd bootloader. I'm not familiar with the 2nd gen though.
Look through the Kindle fire forum linked below and see if there is anything to help you, you'll need to look through the "Android Development" and the "Original Android Development subforums there for all the custom mods for that device.
http://forum.xda-developers.com/kindle-fire-hd
If you can't find what you are looking for then you can post your question in one of the Kindle fire Q&A forums linked below(whichever applies to you).
http://forum.xda-developers.com/kindle-fire-hd/7-inch-help
or
http://forum.xda-developers.com/kindle-fire-hd/fire-2-help
or
http://forum.xda-developers.com/kindle-fire-hd/8-9-inch-help
If those don't help then try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help.
Remember to register an XDA account so you can post and reply in the forums. Good luck.