Database Develop

Samsung site link affects S7

Here's a odd one!
I was using my S7 to research an issue with my Samsung LED Smart TV. I found a How To, noticed a file path at the top of the page and backed up one page. It had several links, one of which was "How to Power Cycle a Customers Network". That sounded interesting so I clicked on it.
As soon as I clicked on the link my S7 turned OFF. I turned it back ON and it was stuck on the Dell logo. I pinned holed and tried again. It stuck again.
I booted into the recovery menu and tried to boot from there but it again got stuck. I had to do a factory reset. I use My BackUp Pro with a external SD card, it wasn't that painful and other than my email to setup, I'm back up.
Anyone see anything like this before?
Here a link to the nasty page for the brave to try: http://support-us.samsung.com/cyber/popup/iframe/pop_troubleshooting_fr.jsp?idx=151038&modelname=&modelcode=&session_id=P7mLwJcB60VpLrLWp3vgvhhXtfh2XSS3p78q2QlvhT3McsST29T1%21-1964052360%211228160092%211329276619709

Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install

cdzo72 said:
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
Click to expand...
Click to collapse
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.

wptski said:
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
Click to expand...
Click to collapse
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.

cdzo72 said:
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
Click to expand...
Click to collapse
I'm sure that a reset must wipe everything out, true? A reset barely a month ago. Your saying that monthly maintenance is needed?
I don't reinstall Windows monthly as that's a last resort at any time.

NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.

cdzo72 said:
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
Click to expand...
Click to collapse
Both for rooted devices and no good for me.

wptski said:
Both for rooted devices and no good for me.
Click to expand...
Click to collapse
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please

cdzo72 said:
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
Click to expand...
Click to collapse
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??

wptski said:
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
Click to expand...
Click to collapse
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes

cdzo72 said:
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
Click to expand...
Click to collapse
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.

wptski said:
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
Click to expand...
Click to collapse
Then you definitely had/have a corrupt package and the renaming is a sign of a read only problem trying to surface sounds like to me

cmod7 kindle app - no menu bar when reading

Don't know it this is a setting somewhere or what, but I have a question on using the Kindle app on the Nook Color running cmod 7 (7.20 stable). The app runs okay, but I seem to be missing a navigation bar once I start reading a book. It only shows the title and where I am - no options to go back to the Kindle menu (like if I want to read a different book). The only way I can get back to the Kindle menu is to reboot.
I've searched the forum and the closest thread to this problem talks about changing the settings - I don't seem to have any settings to adjust. Even if I go to settings/applications/manage applications/downloaded/kindle there still aren't any changable options.
Sorry for so many questions - I'm a noob. I've searched the net on this and searched this forum with no luck.
any help is greatly appreciated!
Thanks in advance!
Dave

dweaton said:
Don't know it this is a setting somewhere or what, but I have a question on using the Kindle app on the Nook Color running cmod 7 (7.20 stable). The app runs okay, but I seem to be missing a navigation bar once I start reading a book. It only shows the title and where I am - no options to go back to the Kindle menu (like if I want to read a different book). The only way I can get back to the Kindle menu is to reboot.
I've searched the forum and the closest thread to this problem talks about changing the settings - I don't seem to have any settings to adjust. Even if I go to settings/applications/manage applications/downloaded/kindle there still aren't any changable options.
Sorry for so many questions - I'm a noob. I've searched the net on this and searched this forum with no luck.
any help is greatly appreciated!
Thanks in advance!
Dave
Click to expand...
Click to collapse
On my device I only have to tap the middle of the page and the menus all pop up.
Sent from my Nook Color running ParanoidAndroid and Tapatalk

Still no go......
Tried that - I still only get the title at the top and the how much I've read meter at the bottom - no menu.
Thanks for replying!
Dave

dweaton said:
Tried that - I still only get the title at the top and the how much I've read meter at the bottom - no menu.
Thanks for replying!
Dave
Click to expand...
Click to collapse
What version of the Kindle app are you using? Try updating to the latest version.
Also try playing with the settings in cm. Go to settings, cyanogenmod settings, tablet tweaks, and play with checking and unchecking disable full screen.
Sent from my NookColor using Tapatalk

uh.....I'm not sure
Thanks for the reply! I downloaded the Kindle app via Amazon, so hopefully it is whatever is their latest. I sure didn't know about the settings, so I'll give the go and see what happens! I do get the drop down from the top stating the title, and the pull-up from the bottom, but the bottom only has how much I've read so far.
Thanks again!
Dave
EDIT: Well, I don't have the tablet options. Everything in there is for a phone! Seems kind of weird on a device that doesn't have a phone.

