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
Related
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app.
Click to expand...
Click to collapse
ADP builds of Android do not have TMobile apps such as Amazon MP3. This has been discussed ad nauseum if you had bothered to search.
mimic1011 said:
I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
It's a protected app. If you need it that bad that I suggest you go back to an RC build and do research before blindly flashing whatever build of Android is at the top of the forum.
mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
If you still have the RC firmware you can just unzip it copy the amazon apk out and install it into the adp the amazon works. I dont think anyone has the IM app working though
We should have an official rc update from tmobile real soon, which will have amazon mp3, myfavs, etc...
Just open a RC33 update.zip and extract the file from /system/app. Then you can install it by adb push.
Verified as working. I just added it to the app folder of Dudes 1.1 build and then did the update and it works just great. Purchased and downloaded a song to verify.
Here it Is
http://droiddeveloper.com/com.amazon.mp3.zip
enjoy it works for me...
Really Bad,
In Germany it cannot charge my creditcard... It has enough money on it.
I have the dude's 1.5 version, and cant seem to get it running. It forces closed upon trying to open. Any thought? It is saved to my SD in the app folder.
TIA
Read my guide
http://forum.xda-developers.com/showthread.php?p=3763025
TY SolemnWishing, this is how I got the app on my SD card to begin with - yours is a very helpful thread for a n00b like me. Unfortunately, I was never able to get the app to open. I am not sure how I could have messed it up - pretty simple, I navigate to the app folder on my SD and click the apk file which proceeds to install Amazon MP3. No go.
If you have any ideas on what the problem might be I would appreciate the input.
Thanks again for your great tutorial
Hmm... I assume you deleted the .zip and renamed it to .apk, what firmware are you using?
I am using firmware 1.5. Yes I renamed to apk. I wants to work, just force closes before it fully loads. I also have this problem with oi music player. It used to work, now no longer loads. I wonder if my SD card is the problem. It is 8 gb, but I am sure only like a class 2 card.
Strange. I have JF 1.5 and installed the Amazon app the normal way for any app on the G1 and have rebooted several times. The app still works. I thought if you did not push the app to the G1 it would need to be reinstalled each time you reboot the device?
Well, I am pretty positive it was my SD card - after writing my post this morning I pulled the SD card and have not been anble to get the phone back since. This thread pretty accuratly describes what is going on...long story short, i think I fried my SD card and as a result am stuck on Splash 2. I have wiped several times...
http://forum.xda-developers.com/showthread.php?t=516874
uggg...all for mp3's!!!! any thoughts and lots of luck would be appreciated.
K
Ahh I did the same thing. Here is what you need to do, you will need to force format it. Windows will NOT detect the card, and it may even freeze your computer. Put the phone into another device, such as a palm pilot or another cell phone and format it from there. It shouldn't take very long, and when it is completed, it will likely say the memory card only has 5Kb or so of memory on it. NOW insert the card into your computer and reformat it into a FAT32 format (+Ex2 for apps to SD) and you should be good! Of course, you will need to reload all your files though. That will fix your SD card. As for your phone... you will need to completely reflash a new firmware onto it, as right now starting up your phone is looking for items on your SD card which it may need, which no longer exist.
edit: if that doesn't work, completely start from the beginning by flashing the dreamimg.nbh file for rooting.
I was able to reformat the SD card, lost all my backups of course, and had to reflash dreaming.nbh and start from scratch. No biggy, at least i still have my phone.
thanks for all the tips...once i get my card re-partioned, I will try the Amazon.apk again.
K
I got it to load - thanks for all your help.
K
No problem at all, glad I could help.
i made an nandroid backup with amon ra 2.2.1 with sd-ext included and when i reboot, everything was gone, as if the data got wiped....
i see some broken apps so i geuss something happended with the ext partition
my sd-ext map is empty and i have this ext.tar in my nandroid map
wtf happened!?
shiyou,
You are having too many problems from the beginning. I posted some tips on your first thread, but never heard back. Also, a member recommended doing more research before going forward. The N1 is different from other phones as far as flashing roms.
I would recommend you do this assuming you have a working rom or working backup and sdcard backup. Depending what you have or don't have the below order may vary. Maybe someone can help us there:
1. Take your sd card out of phone--believe you said you have a backup--format it with sdformatter: http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
You can dl manual also--mainly select full erase on and size adj on as format options.
Put your backup back on sdcard while still outside phone. Put card back in phone and boot into Amon recovery. Go thru the partition steps to get 1gb ext3 and 0swap.
At this point you need to have a working rom to boot into. If not other steps may be needed.
I use Titanium Backup to manage apps, the paid version. After I flash a new rom, I open TB, or get it from Market if not part of rom. Then I restore all apps with data. NOT system data. Then I delete any old rom apps and do a refresh and then backup all apps and data.
At some point you need to get rid of Rom manager and Clockwork and flash a fresh Amon_Ra 2.2.1 from his site: http://forum.xda-developers.com/showthread.php?t=611829 Before flashing make sure the install recovery file from old revovery is deleted thru Root Explorer, see this link: http://forum.xda-developers.com/showthread.php?p=9414097#post9414097. You don't have to use adb, just Root Explorer. Change permission first to R/W.
You can push the 2.2.1 .img after, downloading to root of sdcard, with Terminal Emulator using these commands:
Open TE and type:
SU
at # type flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img then hit enter. I usually check md5's with a file explorer. The recovery-RA-passion-v2.2.1.img part above should be the exact name of the img file you downloaded.
2. Before flashing an update to a rom wipe dalvik cache and cache in recovery
3. If flashing a new rom wipe Phone's System with Temasek's System Wipe zip 3X by flashing from recovery. It should be in your download folder.
http://forum.xda-developers.com/showthread.php?t=723844&page=1767
Then wipe Dalvik Cache and anything else that wasn't wiped with System Wipe zip 5X
4. You probably already know, but you can't restore a CWMod backup using Amon_RA or vice versa.
5. Read all the OP pages on the links I posted carefully
This is the way I been doing this for a long time--and rarely need any help or have problems. The system wipe is critical as old files can be left on phone even after a phone data wipe and flashing new rom.
Hope this helps and I haven't left anything out. Not a good typer. If I did--someone will correct me and some things are personal preference. But these have worked well for me.
BTW: If you have no good rom, you may want to dl the latest CM7 RC or nightly to pc and put it on sdcard after you format and put your sdcard backup from pc to phone. Then it is there to flash after card is ready and good recovery installed. You can always put the 2.2.1 on I mentioned after you get rest worked out. But, you gotta get off CWMod 3.0.
You should not use the beta Dark Tremor either, Would dl the the latest non beta.
Also, want the correct gapps for CM7 from OP page, and flashing order is rom/gapps/DT
Ken
I guess I was the member who recommended doing more research. So let me repeat:
I suggest leaving your phone alone and reading A LOT before you start doing something with it.
Yea, Sorry Jack
I was too lazy to go back and look--been a busy day and Fits is giving me a hard time on another thread
rugmankc said:
Yea, Sorry Jack
Click to expand...
Click to collapse
Nothing to be sorry for But indeed, I agreed with your point - someone who's looking for help rooting the phone and doing basic stuff for several days in a row, encountering a lot of problems, is most probably not ready for it, or not willing to read the guides.
You were right Jack on last thread. OP has now abandoned two threads he/she started and again asking for help on a CM7 thread.
No return to either with thanks and still looking for one magical answer, wondering why his phone don't work.
I gave enough advice for a dozen new users and over a year of flashing/backup expertise all in one post.
If he had done it right to begin with and followed some advice, he'd be running smooth. Card could be bad too, don't know.
I am done--
Ken
I love how you two are having this random conversation hahaha. Although I don't understand how the op did a nandroid backup and his phone wiped.. he mustve clicked wipe and confirmed it instead of nand backup. It's nearly impossible. I also decided (out of boredom) to look at his other thread.. Jack you said "Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them." and what HE did: "i tried factory reset but didnt work..." lmfao you sir, are too nice jack! I'll give you two a thanks for the entertianment!
Well, rom development is slowing
Gotta do something
can't tell the same. 2 times i saved by nandroid due to bad flashing issue...
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:
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
I am looking for a way to flash complete stock rom witch is no where to be found? I deleted system apps thinking that will do the 8 boot fail thing and actually it didn't work like it did before? I need a flashable stock rom if it's possible? Any ideas?
Edit:
I also did a factory reset in cwm and that did not work either.
If you'd like to restore your device to factory default, you're need to do the "8-boot-loop-fail". This is not an automatic process, and you must do it manually.
Turn off your device.
Turn on your device.
Once you see the text "Nook" on your screen (before your Nook boots up), hold the power button down until the screen goes blank (turns off).
Repeat from step 2, seven more times (totalling to 8 failed boot attempts).
Do this eight (8) times, and your Nook will restore to factory defaults on the ninth boot. On the ninth boot, do not turn it off, let it do it's thing. It will take a while, and will restore the device back to stock; erasing all data on Internal Storage.
When performing the 8 boot-loop, I'd note down somewhere the amount of times you've turned your Nook off, as you can easily lose count.
HiddenG said:
If you'd like to restore your device to factory default, you're need to do the "8-boot-loop-fail". This is not an automatic process, and you must do it manually.
Turn off your device.
Turn on your device.
Once you see the text "Nook" on your screen (before your Nook boots up), hold the power button down until the screen goes blank (turns off).
Repeat from step 2, seven more times (totalling to 8 failed boot attempts).
Do this eight (8) times, and your Nook will restore to factory defaults on the ninth boot. On the ninth boot, do not turn it off, let it do it's thing. It will take a while, and will restore the device back to stock; erasing all data on Internal Storage.
When performing the 8 boot-loop, I'd note down somewhere the amount of times you've turned your Nook off, as you can easily lose count.
Click to expand...
Click to collapse
I haven't messed around with the nook.. but before I was able to delete a system app and it restored itself after a reboot?
Anyways.. Your guide did work. Thank you!
So my question now is are we able to edit stock files without it rebooting?
anthony062991 said:
I am looking for a way to flash complete stock rom witch is no where to be found? I deleted system apps thinking that will do the 8 boot fail thing and actually it didn't work like it did before? I need a flashable stock rom if it's possible? Any ideas?
Edit:
I also did a factory reset in cwm and that did not work either.
Click to expand...
Click to collapse
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
anthony062991 said:
I haven't messed around with the nook.. but before I was able to delete a system app and it restored itself after a reboot?
Anyways.. Your guide did work. Thank you!
So my question now is are we able to edit stock files without it rebooting?
Click to expand...
Click to collapse
Glad to hear you've got it sorted.
I'm unsure which stock/system app would cause the reboot, as I haven't looked too deeply into it, sorry. Regarding editing stock files; yes, you can edit to your hearts content to what is visible. However once rooted, you can then edit additional files. You may get away with editing certain files, however, if you edit anything within the "/system/" directory, that will force a system reboot, and will erase all your content.
So in basic terms, you cannot edit within the "/system/" directory on the stock ROM. There maybe other files too which are outside this directory, but I haven't tested them either, sorry. But I can tell you that anything in system is a no-go.
All the best.
leapinlar said:
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Thank you! I will save the zip for backup. It will be much easier then rebooting 8 times.
HiddenG said:
Glad to hear you've got it sorted.
I'm unsure which stock/system app would cause the reboot, as I haven't looked too deeply into it, sorry. Regarding editing stock files; yes, you can edit to your hearts content to what is visible. However once rooted, you can then edit additional files. You may get away with editing certain files, however, if you edit anything within the "/system/" directory, that will force a system reboot, and will erase all your content.
So in basic terms, you cannot edit within the "/system/" directory on the stock ROM. There maybe other files too which are outside this directory, but I haven't tested them either, sorry. But I can tell you that anything in system is a no-go.
All the best.
Click to expand...
Click to collapse
That is what I was messing with. The "/system" files. I deleted some stock apps and it did not restored itself after a reboot? I am really shocked that it did not reboot itself back to its default. Last time i deleted an app from the /system it restored back to default. I used the latest Es File Explorer.
anthony062991 said:
Thank you! I will save the zip for backup. It will be much easier then rebooting 8 times.
That is what I was messing with. The "/system" files. I deleted some stock apps and it did not restored itself after a reboot? I am really shocked that it did not reboot itself back to its default. Last time i deleted an app from the /system it restored back to default. I used the latest Es File Explorer.
Click to expand...
Click to collapse
It could be that ES File Explorer did not really delete them. You have to set /system to r/w before deleting works.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
It could be that ES File Explorer did not really delete them. You have to set /system to r/w before deleting works.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I did R/W to the entire system. I deleted voice recording and then i forget the other apps, but it was all the system. I rebooted and it was completely out of the system. I am going to try to make google apps to work with stock rooted without it restoring itself after a reboot?
Edit:
I was on 2.0.6 Firmware if that means anything?
Edit:
You can edit /system/app but not anything else.
I install gapps and rebooted just fine and it kept all my stuff without it restoring itself..
Thanks
leapinlar said:
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Wow, it is useful for me !thanks