It looks like there are several Nook Simple Touch images for 1.1. Is this the current version of the firmware? Which one is the most official, if any? It looks like the knowledge base isn't up to date.
1.1.0 is the official firmware which is obtainable via B&N. The other images you are seeing are all different ways to accomplish rooting. You will find that some come with GApps, some don't, etc. Salsicha's repackaging of TouchNooter looks fairly promising:
http://forum.xda-developers.com/showthread.php?t=1351719
OTOH if you want the most "official" release, you can go with Gabrial's original TouchNooter. The problem there is that the newest version (1.11.11) doesn't have GApps/Market and the old version (1.6.24) needs to be modified a bit to work with 1.1.0.
Related
I wanted to root my phone and also have a different skin but there are so many different versions like rc33, rc32, cupcake...etc what are the differences between the versions and which is the best version I should use and also the benifits of reflashing different radio versions.
The RCxx builds are based off of the official released (OTA, or Over The Air) that T-Mobile sent out to G1 owners. The xx numbers are the release version numbers. Rc29 had the 'root bug' that was patched in RC32. That is why the first step in rooting your phone is to go back down to that version, so that you can get root.
If you want to stick to the official releases from there, you just want to go to the highest RC version that's out.
You may also see the 1.1 and the 1.5 version numbers.. these are the versions of the android OS itself. Currently, all of the OTA versions released have been 1.1 - the newest update to android is 1.5, which will start to be released by T-Mobile via OTA this week.
From here it get's tricky. Since HTC makes the phone, Google (sort of) makes android and T-mobile releases it for their phones... there are multiple avenues by which the android OS can be obtained (and I'm sure as more manufacturers come on board, there will be more)
As these different flavors of the new 1.5 version (nicknamed cupcake) have been released in official and non-official ways, different developers have tried to create their own released.. this is how all the different versions have appeared. Karkuro relased different versions based on the HTC code and the Google code respectively. TheDudeOfLive released a couple versions based on the Google code... You'd have to read the individual forum threads on each versions to get the gist of the actual differences.. the first post of the threads will usually list what the major differences are.
Basically, like any open source project, there are several forks of the base code - expect this to get even more interesting/complicated in the near future.
Is there a good breakdown on the differences anywhere?
I already asked on AC, but no luck so far.
Hi all,
I'm sorry if this has been discussed somewhere, but I am very green when it comes to rooting/flashing/manually updating the OS on android devices, specifically the Xoom.
I currently have a 3G Xoom with 3.0.1 which is rooted. I didn't put any custom rom on it. I saw there's a zip file on the other sub-forum with the 3.1 update for 3G Xoom devices, but the instructions assume a certain level of proficiency/familiarity with the process (which appears to be almost vastly different across various android devices).
If someone would be as so kind as to post a relatively detailed step-by-step process of updating a rooted 3.0.1 xoom to 3.1 and re-rooting (without having to lose all the apps and settings installed) I would be MUCH OBLIGED and APPRECIATIVE!
Many thanks to anyone who has the patience and inclination to post something definitive!
--Q
P3Droid seems to have posted exactly what I was looking for: http://forum.xda-developers.com/showthread.php?t=1074502
Reading through these forums has been a real education; much thanks to everyone for posting and sharing!
I was given a reconditioned A500 by a friend (obviously a very good friend!), stock Acer_A500_1.104.02_COM_GEN1 with Android v3.0.1. Rooted with Gingerbreak, everything running fine. Really love the tablet.
Anyway, been looking over all of the choices for upgraded ROMS so graciously provided by members of the community, and hit a little analysis-paralysis. What are the major advantages (other than the "latest-and-greatest" factor) to upgrading to 3.1, 3.2, or 3.2.1? Is there any "must-have" advantage to the upgrade? And will my GEN1 have issues with some of the ROMs developed from GEN2 packages?
Thanks for being patient with an old dog trying desperately to learn some new tricks...
The later the version of Honeycomb generally the more stable and quicker it runs. You probably notice with 3.0 and 3.0.1 there are a lot of force closes on apps. There are other benefits to newer versions, such as ability to plug in USB peripherals etc, but I don't know all of them off the top of my head.
One problem that many people learned (myself included) was that when we got the upgrade to 3.2, those who had root lost it and nobody could figure out how to root it because Acer changed their boot loader. Since then people have found ways around it. Custom ROMs that the devs had created here usually make the tablet run better (of course there are risks to doing this and the occasional bug!). Some people run custom ROMS to overclock, some load them to remove Acer Bloatware and some just have the urge to try new and great things.
In terms of having issues with GEN1 and GEN2 packages, when you are installing custom ROMS made by the DEVs on XDA you won't have to worry. I think the GEN1 and GEN2 are just for ACER to distinguish things like the country that the device is from, or to determine when they should be receiving OTA updates.
CharlieSummers said:
Reading through these forums has been a real education; much thanks to everyone for posting and sharing!
I was given a reconditioned A500 by7 a friend (obviously a very good friend!), stock Acer_A500_1.104.02_COM_GEN1 with Android v3.0.1. Rooted with Gingerbreak, everything running fine. Really love the tablet.
Anyway, been looking over all of the choices for upgraded ROMS so graciously provided by members of the community, and hit a little analysis-paralysis. What are the major advantages (other than the "latest-and-greatest" factor) to upgrading to 3.1, 3.2, or 3.2.1? Is there any "must-have" advantage to the upgrade? And will my GEN1 have issues with some of the ROMs developed from GEN2 packages?
Thanks for being patient with an old dog trying desperately to learn some new tricks...
Click to expand...
Click to collapse
Early HC versions have issues with Netflex, video, voice, GPS, etc. Alot of the drivers have been patched since 3.0.1.
TD
If you want a mostly stock rom with just Root and busybox I suggest this one:
http://forum.xda-developers.com/showthread.php?t=1429199
It is very fast and very smooth. haven't run into any problems or force closes yet.
I found that the full screen feature of 3.2 and 3.2.1 was a great reason to upgrade. My iconia came with 3.1 on it and i was content with that rooted until i learned that my apps that didnt fill the screen (guitar hero 5) and some that just didnt run (dance dance revolution s) worked great in full screen on 3.2+.
Greatly appreciate all of the responses. It's pretty clear I need to read the threads here and learn how to upgrade the Android in this tablet. (I especially appreciate starkiller86's pointer to the 3.2.1 sorta-stock image...that looks like the most sensible direction for me to go.)
Thanks again!
I had recently updated from Rooted .596 to .605 OTA.
Previous History:
Rooted Froyo - Bootstrap, Loader, and superuser.
Then upgraded Froyo ->.573 gb root leak (Kept for 1 year)
sbf Back to froyo 2.340 and then sbf to .340 (.596 build) (2days ago)
Currently: .605 OTA (I still have bootloader 30.04, Not Entirely sure why)
Goal: Gaining .602/.605 root and modding to Vortex Rc1.
I had recently tried the one-click rooting D3 (Psouza4's 1 Click Root) which was said to work for the DX.
When it goes on the first step to restart my phone, my phone goes straight into bootloader. It seems to get stuck there because it says it Waiting for Phone to restart. Which is step 1.
What should i do from now? Should I enter bootloader and sbf back to .602 and then try One-Click Rooting again?
My main goal is to have root and gain clockwork mod recovery and then intall Vortex rc1 for .602/.605. Unless someone recommends anything beter.
Also I have no idea whether my phone is considered deodexed or odexed.
I am new and can upload pictures if needed.
System Version:
4.5.605.MB810.Verizon.en.US
Phone Model:
DROIDX
Android Version:
2.3.3
Baseband version:
BP_C_01.09.13P
Kernel version:
2.6.32.9-g34b306d
[email protected]#1
Build number:
4.5.1_57_DX5-35
First, try running a factory reset in recovery, and if that doesn't work, SBF that thing.
rootzwiki . com/topic/5307-guide-root-or-unroot-your-droid-x/
(remove the spaces, it won't let me post external links until I have "approximately eight posts")
In summary, look up "Pete's Motorola Root Tool" (I believe it's the one I used, long ago). There's instructions for other operating systems in there too if you're on a different OS.
wiki . rootzwiki . com/Motorola_Droid_X is another decent source of data. After you root, I assume you're aware of how to install CWM, and from there you're set! I would suggest making a nandroid backup before flashing any new ROMs.
While I love and respect XDA forums for their awesome content for android, they are very greatly lacking in DX support, I would peek around rootzwiki a little, as that is where most of the DX developers post their stuff (as far as I can tell).
As for your phone being deodexed/odexed, if you don't know, then it's odexed. That, of course, will be fixed with any ROM you install, though you can simply install a stock deodexed rom if you want. Being odexed is hardly an issue though, it's a very small performance drag, nothing compared to the general bloat of stock DX apps.
As for what you should install, Vortex is a pretty solid stepping stone, very popular, and ridiculously stable with great battery life. I would suggest testing the waters with Liberty/CM7/MIUI/CM9/AKOP/Rubix(when it comes out)/anything else you can find. Liberty/Rubix/Vortex are all very similar, with subtle, mostly thematic differences, you should definitely go through them. CM/MIUI/AKOP are all 2nd-init (I believe, but that's a story for another time anyways) and come with tons of random/awesome features, but sometimes at the cost of others (camera quality [if it was even an option] was the biggest "flaw" in my opinion). I hope this is helpful and isn't too rambly.
Best of luck in your endeavors, and don't forget nandroid backups, and keeping SBF handy just in case. Let me know if you encounter any other errors.
I was having some issues with my browser and email client and suspected it was due to not running a stock rom. Initially when ICS came out I was a little impatient, didn't wait for the OTA update and installed one of the "released" images.
Yesterday i spent most of the day trying different image. Initially I hoped to install an older version, like honey comb and the to OTA back to a stock ICS rom.
It seems that once your bootloader has been converted to ICS there is now way of going back to Honeycomb. I tried some things suggested on xda developer forum, but none produced the results.
I then installed what I believe is the current stock rom for an A500 giving me the following:
Android version: 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer_AV041_A500_RV03RC01_WW_GEN1
Build number: Acer_AV041_A500_1.0.31.00_WW_GEN1
What I would like to confirm is that this is correct and that this version is the latest available from Acer.
I am not really interested in any of the custom images and don't need it rooted. So a stock standard Acer ROM should do me just fine.
lostinspace2011 said:
I was having some issues with my browser and email client and suspected it was due to not running a stock rom. Initially when ICS came out I was a little impatient, didn't wait for the OTA update and installed one of the "released" images.
Yesterday i spent most of the day trying different image. Initially I hoped to install an older version, like honey comb and the to OTA back to a stock ICS rom.
It seems that once your bootloader has been converted to ICS there is now way of going back to Honeycomb. I tried some things suggested on xda developer forum, but none produced the results.
I then installed what I believe is the current stock rom for an A500 giving me the following:
Android version: 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer_AV041_A500_RV03RC01_WW_GEN1
Build number: Acer_AV041_A500_1.0.31.00_WW_GEN1
What I would like to confirm is that this is correct and that this version is the latest available from Acer.
I am not really interested in any of the custom images and don't need it rooted. So a stock standard Acer ROM should do me just fine.
Click to expand...
Click to collapse
Look in the dev section , the latest is 1.054.00_ww_gen1. It is in the sticky thread.
This thread describes in detail what I did http://forum.xda-developers.com/showthread.php?t=1961301 but now my tablet is bricked. I am still hoping for some way of recovering it though.
lostinspace2011 said:
This thread describes in detail what I did http://forum.xda-developers.com/showthread.php?t=1961301 but now my tablet is bricked. I am still hoping for some way of recovering it though.
Click to expand...
Click to collapse
This is what happens when you have multiple threads going. Nobody knows what the heck is going on.
Perhaps you think it increases your odds of getting your issue fixed, but now, it only compounds things.
If one of the issues is solved, then you need to edit your title thread to state so. This can be done by selecting Edit, Go Advanced.
MD
The reason I started two threads was to answer different question. In this thread I was looking for the latest official released version of ICS available. The other thread describes my journey of trying different ROMs. I was hoping to downgrade to 3.1/3.2 and then to OTA to ICS. Well that is covered in the other thread.
Thanks for all your help. I got my answer on the latest version.