lost cm settings
I tried the cyanogenmod settings, and while everything there was for a phone, I turned off things like vibrate, etc. - pretty much everything dealing with a phone. Now when I try to go back to cyanogenmod settings, the app aborts.
I also look in the dev settings and see a config file in there that set s default resolutions, etc., and includes an option that looks like it hides the menu bar, so I used terminal (I am familiar with Linux) and checked for such a file for the system but wasn't able to locate one. I'm wondering if there's a setting like that somewhere, as I don't get any back arrows, menu, etc., just on the pages, and was wondering if that was also stopping me from getting the full menu bar in the Kindle app?

So you do NOT see the word Kindle in orange Aa, magnifying glass and three vertical dots and a bookmark icon as well as the blue dot and position in book at the bottom of screen when you touch anywhere that is NOT the far left and far right of the screen?
And you do NOT see the back, home, recent apps and "menu" button in the bar at the bottom of the screen outside of the kindle window?
Dev settings? no such beast in CM7 or CM9
There is a Developer options which has nothing to do with any sort of resolutions..
I suggest you reinstall CM7.2 release from the official site, stay out of ADB, and stay away from all the various "work in progress" roms until you can actually navigate the default device...
I think you probably got a bit happy and broke something .. there is a setting in CM7 settings to disable fullscreen apps from hiding the "menubar" at the far bottom of the screen and that should be under tablet tweaks in the system settings app.

Yep, none of those
Yep - none of those. This was just after getting 7.0 stable installed and loading in the gapps, since the gapps file was dated just slightly after that release. Immediately went and got Kindle and Nook reader apps. Tried them to be sure they looked like they were working and then applied the zip of 7.2 stable. I didn't try the cyanogenmod settings until later when it was posted in this thread. Again, there are no options in there for a tablet - only a phone. I don't mind going back and doing everything over, just as long as I don't end up in that deadly embrace of things aborting and google market not working. I'll let you know what happens.
If I flush out the Kindle cache I can get back to seeing my titles, but that really defeats the purpose of reading on the device.

