I feel really stupid on this forum. Everyone is so smart and knows what their doing most of the time. You all talk the lingo and I'm lost half the time. I'm trying to play catch up, read and learn as much as I can. How did all of you learn this stuff? I'm searching these forums and googling everything! I'm a new Android user(obviously)and I love my Nitro, minus the horrible battery life. I really like the fact that these phones can be modified a lot. So far I've rooted my phone and did the no carrier, blue icons and battery % mods.
Now that my 30 days is over, I can NOT screw up my phone. Basically I'm not going to do a thing to it till I have a clue. I guess there's a de-bricking write up, but that is CONFUSING as hell to me. I just need lots of detail, pictures, or better yet, a video to learn that kind of stuff. Reading how do the CWM doesn't look too bad, only because I googled it for the Nitro and there's already a few cites that made a clear write up. Installing a custom ROM doesn't look to hard either. However, all the modifications to these ROMS is overwhelming. Back to Google I go for all of that stuff stuff. I just figured out how to use Titanium Backup Pro, I think. What isn't clear is how to restore my phone with the apps/contacts after a custom ROM is installed. I know theirs more I'm forgetting, but that's enough for now.
I'm not ranting, just slightly frustrated don't understand it all. Not really sure what I want out of writing all this. Maybe some guidance, help, insight and or some answers to some of my questions. Thanks for reading!
It's not you, it's just like picking up on a computer, it takes time. I'm still a noob my most standards. I'm on my 3rd Android phone and know my way around my phones, but I don't know anything about development and don't really know my way around the Android file system that well. Here are some common terms that may help you out.
ADB - Android Debug Bridge, used for running commands to your device from your computer
Fastboot - It allows you to connect to your phone and run commands without booting entirely into your rom
CWM - ClockWorkMod, most common non-stock recovery tool
Bootloader - This partition loads your rom or recovery depending on what you need / select
If there's anything you're curious about just ask and I'm sure someone will help out. My ADB and Fastboot definitions are from my very limited understanding.
Check this out too, should be helpful. Found it on Google.
http://forum.xda-developers.com/showthread.php?t=619153
You'll do just fine so long as you don't try to do too much too soon.
I got started by simply rooting my AMOLED DROID Incredible, following some online guides. After that, I removed some bloatware. I kept reading about how to do more and once Cyanogenmod 7 came out for my phone, I used it. I've stuck with it ever since.
There are other things I'd like to know, too, like if I can get remove stock applications when I'm already using replacements (browser, email, messaging, etc.). But that might have to wait until I upgrade my device so that I can try it on this phone and not the new one.
Anyway, I hear ya when it comes to the steep learning curve. Baby steps, man. Baby steps. You'll get there in due time.
Sent from my AMOLED DInc using XDA App
Man, you haven't lived until you brick your brand new first android phone within a week and a half of purchasing it off contract I almost shat bricks, I thought my phone was a lost cause.
1st andoid device for me too but I love the customization that it provides and dont like the risks. The biggest mistake I have made so far is getting stressed about change. Consequently, I will lose some patience and not follow a direction properly or think through a step like I should.
I did start with TB pro aswell but still broke my phone by freezing the stock launcher then later doing a factory reset. But I would have avoided that if I had been more patient and doublechecked what I had frozen prior. The good news is that caused me to dive in to Malninion's debrick guide which forced me to learn the basics of accessing this phone through the computer and issueeing commands which are all pretty straightforward albeit uncharted territory for me.
Now that I have a basic idea of how to use the basic tool kit I will be installing the cwm but I am waiting a bit longer to let any issues reveal themselves and more importantly see how folks really o er from those issues. Then after getting a better understanding of wtf cwm is ! I will instaall/ flash one of the custom roms after giving them a bit of time to sort themselves out as well.
So basically my strategy is to go slow, don't jump right on with a new dev until those more knowledgeable about it do and give it a good going over.
So now I'm trying to read how to use Titanium Backup to restore your apps after a you install a new ROM.
I found this> http://www.androidtablets.net/forum/viewsonic-gtablet-technical/12513-howto-titanium-backup-restore-apps-system-data-new-rom.html I know not to restore system data though.
Now what is frustrating is this: (If you have the donate version, don't forget to save your TitaniumBackup_license that is in the root folder.)
I have the Pro version, that I am 100% sure and it all works. What I think is my root folder, there is NOTHING in there (/root). I tried a search using Root Explorer and looked in Astro. I can't find my TitaniumBackup_license.txt file. I've google searched trying to find where it is and apparently it's a big secret that everybody knows but me.
It's really easy once you do it a few time's, if you need help let me know.
Hello, I'm brand new here, and found my way here after purchasing my Kindle Fire last week, and upon receiving it, almost immediately did a Google search for "hacking the Kindle Fire".......just to see what people were doing to this device.
I was pleasantly surprised at how much more they are capable of. I've never owned a tablet of any kind, and I'm one of the half dozen people on the planet that doesn't yet have a smart phone, lol.
That being said, I did a few minor hacks on a couple different cell phones in he past, I just built my first computer, and it actually works, with no problems......so far anyway, lol.
What I'm getting at is.....messing around with a device doesn't intimidate me too much, and I'm not a complete stranger to tinkering with electronics, and I like the challenge, BUT, I'm far from an "expert" or as knowledgeable as a lot of you that post here.
Now, to the point.......
I saw this thread
http://forum.xda-developers.com/showthread.php?t=1399889
And that utility seems pretty straightforward, and after watching a youtube video on how to use it
http://www.youtube.com/watch?v=mwMHIkX20YI&feature=related
I think I will try it......maybe not right away, but in a couple weeks or so.
My Fire is being replaced by Amazon for a screen issue, and a couple other things, but anyway, I already tried just the Go Launcher Ex app, and that made quite a bit of a difference to me. Just getting rid of that stock carousal is worth it. Actually, If I could set a few of those Go wallpapers and make them stick, I'd be content for a little while anyway.
But...as far as rooting it, and please correct me if I'm wrong.....after using that utility, you're pretty much good to go, correct? I mean, as far as the Fire being able to do much more....more apps available, and getting more of a true Android OS out of the Fire etc.
If I follow that video carefully, how much of a risk is there of breaking my device, or anything really going wrong? Am I getting in over my head, or is this pretty simple stuff? I bought the Fire because it's as close to a full fledged tablet as I can afford, and now I'm learning that it can be much more of a tablet than it is, so is it worth the risk?
I'm just trying to get some kind of consensus from you people that know this like the back of your hand, if I may be biting off more than I can chew or??? And, what are the major benefits of rooting that I haven't already seen?
Thanks in advance for any input, and for reading my semi rambling post!
From my experience it has shown more beneficial to learn the command line methods first rather than going straight to a utility like the KFU.
Depending on what you want out of your Kindle Fire experience, it can be troublesome or very easy.
If you want to run a rooted straight stock interface it's slightly more work and you run the risk of Amazon's OTA updates reeking havok on your system, but there are ways around that.
If you want to run a custom rom the process is much easier as all custom roms come pre rooted. And if it's the stock Kindle Fire interface you want, there's a custom rom for that as well.
The biggest thing is installing custom recovery which, as of now, is the only thing you have to do via the command line.
Next would be installing a custom bootloader. The bootloader allows you to use the power button to enter recovery and the most recent version (1.4) allows you to change your bootmode, which will prove very useful in a pinch. Also the new bootloader is flashable via recovery, drastically reducing the possibility of "bricking" your device.
After that, installing and switching between roms is easy with recovery.
There is an immense knowledge base here but it isn't very organized and the search function has a bit to be desired. But if you look around, you'll see most of the same problems are repeated throughout (usually due to lack of experience or user error or both).
The guide posted at this link is a must for any Kindle Fire user so check it out. http://forum.xda-developers.com/showthread.php?p=23747567
Read through the second and third posts as well.
Good luck
And at the end of the third post Soup mentions above, is a link to a supplemental guide written by Kinfauns that puts all the previous info together to let you root and install roms via commands if you decide to go that route instead of using KFU or a similar utility.
soupmagnet said:
From my experience it has shown more beneficial to learn the command line methods first rather than going straight to a utility like the KFU.
Depending on what you want out of your Kindle Fire experience, it can be troublesome or very easy.
If you want to run a rooted straight stock interface it's slightly more work and you run the risk of Amazon's OTA updates reeking havok on your system, but there are ways around that.
If you want to run a custom rom the process is much easier as all custom roms come pre rooted. And if it's the stock Kindle Fire interface you want, there's a custom rom for that as well.
The biggest thing is installing custom recovery which, as of now, is the only thing you have to do via the command line.
Next would be installing a custom bootloader. The bootloader allows you to use the power button to enter recovery and the most recent version (1.4) allows you to change your bootmode, which will prove very useful in a pinch. Also the new bootloader is flashable via recovery, drastically reducing the possibility of "bricking" your device.
After that, installing and switching between roms is easy with recovery.
There is an immense knowledge base here but it isn't very organized and the search function has a bit to be desired. But if you look around, you'll see most of the same problems are repeated throughout (usually due to lack of experience or user error or both).
The guide posted at this link is a must for any Kindle Fire user so check it out. http://forum.xda-developers.com/showthread.php?p=23747567
Read through the second and third posts as well.
Good luck
Click to expand...
Click to collapse
Thanks for all that info. Much appreciated. I will read that guide thoroughly, and make a decision. I got my replacement Kindle Fire today, and I just found out you can't remove some of their pre loaded apps. Not the end of the world, but that kind of thing right there is why I will most likely root it.....to have control of the device to do with as I please. I'll see how I feel after I read the guide. Like I said, I like the challenge of stuff like this, and simply making the device more personal. I ended up getting a brand new one for $128, so that makes it even more worth the small risk of turning it into a paperweight. I doubt that would happen, but I'm not taking it lightly either.....I know it can happen.
leswgnr said:
And at the end of the third post Soup mentions above, is a link to a supplemental guide written by Kinfauns that puts all the previous info together to let you root and install roms via commands if you decide to go that route instead of using KFU or a similar utility.
Click to expand...
Click to collapse
And thank you as well.
Is there a downside to using the KFU? It seems like it does everything for you pretty much automatically, but maybe that's just how I see it watching that video, and I'm off track, and missing something, or taking it too lightly.
soulweeper51 said:
And thank you as well.
Is there a downside to using the KFU? It seems like it does everything for you pretty much automatically, but maybe that's just how I see it watching that video, and I'm off track, and missing something, or taking it too lightly.
Click to expand...
Click to collapse
There are many variables that can come into play to make the KFU a bad choice for beginners IMO. For a small majority of users, the KFU works flawlessly. But there are some, for a lot of different reasons, for which it has caused unforeseeable problems, without having the necessary knowledge to fix. And for that reason I suggest you research and learn how everything works beforehand so you will have a strong foundation to troubleshoot any problems that may, and likely will arise.
soulweeper51 said:
Is there a downside to using the KFU? It seems like it does everything for you pretty much automatically, but maybe that's just how I see it watching that video, and I'm off track, and missing something, or taking it too lightly.
Click to expand...
Click to collapse
Soupmagnet sums it up well in the prior post. I haven't used KFU but have looked at it to see what it's doing, and seen all the instances where someone needed help after using it. When it works it works great, but if you really want "...to have control of the device to do with as I please ... like the challenge of stuff like this" -- then go for it!! The guides will help you get there.
While it's a lot to learn, it's not as much as it seems and will stand you in good stead for as long as you have the device.
leswgnr said:
Soupmagnet sums it up well in the prior post. I haven't used KFU but have looked at it to see what it's doing, and seen all the instances where someone needed help after using it. When it works it works great, but if you really want "...to have control of the device to do with as I please ... like the challenge of stuff like this" -- then go for it!! The guides will help you get there.
While it's a lot to learn, it's not as much as it seems and will stand you in good stead for as long as you have the device.
Click to expand...
Click to collapse
Yeah, I read through the guide once, and a fair amount went right over my head, lol. But, I'll read it a few times to let it sink in. Like I said, I'm not nearly as smart as a lot of people that post here, when it comes to this kind of thing, but I've attempted a few things like this with success, and I'm fairly brave, as far as taking the risk. It sounds like you really have to not be paying attention to brick this thing.
Hey, there's only one way to learn, right?
soulweeper51 said:
Yeah, I read through the guide once, and a fair amount went right over my head, lol. But, I'll read it a few times to let it sink in. Like I said, I'm not nearly as smart as a lot of people that post here, when it comes to this kind of thing, but I've attempted a few things like this with success, and I'm fairly brave, as far as taking the risk. It sounds like you really have to not be paying attention to brick this thing.
Hey, there's only one way to learn, right?
Click to expand...
Click to collapse
It's very difficult, if not impossible to truly brick this device. The worst thing you can do is kill the bootloader, but even that is not an irrecoverable mistake.
The first post is the most important of the three... you should at least have a good grasp of that one. What part of the guide gave you problems?
kinfauns said:
The first post is the most important of the three... you should at least have a good grasp of that one. What part of the guide gave you problems?
Click to expand...
Click to collapse
Not so much a "problem", as some of it is a little foreign to me.......I guess that's a good way to put it. As much as I want to just use the KFU and cross my fingers, I do want to understand as much of it as I can, so in the event of something going a little south, I hopefully know exactly why.
The Youtube video I watched makes it look so easy, but like I was told, doesn't help with understanding how it all works.
Not to question your capabilities, but what's the rush? You say you've never had a smartphone, so I take it you're unfamiliar with Android devices.
I see so much misinformation floating around about the Fire (you need to root to sideload apps, you need to root to change the stock UI, etc.).
Why don't you fool around with it for a week or two first, get familiar with Android, and see what it's capable of doing, and then root it?
grvthang said:
Not to question your capabilities, but what's the rush? You say you've never had a smartphone, so I take it you're unfamiliar with Android devices.
I see so much misinformation floating around about the Fire (you need to root to sideload apps, you need to root to change the stock UI, etc.).
Why don't you fool around with it for a week or two first, get familiar with Android, and see what it's capable of doing, and then root it?
Click to expand...
Click to collapse
I basically agree with you, as far as not rushing into it. Part of it is my personality......I started looking up what people do to this device as soon as I got it, and it doesn't take long to see how much you can do with it, if you choose.
I hated that carousel right away, so I got Go Launcher Ex, to get rid of that....then I discovered some of the Go wallpapers, and when you set one, it reverts back to the stock one every time it "wakes up" or is powered on, so I found a Youtube video that shows how to set the wallpaper you choose to stay, but it has to be rooted.......and so on and so forth. You get the idea. At the moment I'd be happy just to root it and do that, and then go from there. Like I said, part of it is "I want to do it, just because I can", and it will be more "mine". Maybe that sounds corny, but it's how I feel about it, for the most part. I want to do a few things that I want to do, and then learn more and do more, accordingly, if that makes sense.
That being said, I watched the Youtube video by Nat3mil on using KFU, but from what I can tell, he just goes through downloading the utility, installing the drivers on your computer, and then how to Install Permanent Root with Superuser(option 2)......but what about the other 5 commands?
Like
1 Bootmode menu
3 Install latest TWRP recovery
4 Install latest clockwork recovery
5 Install latest FireFireFire
6 Extras <Requires root>
I guess what I'm asking is....if a person uses KFU, is it best to use all the commands? I guess because the video I watched didn't cover anything other than Install Permanent Root, I'm a little confused.
I hope that made sense, and I'm pretty sure that may seem like a stupid question, but if I don't ask, I won't know.
I'm assuming I can just Install Permanent Root to start with, or like I said, do I go through all the commands?
Go easy on me.
Select install permanent root it should put on fff boot loader and twrp all in one shot clockwork mod recovery isn't needed at that point as for the extras Google market is nice. I say twrp if you want to try any of the new ics roms cwm won't flash them if you do you'll be bricked.
But it might be a little different since I tryed it maybe fff and twrp are seperate installs last time I ran it the first screen I came to after it rebooted was burrito root then it rebooted again I was greeted by the fff bootloader then it booted into twrp where there was a big reboot button so I hit reboot. It then rebooted to the fff bootloader screen then into the kindle os all done rooted new boot loader and recovery
---------- Post added at 12:40 AM ---------- Previous post was at 12:25 AM ----------
This may differ now the best person to ask is vashypooh himself
---------- Post added at 01:02 AM ---------- Previous post was at 12:40 AM ----------
Nat3mil is a great guy and he has done very good videos I just noticed on this last one he didn't show you what's going on on the kindle screen I really wish he would have. If you watch the others 6.21 and 6.22 they vary slightly from that of 6.3.
1. Get adb working
2. Check allow installation from unknown sources
3. Make sure that your USB mass storage drivers are still functioning( in an emergency you will need them)
4 never unplug your device until you are darn sure the process is finished.
Read the dialogue that happens in kfu you can see what is being pushed to your kindle
Ask lots of questions if your in doubt
---------- Post added at 01:25 AM ---------- Previous post was at 01:02 AM ----------
Oh and use the most recent version of kfu it has the very latest bootloader which is different from the original more features are added. To access recovery from this one when you see the blue kindle fire logo give the power button a few pushes small words will come up at the bottom of the screen.
-- normal--
Recovery
Change boot mode
The power button toggles you through these options.
If I had to choose of course root first second run twrp third run fff last Google apps/go launcher.
O.k. thanks!
Now that I've read that guide a couple times, and watched the video a couple times, I'm torn between the two. The idea of just letting KFU do everything, and hoping nothing goes south has an appeal, and the manual method is just more tedious, but you learn more in the process, kind of like when I built my first computer recently......I learned a lot, though it would have been easier to just buy one. Damn.....not sure what to do.
If I'm following all this correctly, if I use the KFU, and there is an OTA update, could I potentially have a problem on my hands that could be a PITA, or would I simply lose the root and have to do it again?
Also, it sounds to me like the custom ROM is the way to go, and actually a littler easier???
Hope my assumptions are at least fairly accurate.
Your correct but you will just lose root from an ota and yes custom rooms will solve this as long as your willing to live with some bugs. CM7 is stable but once you learn about the bugs of CM9 its not all that bad.
Thepooch said:
Your correct but you will just lose root from an ota and yes custom rooms will solve this as long as your willing to live with some bugs. CM7 is stable but once you learn about the bugs of CM9 its not all that bad.
Click to expand...
Click to collapse
Just to clarify......if I wait a bit on the custom roms, and just root it for now, and there is an OTA update, I simply lose the root...no other harm done. Just root it again, and back in business, correct?
Just making sure.
Not quite. OTA updates usually cause a lot of problems to rooted devices and if you don't know how to fix them, you may be looking at a lot of headaches. You can disable them for now but no one knows for sure if Amazon will try to get around it. The more we learn, the more they learn as well. Apple has an entire team whose sole purpose is to try to beat the jailbreakers and I think it's only a matter of time before Amazon follows suit. And at the rate some of these noobs keep sending their devices back with problems caused by modifying, I think that time will be a lot sooner than we think. But that's just my opinion.
soupmagnet said:
Not quite. OTA updates usually cause a lot of problems to rooted devices and if you don't know how to fix them, you may be looking at a lot of headaches. You can disable them for now but no one knows for sure if Amazon will try to get around it. The more we learn, the more they learn as well. Apple has an entire team whose sole purpose is to try to beat the jailbreakers and I think it's only a matter of time before Amazon follows suit. And at the rate some of these noobs keep sending their devices back with problems caused by modifying, I think that time will be a lot sooner than we think. But that's just my opinion.
Click to expand...
Click to collapse
Thank you.
That definitely all makes perfect sense. Like I said, I'd like to change a few things, and rooting it would allow the little changes that would make me content for a bit, but it's either just root it, and disable the updates(with fingers crossed they don't get around it for a bit), or go straight to the custom roms, and updates are no longer in the equation......am I on the right page with that?
Also, If I decide to just root it for now, and disable the updates, and Amazon finds a way around it in the not too distant future, how hard is to just go back to the stock device?
Yeah right page http://forum.xda-developers.com/showthread.php?t=1399072
In an attempt to set a factory reset and have an ICS backup ROM after trying to eliminate small bugs from the JB flash (Jelly Belly w/ the fix), I erased everything by formatting data, system, and cache. The bugs were on my side of things, which is why I was trying to build from scratch.
I made the fatal error of formatting all of the above info before I had pushed Liquid's JB, and when it was time to flash the file, I had nothing.....Now, I have my buddy helping me trying to rebuild this from scratch...
I am an idiot and had no attention span today and had the same feeling that you have when you watch yourself lock your keys in your car (unless you are the dbag that doesn't feel it is "necessary to have a car in London." -Shaun of the Dead)
I joke that I was going to send my phone to Koush and give him a challenge....but he is too busy.
Any suggestions are wanted.
Right now, it appears that I have problems with the drivers. Remember, the only functional part of the phone is the bootloader and recovery mode. Cannot access USB debugging etc. b/c I can't boot the phone past the google unlock screen
Here is what I/we have done:
changed batteries
tried to load the google 4.0.2 image
load JB, ICS roms and anything stock that my friend has backed up
Reinstall the drivers
reinstall the su.zip
cheers
GN Verizon
No Rom
No Kernel
No Radios
No Nothin
Do you have adb? Have you tried to go back to stock following this http://forum.xda-developers.com/showthread.php?t=1529058
Affirmative on the ADB. Working on trying to push through drivers and everything else right now. The problem is that ADB does not see the device
You don't use ADB to flash images. Use the bootloader and fastboot on your computer.
Follow efrants guide on how to flash back to stock. http://forum.xda-developers.com/showthread.php?t=1626895
You should be back up and running.
Thanks for the clarification. Like I said, I had a safety net installed, but realized it was too late to save it before I wiped everything.
On a side not, I agree with your rant about toolkits and how they allow users who do not know what is really going on to play around with their devices, (users like me). I do not think that this is a bad thing though. I guess you have to ask the developers how they feel about the increased numbers of users and the support given through purchasing apps and their ROMS and Kernels. I am trying to learn how to manually build this stuff, but I never have rooted before, and if you had the ability to flash awesome new ROMS and Kernels that allowed for easy customization on your G1, could you honestly say that you wouldn't flash them the easy way while trying to learn the ropes? This is a function of an advancing technology. There will always be the pioneers who taught themselves from day 1 and are a little upset with those of us who come in and make it mainstream and cause a lot of problems and frustration. There is a learning curve, and the noobs/people-who-suck-at-this make it frustrating for those who have been in the game for a long time. But without a mainstream audience, there would not be the development that you are seeing today.
So I thank you for your patience and help. I am in the same spot you were in when you were teaching yourself on the G1, the only difference is that I have many more options and tools to use, so why shouldn't I use them?
hairfarmer said:
Thanks for the clarification. Like I said, I had a safety net installed, but realized it was too late to save it before I wiped everything.
On a side not, I agree with your rant about toolkits and how they allow users who do not know what is really going on to play around with their devices, (users like me). I do not think that this is a bad thing though. I guess you have to ask the developers how they feel about the increased numbers of users and the support given through purchasing apps and their ROMS and Kernels. I am trying to learn how to manually build this stuff, but I never have rooted before, and if you had the ability to flash awesome new ROMS and Kernels that allowed for easy customization on your G1, could you honestly say that you wouldn't flash them the easy way while trying to learn the ropes? This is a function of an advancing technology. There will always be the pioneers who taught themselves from day 1 and are a little upset with those of us who come in and make it mainstream and cause a lot of problems and frustration. There is a learning curve, and the noobs/people-who-suck-at-this make it frustrating for those who have been in the game for a long time. But without a mainstream audience, there would not be the development that you are seeing today.
So I thank you for your patience and help. I am in the same spot you were in when you were teaching yourself on the G1, the only difference is that I have many more options and tools to use, so why shouldn't I use them?
Click to expand...
Click to collapse
Thanks for your comment. I reiterated a few times in that thread that I don't think toolkits are necessarily bad. I was just stating the problems they may cause. They do serve a purpose.
Many people in this forum get stuck and make panic threads giving no information about how they messed up their phone. Which doesn't leave people who are here to help much to work with. The frustration with that led me to make that post.
Your thread asking for help was an informative one and I have no problem trying to help someone like your self. You did it the right way.
Sent from my Galaxy Nexus using xda premium
Hello all. I will be returning to a newish epic soon...hella missed this phone. I've got tons of old files from a couple years ago but I assume there has been lots of goodness put together since my epic got trashed. I've read lots of forums, dowloaded some files, yadaya but If there is still anyone out there using or developing for the epic, can you please give me some direction. Best way to root, from what I assume will be a stock phone. (still odin v3+1.85?) Also and more to the point of my question, Roms? Best roms that actually have valid download links? Thank you for your time if anyone actually reads this
darkrelik696 said:
Hello all. I will be returning to a newish epic soon...hella missed this phone. I've got tons of old files from a couple years ago but I assume there has been lots of goodness put together since my epic got trashed. I've read lots of forums, dowloaded some files, yadaya but If there is still anyone out there using or developing for the epic, can you please give me some direction. Best way to root, from what I assume will be a stock phone. (still odin v3+1.85?) Also and more to the point of my question, Roms? Best roms that actually have valid download links? Thank you for your time if anyone actually reads this
Click to expand...
Click to collapse
I don't know how much advice I can give about what is "best", but I can tell you what I am still using on my "daily driver"...?
I try to keep up with the CM11 "Nightlies", and so right now I'm using the latest: cm-11-20150614-NIGHTLY-epicmtd.zip
The kernel (?) I'm using: notest-epicmtd-kk4-20140401-cma.zip
I make use of Link2SD app as far as juggling space for apps.
Somewhere along the way, the stock Android Messaging app just stopped working correctly for me (couldn't compose a new message - just greyed out - never could figure out what was wrong), so I've "Frozen" the stock Messaging app and installed the (almost identical) SoftCoil Messaging app.
The stock Android browser did not seem to perform very well for me, so I went looking for a "lighter footprint" browser - right now I am trying out the "UC Mini" browser, and so far so good (?) although I still don't rely on using the browser that much, so maybe I haven't done solid testing of it...
I'm not a super-whiz at this, but if there's anything I can answer to help, I'll try. Maybe you'll have some ideas or find out some things that are more up-to-date than what I'm doing...?
Glad to see I'm not the only one posting in this "Ghost Town" these days...
(Although to be honest, I did just get the letter from Sprint about the discontinuation of the WiMax network... so the months are ticking away as for how long I will stick with this, too... soon as I buy a new phone for my lady, I will probably inherit her Nexus 4 and finally say goodbye to the beloved Epic 4G...)
Thank you very much for taking the time to share that info with me. I just got my new Epic about 20 min ago and can't wait to get some CM goodness going. I really didn't expect a reply to this at all so thank you again. I'll post again if I come across something worth sharing.
Oh also give puffin browser a try, I use it on my Tab 2 and its pretty damn fast!
Arson Smith said:
I don't know how much advice I can give about what is "best", but I can tell you what I am still using on my "daily driver"...?
I try to keep up with the CM11 "Nightlies", and so right now I'm using the latest: cm-11-20150614-NIGHTLY-epicmtd.zip
The kernel (?) I'm using: notest-epicmtd-kk4-20140401-cma.zip
I make use of Link2SD app as far as juggling space for apps.
Somewhere along the way, the stock Android Messaging app just stopped working correctly for me (couldn't compose a new message - just greyed out - never could figure out what was wrong), so I've "Frozen" the stock Messaging app and installed the (almost identical) SoftCoil Messaging app.
The stock Android browser did not seem to perform very well for me, so I went looking for a "lighter footprint" browser - right now I am trying out the "UC Mini" browser, and so far so good (?) although I still don't rely on using the browser that much, so maybe I haven't done solid testing of it...
I'm not a super-whiz at this, but if there's anything I can answer to help, I'll try. Maybe you'll have some ideas or find out some things that are more up-to-date than what I'm doing...?
Glad to see I'm not the only one posting in this "Ghost Town" these days...
(Although to be honest, I did just get the letter from Sprint about the discontinuation of the WiMax network... so the months are ticking away as for how long I will stick with this, too... soon as I buy a new phone for my lady, I will probably inherit her Nexus 4 and finally say goodbye to the beloved Epic 4G...)
Click to expand...
Click to collapse
Howdie!
I see you are one of the last people in this forum actively doing things. If I have an old Epic lying around that I want to use as a gaming only system--doesn't need any phone support, which is the most stable rom for that feature? I'm not looking to strip a carrier radio out or anything, just don't care if works or not, I plan to disable everything but wifi.
Suggestions--if you don't mind?
TIA