Related
Let me apologize first of all as I come from 5 years of using Windows Mobile knwoing what I am doing (cooking ROMs included) and now just got my Galaxy /Android a couple weeks ago and am blank at all of it.
After messing up with some system files and (useless) stock applications (like I removed stk.apk and other stuff) I decided to do a full hardware reset as the phone started getting random crashes.
But after the full reset things only got dramatically worse. I quickly realized all the missing system apps are still missing (I thought they'd be "restored") and basically nothing works, just crashes one after the next, cant use anything.
So, a hardware system reset on the galaxy, doesnt really reset anything except user installed apps and settings... amazing
Can someone please tell me (the idiot here, I know) how to do a real full restore where all system files, all missing files and positively everything gets back in the Tab as it was originally?
What a flippin' nightmare... Thanks in advance very much!
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
Click to expand...
Click to collapse
OK, first of all a big thanks for both file and info. Aside from the Stk.apk, the biggest thing that made me run into problems was trying to update my Contacts.apk:
http://forum.xda-developers.com/showthread.php?t=907399
things didnt work out for me and even after restoring the original files (Contacts.apk and Contacts.odex) nothing really worked again, reason for wich I tried a system reset.
Now, do I need to re-root the Tab or its still rooted, and can I perform the operations easily with Root Explorer like I did before? You mentioned to use adb and set permissions to 644 after push but, sorry again for the ignorance, I have no clue what adb is nor what/how to set permissions. Pathetic to be ignorant huh?
My last 2 questions are, where could I find the original Contacts.apk and Contacts.odex and if needed a full ROM to do a total restore?... hopefully I wont need to get to that point?...
Thanks a million again.
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
bartito said:
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
Click to expand...
Click to collapse
Hmmmm thanks again but I think Im beyond all this. I dont have a file manager on my system, just realized I deleted the useless stock one and had repalced it with Root Explorer and ES File Explorer. I have them on my External SD Card to install them again but withou a file manager or an app installer cant get to them. And I tried download an app installer from the Market and get Framework errors non-stop and downloads do not initialize... I think Im beyond a quick fix... how do I get my hands on a stock full ROM to restore everything... and how? What a nightmare... gotta tell you, I love Windows Mobile... I love it... never ran into anything like this in the past 5 years of using it... never...
Thanks again!
use "adb" in order to access to your tab from your desktop pc.
bartito said:
use "adb" in order to access to your tab from your desktop pc.
Click to expand...
Click to collapse
Cant. Dont even know if I need Kies installed or not (I did have it installed) but adb just asks me to connect the phone and thats it... its connected aready... this is desperating...
OK I did manage to connect with adb but, how to I install applications? I can navigate to my SD card where I have ES File Explorer and Root Explorer but dont seem to be able to install them... Also if i try to copy Stk.apk I get immediately an failute message... this is crazy...
OK so I managed to install ES File Explorer and Root Explorer with adb... crazy process. It seems my phone is still rooted after the reset. From the phone I copied Stk.apk back to /system/apps where it was before deleted.
But needless to say nothing got fixed... not sure if Stk.apk is now "actually" installed or just there in the folder. But still nothing works and crashes every 10 seconds... logs provider, dialer, phone, framework, contacts... its all a firework of crashes...
Given that you've hard reset your device already, you are pretty much wasting your time trying to "fix" what you broke by messing with /system, and you should really just flash another ROM.
My suggestion would be to follow the advice on this thread.
Regards,
Dave
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
VeEuzUKY said:
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
Click to expand...
Click to collapse
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
foxmeister said:
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
Click to expand...
Click to collapse
Yes Dave you are right, right and right again!!! Thank you for the wisdom and advice!!!
The main thing I have understood with today's messy experience was that the actual ROM files are never deleted or damaged as long as you dont access them via a rooted tool and start deleting them. Now I understand that Titanium Backup, Sprint Backup (my favorite), My Backup Pro and others, only back-up and restore what the user installs on top of the ROM itself. So a full "reset" wipes all that data but leaves the ROM files as they always were. If they got damaged in the process, they'll still be damaged till a a full ROM restores all system data, now I get it.
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Till I find an app or way to do a simple one-click "backup everything" and then "restore evertything" I always feel vulnerable to changes I make to the Tab that may get it unstable or corrupt and then not being able to be restored properly without a full ROM Flash and then re-installing all from scratch.
With WinMo, I could do all sorts of crazy experiments and tweaking and after that, a registry restore or back-up restore would bring me back my phone to exactly like it was with all my stuff and configuration in a matter of seconds or minutes. Thats what I need to find out with this Tab/Android and then Im ready to be able to explore messing up with this knowing I can always easily go back within minutes to the state I had before with all my apps and settings.
This is what I need to learn next how to do! Trampoline without a safety net is not a good idea. Ive alwways loved WinMo for the ease of backing up and restoring whatever I was doing on my handsets withjout ever worrying to put myself at risk to loose it all. I need to learn this on Android and its definitely more intricate!
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
instechgainza said:
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
VeEuzUKY said:
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
Click to expand...
Click to collapse
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
instechgainza said:
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Where is the modaco kernel section you refer to? I can search for hours and find zilch... these blogs are endless...
VeEuzUKY said:
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Click to expand...
Click to collapse
What you want is a Nandroid backup, which you can only make from a recovery image like Clockworkmod recovery.
Essentially, this does exactly what you want, but you need to flash a new kernel (e.g. the MoDaCo kernel) which supports Clockwordmod.
Regards,
Dave
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
Click to expand...
Click to collapse
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
b0ricuaguerrero said:
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
Click to expand...
Click to collapse
When I delete stk.apk (for me useless useless useless) the first thing that happens immediately is that when I hang-up on a call made or received, the Tab vibrates then freezes for about 5 seconds then tells me the phone application has crashed. I tried this with 2 ROMs now as a test and its guaranteed. More even, if you use a program like SYSTEM APP REMOVER you can emulate the removal of an app by disabling it... it only takes me to disable STK and a reboot for the phone not to work. cant get rid of it, that simple
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
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:
I have played Android devices for several years and rooted them for several years. The first thing after rooting is to change the font under /system. But I heared that this may coz OS reset!
Did anybody try this? what if we use a softLink for the font file to avoid the checksum comparing?
Any changes to /system will cause the bootloop reset. However, if you pull a file from /system and symlink it to a file not located on system (/data for instance) then the symlink will not cause a bootloop. When fooling with systemui, you can quickly get yourself in trouble if there is a flaw in your files though, so be careful. I would make a nandoird before trying it.
dbh369 said:
Any changes to /system will cause the bootloop reset. However, if you pull a file from /system and symlink it to a file not located on system (/data for instance) then the symlink will not cause a bootloop. When fooling with systemui, you can quickly get yourself in trouble if there is a flaw in your files though, so be careful. I would make a nandoird before trying it.
Click to expand...
Click to collapse
I have instructions on how to do the symlinking in my HD/HD+ Tips thread linked in my signature. But like dbh369 said, be careful. I was able to make a Vietnamese font for a user doing this. Look in the Q&A section, I think.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks above two. Are you sure that Stock will check every file under /system? I plan to replace the font file directly and see the result. I will report the result. By the way, if it's reset, I plan to use CM10.1.
songxiny said:
Thanks above two. Are you sure that Stock will check every file under /system? I plan to replace the font file directly and see the result. I will report the result. By the way, if it's reset, I plan to use CM10.1.
Click to expand...
Click to collapse
Yes I am positive, any new or changed file on /system will reset stock. It automatically checks each file it finds and checks to see if it is on its manifest list and if it does not match the manifest or the checksums there, it will reset. So don't even try unless you want to lose everything including your media files.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Yes I am positive, any new or changed file on /system will reset stock. It automatically checks each file it finds and checks to see if it is on its manifest list and if it does not match the manifest or the checksums there, it will reset. So don't even try unless you want to lose everything including your media files.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
yes, you are right. I tried to modify the font file directly, stock reset. Even I delete the file, it reset. But, your sysLink tips work.
Thanks a lot.
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