Something is not right
Okay, I downloaded everything again and made the microSD. I booted the microSD, did the format data/system reset, went to mounts and did the format /system, while there I tried the format /data - it fails. I had noticed before that when the data/system reset is run and completes, I can no longer do anything - I have to manually power off, wait a while, and power back on. Did all that, went to advance and cleared the kelvich or whatever it's call cash. Installed the cmod7.20 stable. Took out the microSD and rebooted. All of my old apps, etc., are still there. I also was looking at settings and see that the settings I changed were under "phone", not using the cyanomod settings app - it still just aborts.
So, what have I got to do to completely clean all this stuff off and then try installing again? As you can imagine, the number of attempts, partial successes, successes (at least I thought it was only the Kindle app that wasn't showing the menu), etc., we're talking all kinds of hours starting Monday night - probably at least 10 hours each day. Now I'm no further than when I started. For now I'm going to load the old 1.4.1 image again for the umpteenth time and hope someone can tell me how to clear this all up, or else recommend a different android that will run on the Nook Color without problems.
I still think if I can clear EVERYTHING (well, not /boot, obviously) so I'm starting with a CLEAN slate again it may help. I just don't have a clue how to do that using cwm recovery.

Still no good
I redownloaded everything again, created the microsd and tried to install 1.4.1 just to get back to a clean starting point. Can't get beyond where it asks for B&N userid/password as the keyboard shows for about 1/2 a second, no matter what I do. So, I tried the format data/system reset again and just loaded in the cmod 7.20 stable. Again, after booting, everything is still there - the google apps and all. How do I get rid of all this stuff so I can try an install from a clean slate? Right now I've been going thru all the data folders I can find and manually removing everything there. I would like to delete a lot of apps, but I never seem to be able to "uninstall".
So, before I start over again, can someone tell me how to clear EVERYTHING (except /boot, /emmc [unless I need to],/sd*) so I have a clean system first?
Thanks!
Dave

dweaton said:
I redownloaded everything again, created the microsd and tried to install 1.4.1 just to get back to a clean starting point. Can't get beyond where it asks for B&N userid/password as the keyboard shows for about 1/2 a second, no matter what I do. So, I tried the format data/system reset again and just loaded in the cmod 7.20 stable. Again, after booting, everything is still there - the google apps and all. How do I get rid of all this stuff so I can try an install from a clean slate? Right now I've been going thru all the data folders I can find and manually removing everything there. I would like to delete a lot of apps, but I never seem to be able to "uninstall".
So, before I start over again, can someone tell me how to clear EVERYTHING (except /boot, /emmc [unless I need to],/sd*) so I have a clean system first?
Thanks!
Dave
Click to expand...
Click to collapse
Boot to CWM and do a factory reset. If you don't have CWM on emmc, make a bootable CWM SD. You can get one on my tips thread linked in my signature. A factory reset clears /data, /cache and clears any apps you may have installed to SD. It does not touch boot, system or emmc media.

no good
leapinlar said:
Boot to CWM and do a factory reset. If you don't have CWM on emmc, make a bootable CWM SD. You can get one on my tips thread linked in my signature. A factory reset clears /data, /cache and clears any apps you may have installed to SD. It does not touch boot, system or emmc media.
Click to expand...
Click to collapse
That's what I've been doing - format data/factory reset option from cwm. Before rebuilding the entire microSD on my Windows PC I have also done a complete format of the media. I then boot CWM from the microSD and install the cmod7 7.20 stable zip - I always assumed this was going straight to the device since when I remove the microSD and boot cmod7 is there. However, none of the pre-existing apps are gone - everything is still there.
I've tried using CWM, advanced options, and format /data - it always fails. So I'm wondering if perhaps the format of /data the is part of the factory reset also fails but the script doesn't error out. Right now I'm going through an extremely time consuming task of manually removing the files and folders in /data via the terminal and su so I get the permissions. If there is another quicker way to clear /data I'd sure appreciate knowing. I've tried some of the treed removes from my Linux experience but they don't seem to work.
Thanks!
Dave
EDIT: forgot to mention - I'm trying your partition restores from the link in your signature - only the "safe" ones - I don't to do that partition 2 stuff and really mess up. Perhaps this will clean everything off.

Thank you thank you thank you!!!!!
leapinlar said:
Boot to CWM and do a factory reset. If you don't have CWM on emmc, make a bootable CWM SD. You can get one on my tips thread linked in my signature. A factory reset clears /data, /cache and clears any apps you may have installed to SD. It does not touch boot, system or emmc media.
Click to expand...
Click to collapse
I followed the link and did the repartitioning and formating with the first 2 scripts (left partition 2 alone!). Installed 7.20 stable - I now have the bar at the bottom of my screens. I'm waiting to format a 16gb microSD then I'm going to try the Kindle app out again, but I'd say this looks REALLY promising! Your scripts did what I wanted to do - they cleared everything out!
Thank you SO much!!!!!
Dave

Thank to everyone!
I just wanted to post a big THANK YOU to all the people who made cwm and cmod 7 so this whole thing would even be possible. Thanks to everyone here who helped me! Now "all" I have to do is just try to learn this! Maybe some place down the road I might try some programming, but I don't know how different it will be from my C using GTK++ on Linux. But first, to learn!
Thank you everyone SO much!
Dave

dweaton said:
That's what I've been doing - format data/factory reset option from cwm. Before rebuilding the entire microSD on my Windows PC I have also done a complete format of the media. I then boot CWM from the microSD and install the cmod7 7.20 stable zip - I always assumed this was going straight to the device since when I remove the microSD and boot cmod7 is there. However, none of the pre-existing apps are gone - everything is still there.
I've tried using CWM, advanced options, and format /data - it always fails. So I'm wondering if perhaps the format of /data the is part of the factory reset also fails but the script doesn't error out.
Click to expand...
Click to collapse
I know you got it all working and I am glad, but just for future reference, the problem you were having probably stemmed from using an old version of CWM. You have to use version 3.2.0.1 or newer or the format of data will fail on the newer nooks. The one in my tips thread is the newest version.

Thanks!
leapinlar said:
I know you got it all working and I am glad, but just for future reference, the problem you were having probably stemmed from using an old version of CWM. You have to use version 3.2.0.1 or newer or the format of data will fail on the newer nooks. The one in my tips thread is the newest version.
Click to expand...
Click to collapse
I did look at the the tar file I downloaded when I was trying to install from a 4gb microSD - it does say only 3.0.2.8, so I'm sure the 16gb I ended up installing from was probably the same, so I'll go grab what you recommended!
Since I don't want to have the problem again, I'm DEFINITELY going to follow your advise!
I had another suspicion for what may have happened, and why I had so much problem from the get-go with cmod 7 - I tried someone else's "put android on your nook" thing, which I know tried to root the nook and then dump some stuff in, and that didn't end up working.
I'm just glad your posts have gotten me going correctly!! BTW - the Kindle app works fine now, too!
Again, thank you SO much!!
Dave

Want to make sure I get this all right
You've been such a great help - I hope you don't mind a couple of more questions:
- The new CWM you recommend is the 5.x.x.x that's on the link, correct?
- Are there any newer releases of Android for the Nook Color? Right now I don't know anything about Android (complete noob [LOVE the movie on the registration page!] ). I know someone who is quite versed in all of this he mentioned that I'm running some name (honeycomb or something like that) and that there are newer ones out there (maybe that was honeycomb). At any rate, are there some updates I could run to make this any "better"? I know the version I'm running also seems to think it's a phone - is there one where it actually thinks it's a tablet?
Again, thank you SO much!
Dave :good:

dweaton said:
You've been such a great help - I hope you don't mind a couple of more questions:
- The new CWM you recommend is the 5.x.x.x that's on the link, correct?
- Are there any newer releases of Android for the Nook Color? Right now I don't know anything about Android (complete noob [LOVE the movie on the registration page!] ). I know someone who is quite versed in all of this he mentioned that I'm running some name (honeycomb or something like that) and that there are newer ones out there (maybe that was honeycomb). At any rate, are there some updates I could run to make this any "better"? I know the version I'm running also seems to think it's a phone - is there one where it actually thinks it's a tablet?
Again, thank you SO much!
Dave :good:
Click to expand...
Click to collapse
Yes that CWM is attached to my tips thread linked in my signature.
You can try CM9 which is tablet based, but it is still in alpha and not as stable as CM7. Don't use honeycomb, it is old and very buggy.

Thanks!
Thanks again for the info! I'll get that copy of cwm right away. Since CM9 is still early, I'll wait on any updates. I really don't know anything yet, but I am having fun with the Nook Color being all Android now. It's nice having the Kindle app and the Nook app - this way have all my books on 1 device, and that works great!
Thanks again!
Dave :good:

[Q] No BN store or books

Hi everybody!
I rooted my Nook Color about two years ago and never looked back (that was two weeks after launch day...I think it was 2.1 Eclair back then). The other day I was futzing about and deleted all my system data. Gak. I attempted to restore using Clockwork Recovery, but alas, I didn't realize until too late that my "newest" backup was from April of 2011. In retrospect, I should have tried to restore from my weekly Titanium Backup, first. As it turns out, the old Clockwork image overwrote the Titanium backup. Bummer.
Anyway, after the restore, the Nook still works perfectly with Google Market et al, but can no longer download any of my purchased books (and the Store doesn't work, either). It has my "Owner Name" and "Account" info correct in "Settings -> Device Info -> About Your NOOKcolor" but I get an error when trying to sync ("nook color internal error exception executing the command").
Is there a way to repair the damage I've done without taking the device back to the stock firmware, wiping it clean, and starting all over from scratch?
If I *do* have to start over, what's the latest and greatest STABLE way of rooting a Nook Color these days?
Any thoughts are much appreciated!

riffrafff said:
Hi everybody!
I rooted my Nook Color about two years ago and never looked back (that was two weeks after launch day...I think it was 2.1 Eclair back then). The other day I was futzing about and deleted all my system data. Gak. I attempted to restore using Clockwork Recovery, but alas, I didn't realize until too late that my "newest" backup was from April of 2011. In retrospect, I should have tried to restore from my weekly Titanium Backup, first. As it turns out, the old Clockwork image overwrote the Titanium backup. Bummer.
Anyway, after the restore, the Nook still works perfectly with Google Market et al, but can no longer download any of my purchased books (and the Store doesn't work, either). It has my "Owner Name" and "Account" info correct in "Settings -> Device Info -> About Your NOOKcolor" but I get an error when trying to sync ("nook color internal error exception executing the command").
Is there a way to repair the damage I've done without taking the device back to the stock firmware, wiping it clean, and starting all over from scratch?
If I *do* have to start over, what's the latest and greatest STABLE way of rooting a Nook Color these days?
Any thoughts are much appreciated!
Click to expand...
Click to collapse
That CWM restore should not have wiped out your Titanium Backup backup files. They should still be on sdcard or emmc media, wherever you saved them. It may have wiped out the installation files but not the backup files. Reinstall TB and see if the backups are still there.
And the best way to start over is to flash the latest ROM (1.4.3) and use Manual Nooter 5.08.20 to root it. Get a cwm flashable version of 1.4.3 in the link in my tips thread linked in my signature. Look at item A15.
Sent from my Nook Color running CM10 and Tapatalk.

Trying to restore from the old Titanium files was a no-go. Even tried from a backup on a different SD card (August 2012)... same result. Tried deleting the /data/system/accounts.db file and rebooting; that just removed my BN login info AND Google login.
So, I've decided to try your suggestion and have run the format 5-6-7 zip file from CWM, and then your 1.4.3 file, also from CWM. So far so good. Many thanks.
Any caveats I need to watch for from here going forward? I have re-registered with BN, and everything looks good.
At this point, I'm faced with some options. From the "Manual Nooter 5.08.20" page, I see:
1. Download one of the Following ManualNooter 5 files based on your needs:
*manualnooter-5.08.20.basic.zip - It doesn't include apps2sd support, and doesn't block B&N updates. Doesn't replace any system files
*manualnooter-5.08.20.basic.block_updates.zip - It doesn't include apps2sd support, but has B&N updates blocked. Doesn't replace any system files
*manualnooter-5.08.20.apps2sd.zip - Includes apps2sd support, but doesn't block B&N updates. It will replace a system file, making it firmware version specific
*manualnooter-5.08.20.apps2sd.block_updates.zip - Includes apps2sd support, and has B&N updates blocked. It will replace a system file, making it firmware version specific.
If you will be flashing with apps2sd support, you will also need to download one of the following kernel images to fully utilize apps2sd support.
Dalingrin OC kernel - Dalingrin 090111 OC kernel
OR Stock kernel - Stock. kernel with apps2sd support
Phew! I assume there are advantages/disadvantages with the firmware-specific stuff? I also assume that BN updates have the potential to wreak havoc with a rooted Nook? I further assume "OC" stands for Over-Clocked?
Which combination would you recommend?
Thanks again!

I would use the basic but block updates. No apps2sd.

leapinlar said:
I would use the basic but block updates. No apps2sd.
Click to expand...
Click to collapse
CWM seems to be gone. Do I need to re-install it in order to load "manualnooter-5.08.20.basic.block_updates.zip?"

riffrafff said:
CWM seems to be gone. Do I need to re-install it in order to load "manualnooter-5.08.20.basic.block_updates.zip?"
Click to expand...
Click to collapse
Installing the stock rom erased it. It is best if you make a bootable SD with CWM on it. See item A10 in my tips thread.

Got it. Running Verygreen's agnostic image with the newest nightly of 7.2. Wow. Things have really changed in the last two years! I can barely find my way around. The learning curve begins. Now I'm trying to find the "gapps...zip" file. From this thread http://forum.xda-developers.com/showthread.php?t=1000957 it says this link should take me there...
"Go to http://wiki.cyanogenmod.com/index.ph...Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip."
Link: http://wiki.cyanogenmod.com/index.php?title=Latest_Version
I dunno. Not seeing it. More searching is called for. :good:

Okay, found the gapps stuff at http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
...the world is bright and gay again! Happy, happy, joy, joy.
Coolness. Thanks for your help. Now to see if I can't finger out some of this new-fangled stuff!

Everything seems to be working, except I cannot create any CWM backups. Telling ROM Manager to "Backup Current ROM" results in the device rebooting into a short Linux boot that appears to attempting to run "gapps installer." Then it shuts down. I can get to a boot menu with the home and power buttons held down, but it's not the CWM menu. From your post here: http://forum.xda-developers.com/showthread.php?p=21885572#post21885572 I guess that CWM doesn't really exist now, but only the Verygreen script. So I guess it's not possible to backup the ROM this way?

riffrafff said:
Everything seems to be working, except I cannot create any CWM backups. Telling ROM Manager to "Backup Current ROM" results in the device rebooting into a short Linux boot that appears to attempting to run "gapps installer." Then it shuts down. I can get to a boot menu with the home and power buttons held down, but it's not the CWM menu. From your post here: http://forum.xda-developers.com/showthread.php?p=21885572#post21885572 I guess that CWM doesn't really exist now, but only the Verygreen script. So I guess it's not possible to backup the ROM this way?
Click to expand...
Click to collapse
To back up... shut nook down... take SD out and put it in computer... use win32diskimager or winimage to create an image of the SD

DizzyDen said:
To back up... shut nook down... take SD out and put it in computer... use win32diskimager or winimage to create an image of the SD
Click to expand...
Click to collapse
Thanks. I'll try that, excepting that I'll use 'dd' seeing as how I don't do Windows.

riffrafff said:
Everything seems to be working, except I cannot create any CWM backups. Telling ROM Manager to "Backup Current ROM" results in the device rebooting into a short Linux boot that appears to attempting to run "gapps installer." Then it shuts down. I can get to a boot menu with the home and power buttons held down, but it's not the CWM menu. From your post here: http://forum.xda-developers.com/showthread.php?p=21885572#post21885572 I guess that CWM doesn't really exist now, but only the Verygreen script. So I guess it's not possible to backup the ROM this way?
Click to expand...
Click to collapse
You can use my modified CWM to do nandroid backups of the SD install. Look in my tips thread linked in my signature and look at item B5.

leapinlar said:
You can use my modified CWM to do nandroid backups of the SD install. Look in my tips thread linked in my signature and look at item B5.
Click to expand...
Click to collapse
Cool. I'll do that. Thanks! :good:

[Q] upgrade to 2.0.6 and re-root?

All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff

How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD

Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff

js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD

Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff

[Q] kfhd missing storage space

i put twrp on my kindle form this thread:
[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
after that my free storage is reduced to 2 gb. when i look under device/ storage somthing called "others" using up 10 gb. i redid the whole thing still the same. what should i do?

What's the exact path to the folder you are referring to? All twrp does is flash the recovery partition, and 2nd boot loader doesn't really use up any space since its not exactly a physical file if I remember right, I believe it's stored in the kernel.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

moiragreen said:
i put twrp on my kindle form this thread:
[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
after that my free storage is reduced to 2 gb. when i look under device/ storage somthing called "others" using up 10 gb. i redid the whole thing still the same. what should i do?
Click to expand...
Click to collapse
You probably had this issue before modding. Restore back to complete factory status and then let your tablet update automatically (OTA.) This should fix the issue.

I'm willing to bet if you poke around you will find a twrp backup folder they are typically 2 gigs and don't show up right in the used space
Sent from my XT907 using xda app-developers app

stunts513 said:
What's the exact path to the folder you are referring to? All twrp does is flash the recovery partition, and 2nd boot loader doesn't really use up any space since its not exactly a physical file if I remember right, I believe it's stored in the kernel.
Click to expand...
Click to collapse
I was misleading with using the slash. I ment 'Storage' under 'Device' in kindle settings.
LinearEquation said:
You probably had this issue before modding. Restore back to complete factory status and then let your tablet update automatically (OTA.) This should fix the issue.
Click to expand...
Click to collapse
After twrp, i modded with Kinology. Issue remained. Did a hundred reset, whipe cash, dalvik cash, ect. Still not working. Restored the whole thing with KFHD_SRTv1.3.5 option 1, thats restore back to stack whith root (without root option did not work, it kept saying device cannot boot). I think that was 7.3.1. Updated to 7.4.6, put twrp with fireflash and again there was a whole lot of nothing using 10 gigs.
mrkhigh said:
I'm willing to bet if you poke around you will find a twrp backup folder they are typically 2 gigs and don't show up right in the used space
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Poked around a lot looking for files like that, I found twrp backup folder whitch was empty, I booted in twrp and scavenged for hidden files, nothing came up like there wouldn't be anything except system.
I really would miss twrp, becase it allowed me to use Kinology which fullfilled my every need that I have for a tablet. Still dont want to sacrifice 10 gb for it. Is it possible that fireflash somehow partitioned it? Sorry if I ask stupid questions. I'm close to a surgeon when it comes to my kindle: I read a lot about it, only understood the half of it but doing it anyway.

moiragreen said:
Did a hundred reset, whipe cash, dalvik cash, ect. Still not working. Restored the whole thing with KFHD_SRTv1.3.5 option 1, thats restore back to stack whith root (without root option did not work, it kept saying device cannot boot). I think that was 7.3.1. Updated to 7.4.6, put twrp with fireflash and again there was a whole lot of nothing using 10 gigs.
Click to expand...
Click to collapse
Do a complete factory reset and then wait for an OTA update. Then this will fix it. You must let an OTA update happen. Get ris of root, the whole nine yards.