So the point of this thread is to make sure i understand what I am doing before I do it. I have decided to update the cm7 on my phone. I was going to use the cm9 since it is the next stable release. But the people who talk about the Jellybean releases are super happy about them so i decided to skip ics. I looked into a thread for cm10 nightly releases vs hellybean. It was there i heard of Lanight. After reading more about it, it sounds like the version to go for right now. So my final problem became nodatadata vs datadata. I have a vague understanding of what the difference is from trying to search it up...but i did not come across a clear explanation. One way i can bypass the question is by asking "Was CM7 DATADATA or NoDATATA, and if they were both available, how do i figure it out."[/B.
This thread is to make sure that I have fully understood what i read and that i am not creating problems for myself later. I do appologize if this question has been answered a million times. Just one more time for me please.
CM always had datadata until, CM10, but they put it back in CM10.
Sent from a jelly bean
dustingvitamins said:
So the point of this thread is to make sure i understand what I am doing before I do it. I have decided to update the cm7 on my phone. I was going to use the cm9 since it is the next stable release. But the people who talk about the Jellybean releases are super happy about them so i decided to skip ics. I looked into a thread for cm10 nightly releases vs hellybean. It was there i heard of Lanight. After reading more about it, it sounds like the version to go for right now. So my final problem became nodatadata vs datadata. I have a vague understanding of what the difference is from trying to search it up...but i did not come across a clear explanation. One way i can bypass the question is by asking "Was CM7 DATADATA or NoDATATA, and if they were both available, how do i figure it out."[/B.
This thread is to make sure that I have fully understood what i read and that i am not creating problems for myself later. I do appologize if this question has been answered a million times. Just one more time for me please.
Click to expand...
Click to collapse
I don't know much about Lanight but I do know that the dev created the two versions because some people were having wifi issues on one version and wasn't on the other. That being said I've run different roms, some of which are datadata and some that aren't, and haven't had issues. As far as causing trouble for you down the road the only thing I've ran into is the inability to restore your nandroid backup when going from datadata to nodatadata and vice versa. Occasionally I've ran into status 7 errors going between the different layouts but flashing the kernel by it's self for the rom you're going to prior to flashing the rom package generally solves that issue.
Related
Since everything I need to know is scattered across various threads and there is no specific information regarding my question AFAIK so I decided to post a new thread. Forgive a newb for being worried.
I've decided to root my N1 and am running the EPF24B European build. I just had some questions and concerns:
1. What ROM do you think is best? I think the majority of people like Cyanogen.
2. If I root my phone now and flash on Cyanogen, when Cyanogen releases a Froyo ROM how will I update? Does that happen through a dedicated app? OTA?
3. How do I keep all my current programs and settings? I've heard of Nandroid but have no idea what it does. I presume it has something to do with the NAND memory?
4. btw how stable is a rooted phone?
5. I've seen a number of guides here, but don't know whether or not they are the latest versions. Can anyone point me to a proper guide? Or are they all the same?
Thanks if anyone can answer this.
-------------------------------------
Sent from my Nexus One
hackm0d said:
Since everything I need to know is scattered across various threads and there is no specific information regarding my question AFAIK so I decided to post a new thread. Forgive a newb for being worried.
I've decided to root my N1 and am running the EPF24B European build. I just had some questions and concerns:
1. What ROM do you think is best? I think the majority of people like Cyanogen.
2. If I root my phone now and flash on Cyanogen, when Cyanogen releases a Froyo ROM how will I update? Does that happen through a dedicated app? OTA?
3. How do I keep all my current programs and settings? I've heard of Nandroid but have no idea what it does. I presume it has something to do with the NAND memory?
4. btw how stable is a rooted phone?
5. I've seen a number of guides here, but don't know whether or not they are the latest versions. Can anyone point me to a proper guide? Or are they all the same?
Thanks if anyone can answer this.
Click to expand...
Click to collapse
you might get flamed for this or get this thread closed but i will try to help u.
1)while cyanogen is the best rom in my opinion, froyo is the ****. no matter what. and when cyanogen finally puts his touches on it, it will be even better.
3)no you cant keep them. u would have to be ROOTED first and then you can use titanium backup to make a backup or all your settings and freeze apps. til then, nope u have to completely wipe and start over again. i know when i switch from rom to rom, google automatically downloads the apps that i have had installed before i switch roms if that helps you any.
4)rooted phones are VERY stable and even faster than stock. more memory, runs smoother. the only one that might not run as smooth is the Desire Rom because of sense ui but i love sense ui and have it on my G1 but yes rooted phones are stable.
5)i have followed the instructions of this guide that was for macs tho. u have to be a bit specific if your on mac or pc
I'm using a PC.
And thanks for your input.
btw you didn't answer question 2. If I update to CM now, will I be able to update OTA when a Froyo version comes out?
I have a major headache here. I flashed the latest dalingrin OC kernel (5/13) and it would hang on startup. So I tried to use a nookie froyo image on a sd card and get back into ROM Manager and use CWR and try to reinstall everything. Well now its stuck in boot loop on the touch the future screen. I'm reading everything I can but I'm so confused. How can I get into CWR again so I can re-flash everything? I am trying to do the bootable CWR sd card thing but I can't get it to work and I'm really getting frustrated at this whole "img" thing, I can never get it to work. Anysuggestions. and yes I'm still reading...
http://forum.xda-developers.com/showthread.php?t=1030227 if you haven't yet.
I'm almost in the same boat. I was running stable 7 and decided I wanted Dal's new kernel and figured I'd at least upgrade to 7.03 stable. I was in the reboot loop and now I can't get it to display anything past the "touch the future" screen.
I've formatted the system, data, cache, and installed from scratch with cm7 stable (and tried a nightly too), along with gapps and Dal's latest kernel.
Might just have to leave out the kernel this time and see if it works.
Update- I got mine working with leaving Dal's kernel out. I might just flash the 4/24 now instead or just wait til he puts out something a little more solid than the 5/13.
Dal, if you're reading this, not knocking on you. Thanks for all the work you put in. I have loved having the 1100 kernel.
cincibluer6 said:
http://forum.xda-developers.com/showthread.php?t=1030227 if you haven't yet.
I'm almost in the same boat. I was running stable 7 and decided I wanted Dal's new kernel and figured I'd at least upgrade to 7.03 stable. I was in the reboot loop and now I can't get it to display anything past the "touch the future" screen.
I've formatted the system, data, cache, and installed from scratch with cm7 stable (and tried a nightly too), along with gapps and Dal's latest kernel.
Might just have to leave out the kernel this time and see if it works.
Click to expand...
Click to collapse
Ok I just followed the instructions in that thread and it worked perfectly! WHEW! (I stuck with the 4/24 kernel) I think I will keep a spare card made up for this just in case!
KDOG2020 said:
Ok I just followed the instructions in that thread and it worked perfectly! WHEW! (I stuck with the 4/24 kernel) I think I will keep a spare card made up for this just in case!
Click to expand...
Click to collapse
The 5/13 kernel is NOT for current stable or nightly builds. It's for exclusive use in the Beta 3 CM7 rom at the moment and requires the use of the 1.2 u-loader (read forever).
sent from my Ginger-Hero CDMA
hockeyfamily737 said:
The 5/13 kernel is NOT for current stable or nightly builds. It's for exclusive use in the Beta 3 CM7 rom at the moment and requires the use of the 1.2 u-loader (read forever).
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Good to know. I was seeing all this stuff about beta but had no idea what it was or where it might be.
Sticking with 4/24 for now too until the 5/13 is just a hair more stable.
Lol, prime example why YOU SHOULD READ before doing. I thought this was a joke thread at first.
Hopefully people can learn from this...seems to be the only way nowadays...
Seems like and I.D. 10 T error to me
cincibluer6 said:
Good to know. I was seeing all this stuff about beta but had no idea what it was or where it might be.
Sticking with 4/24 for now too until the 5/13 is just a hair more stable.
Click to expand...
Click to collapse
You still don't understand. 5/13 is rock frickin' solid if you flash it with the correct BETA ROM.
If you flash the 7.1.0 Beta3 found in the CM7 developers thread with the 5/13 kernel you get CM7 as it should be.
sassafras
sassafras_ said:
You still don't understand. 5/13 is rock frickin' solid if you flash it with the correct BETA ROM.
If you flash the 7.1.0 Beta3 found in the CM7 developers thread with the 5/13 kernel you get CM7 as it should be.
sassafras
Click to expand...
Click to collapse
except for the renewed sleep of death issues and the spontaneous reboots and the occasional lockups, that have been repeatedly reported, it is a fairly solid beta test build. But it is a development beta test build after all, and very cool one at that. If people choose not to test it that's cool too.
sassafras_ said:
You still don't understand. 5/13 is rock frickin' solid if you flash it with the correct BETA ROM.
If you flash the 7.1.0 Beta3 found in the CM7 developers thread with the 5/13 kernel you get CM7 as it should be.
sassafras
Click to expand...
Click to collapse
Sorry, I meant to say until the beta is stable. As 12paq has stated, it's not stable enough for me to give it a whirl. I know that it is a lot better though when it's working.
For me, I'll sit this one out for now. Maybe I'll get bored next weekend tho and mess with it.
I still don't get the uloader thing will that need to be changed BEFORE flashing the .32 builds or will flashing those builds take care of that automatically?
KDOG2020 said:
I still don't get the uloader thing will that need to be changed BEFORE flashing the .32 builds or will flashing those builds take care of that automatically?
Click to expand...
Click to collapse
I'm also curious. I ended up in the boot loop after trying to use Kernel Manager after updating to 7.0.3 using ROM Manager.
Came here to see what was wrong. Kernel Manager said it was flashing the 4/x version but I guess it was flashing 5/x. I just downloaded and manually flashed the 4/x kernel linked about and now it's working again.
What will I need to do when this CM7 build is final?
I believe, you can use the 1.2 bootloader file for stable, nightly or beta. But for beta which uses the new .32 Kernel, the newer 1.2 bootloader is needed. The new kernel was written from the .32 source and needs the new bootloader to play nice. Only OC test kernels run with the beta test builds.
It has been implied that after the beta is thoroughly tested by us guinea pigs, the devs will incorporate the new kernel and its really cool improvements into the normal builds.
The beta with the new kernel is smoother and faster, WiFi drivers are better and it reaches deep sleep, so battery life is better. But it's still a test beta so it's not perfect yet, for some.
All above is my interpretation, correct me as/if needed..
ace7196 said:
Lol, prime example why YOU SHOULD READ before doing. I thought this was a joke thread at first.
Hopefully people can learn from this...seems to be the only way nowadays...
Seems like and I.D. 10 T error to me
Click to expand...
Click to collapse
It is possible to read and get incomplete information from the threads. I read that line about the kernel not being for use with the stable mod but it also says you're OK if your NC boots with "Read Forever". Well mine boots this way so I thought I was good to use the 2.6.32 kernel.
So instead of trying to belittle people, how about being a little more helpful? Not all of us are IT people.
yeah things actually got more complicated recently, in addition some of the older test kernels needed script edits too..
Ace even started a thread in the dev section to help out with the clarifications. He's just the excited one in the group... probably didn't mean to belittle ya..
darien87 said:
It is possible to read and get incomplete information from the threads. I read that line about the kernel not being for use with the stable mod but it also says you're OK if your NC boots with "Read Forever". Well mine boots this way so I thought I was good to use the 2.6.32 kernel.
So instead of trying to belittle people, how about being a little more helpful? Not all of us are IT people.
Click to expand...
Click to collapse
Many of us are not IT people (I for one am a machinist....I make $hit out of metal). Recently developement has started going in many different directions at once and if you're going to play around on the "dark side" of the Nook it's important to read as much and as often as you can. No one means to belittle anyone, but please understand we have answered these questions multiple times in multiple threads. So as you get frustrated with your problems, we to get frustrated answering the same questions over and over again. It's a vicious cycle. Enjoy your Nook and stay on top of these threads for the most recent information about your device!
hockeyfamily737 said:
Many of us are not IT people (I for one am a machinist....I make $hit out of metal). Recently developement has started going in many different directions at once and if you're going to play around on the "dark side" of the Nook it's important to read as much and as often as you can. No one means to belittle anyone, but please understand we have answered these questions multiple times in multiple threads. So as you get frustrated with your problems, we to get frustrated answering the same questions over and over again. It's a vicious cycle. Enjoy your Nook and stay on top of these threads for the most recent information about your device!
Click to expand...
Click to collapse
No problem dude. Believe me I get where you're coming from. I'm a big home theater guy and hang out at Audioholics. I admit I get bugged when noobs come in asking the same questions about what speakers should I get? Is this amp any good? blah, blah, blah. I just tend to ignore those guys though.
I know I an nowhere near qualified to be rooting my Nook. That's why I paid a local guy to do it for me for $25. I think it was a bargain as I now have a kick-ass tablet PC for $275. Many thanks to CM and XDA!!!
But I just had one issue, the sleep thing and installing the new kernel seemed like an easy proposition. Turned out that it was quite as simple as I thought. I have since gotten the 5-15-11 kernel installed but my battery still seems to be wearing down at the same speed. Not sure if the sleep fix isn't part of this kernel.
12paq said:
yeah things actually got more complicated recently, in addition some of the older test kernels needed script edits too..
Ace even started a thread in the dev section to help out with the clarifications. He's just the excited one in the group... probably didn't mean to belittle ya..
Click to expand...
Click to collapse
It was actually the OP that Ace was flaming. But I wasn't taking it personal, just trying to tell the guy to chill out and help us noobs, as frustrating as we can be.
Hey, everyone, I'm sure this has been covered somewhere, but a search regarding the EU bug on Jellybean only pulls one irrelevant thread...
Have there been any reports of the EU bug popping up on Cappys with Jellybean ROMs installed? I know ICS is the main offender, but I haven't really read anything about it rearing its ugly head on JB.
I'm running GB KK4 2.3.5, and would like to make the upgrade, but the thought of getting that bug scares the life out of me. Thanks in advance!
Would love to know the answer to this too.. i think im gonna copy your thread in the vibrant forums.
Sent from my SGH-T959 using xda app-developers app
By all means! Let me know if you get an answer to this. I can't believe after over 140 views, no one can answer this!
Yomaster91 said:
Hey, everyone, I'm sure this has been covered somewhere, but a search regarding the EU bug on Jellybean only pulls one irrelevant thread...
Have there been any reports of the EU bug popping up on Cappys with Jellybean ROMs installed? I know ICS is the main offender, but I haven't really read anything about it rearing its ugly head on JB.
I'm running GB KK4 2.3.5, and would like to make the upgrade, but the thought of getting that bug scares the life out of me. Thanks in advance!
Click to expand...
Click to collapse
On the Paranoid Android forum I've seen a reply suggesting that the /data partition is unavailable, but I'm not sure if that occurred during an ICS rom or during the switch to jb. So far that's been the only mention of it that I've seen on a jelly bean thread, so it must not be a prevalent issue so far in these early builds.
Yomaster91 said:
Hey, everyone, I'm sure this has been covered somewhere, but a search regarding the EU bug on Jellybean only pulls one irrelevant thread...
Have there been any reports of the EU bug popping up on Cappys with Jellybean ROMs installed? I know ICS is the main offender, but I haven't really read anything about it rearing its ugly head on JB.
I'm running GB KK4 2.3.5, and would like to make the upgrade, but the thought of getting that bug scares the life out of me. Thanks in advance!
Click to expand...
Click to collapse
I've been like you following this bug for a very long time, its the only reason I've not upgraded to ICS, though I did try it briefly. I went ahead a bit the bullet and upgraded to Helly Bean from Legend 5 and so far have had no problems nor have I heard of anyone getting the EU bug. If you haven't seen this thread:
http://forum.xda-developers.com/showthread.php?t=1447303
Its the main one that talks about it and I've seen a few people asking on there if JB has seen this bug...so far nothing.
I haven't replied because it's not that straightforward. I have had the "EU" error a few times on jb but have always been able to recover by flashing back to gb stock.
From what I've read this error may cover a variety of conditions, not all fatal.
In any event, I am currently running pics and will upgrade to jb again soon.
mschandler76 said:
I've been like you following this bug for a very long time, its the only reason I've not upgraded to ICS, though I did try it briefly. I went ahead a bit the bullet and upgraded to Helly Bean from Legend 5 and so far have had no problems nor have I heard of anyone getting the EU bug. If you haven't seen this thread:
http://forum.xda-developers.com/showthread.php?t=1447303
Its the main one that talks about it and I've seen a few people asking on there if JB has seen this bug...so far nothing.
Click to expand...
Click to collapse
Good to know. I'm running Legend 5 as well. How does Helly Bean compare to it? I've been on Legend ROMs for a while now...
Excellent info, everyone! Looks like I'll be flashing JB in the near future. Thanks to all of you!
Yomaster91 said:
Good to know. I'm running Legend 5 as well. How does Helly Bean compare to it? I've been on Legend ROMs for a while now...
Excellent info, everyone! Looks like I'll be flashing JB in the near future. Thanks to all of you!
Click to expand...
Click to collapse
Hard to answer that, they don't compare at all really. Legend ran the best on my phone for a GB rom but would give me quite a bit of lag especially trying to play games like Angry Birds, so I tried different GB roms to see if I had the same problems and I did...and worse. So I always stuck with Legend. With HellyBean everything runs flawlessly so far and I haven't noticed any lags or problems. If you decide to go that route this is what I did. Odin one click to stock> Odin latest corn kernel> flash cm9 stable> flash HellyBean. Doing this per each roms individual instructions has given me no problems.
Hi, I'm practically new to this, last week was the first time I flashed a custom rom on my phone, CM 10.1.3 RC2, and now I'm just curious about Kernel, first of all I'm not realy sure what is it, should I change it or something to make my phone run smoother? Can you recommend me one then?
I know those questions may have been stupid for you guys but thanks anyway
You should probably read an FAQ for Android to understand what a Kernel is and what it does.
For now just stay with the standard CM kernel and read about what you can do with your new custom ROM.
And do nandroid backups (if you don't know what that means, search and read).
I know that those kind of answers are not likely those you want to get, but you will learn so much more if you read everything you can find.
I rarely post any questions here because I read everything and try to sort things out for myself
Sent from my 4x HD
I see alot of Tocuhpad Dev threads and I just pulled my TP out of storage.
Its running Cyanogen Mod 4.0.4 (System settings says Cyanogen Mod Version 9-20120930 Nightly tenderloin)
Build date Sun Sept 30th 2012
I have CWM-based Recovery v5.0.2.6
moboot 0.3.5
As you can see its very outdated.
What should I be running now if I am looking for daily reliability with most features working? Thanks for your input (If there is a newer guide I can follow to update from my current version to a new one please post it, thank you)
I would suggest that you read this http://forum.xda-developers.com/showthread.php?t=2147284.
It is an excellent guide with video tutorials if necessary. Roland has also posted an additional guide of the newer more experimental Roms also in Touchpad Development forum.
Hopefully they will help you make a decision based on what you need to use your tablet for ie Bluetooth/gaming etc.
Have fun there have been lots of improvements since you last used it.
sstar said:
I would suggest that you read this http://forum.xda-developers.com/showthread.php?t=2147284.
It is an excellent guide with video tutorials if necessary. Roland has also posted an additional guide of the newer more experimental Roms also in Touchpad Development forum.
Hopefully they will help you make a decision based on what you need to use your tablet for ie Bluetooth/gaming etc.
Have fun there have been lots of improvements since you last used it.
Click to expand...
Click to collapse
Where do you even start on that thread, there is about 100 links and 15 videos posted?
gt5oh said:
Where do you even start on that thread, there is about 100 links and 15 videos posted?
Click to expand...
Click to collapse
Just read the first page, then try a couple of different ROMs at the very least you can see all the different variations available and the requirements needed to install them(Partition size.
If you then have a specific question having tried the above it will probably be a lot easier to help you.
Personally, I would go with milaq's last Jelly Bean 4.2.2 rom cm10.1
The next step is 4.3 - read need for resizing of /system, and/or /data partitions - or 4.4 (Kitkat), which is still very much experimental/developmental.
Milaq's 10.1 Jelly Bean roms are very stable and good for daily use.
Just my opinion!
Peace
Thanks, I actually went the opposite way and did the test version of 4.4 to see how it is
It appears you are already partitioned to run the newest ROMs, but if you or others want to try at least a 10.1 ROM (Android 4.2.2) without having to increase partition size, OaT's Light n Tasty (LnT) is very stable and except for the lack of bluetooth plaguing a number of the post-CM9 ROMs the ROM is very solid. He somehow lightens the ROM and the GAPPs so it runs in the pre-CM10 partitions. I am leery of going all the way back to webOS, removing Android, doctoring and changing partitions, and then starting over. At some point I am sure I will, especially if a really solid KitKat ROM is released with bluetooth.
Many people have stayed on CM9 btw, as they find CM9 the most dependable.
Here's a link to the XDA discussion on OaT LnT. Note his OP has an older version of his ROM... if you scroll towards the end he includes a link to an October 8 version he has been using recently. Make sure to also use the GAPPs he includes in the OP, since it is lightened as well. He leaves off a few things... like calendar and browser, since so many people can and do use ones downloaded from Play Store (is. I use aCalendar and Next browser).
http://forum.xda-developers.com/showthread.php?t=2332510
CM 10.1 (JB 4.2.2) doesn't require repatitioning, its the newer 10.2/4.3 and Kitkat 4.4 that require/advise a larger /system partition.
I actually went back to ICS from 10.1 thinking it had been better, but tbh the experience wasn't what I remembered and I very quickly went back to 10.1 (via Kitkat, briefly, but too buggy for me atm). Battery life, responsiveness and stability were all better, for me, with 10.1 (spceifically milaq's roms).
Having said that, its worth giving yourself a bigger /system partition - 5 or 600mb - and trying out the latest kitkat builds, there's lots of promise there!
I will definitely be going back once certain bugs and issues are ironed out...
Peace