Related
Hi,
I want to install a new ROM without loosing any data and settings. I have made a Titanium backup.
As I now have only one SDCard, will ti be OK to copy the titanium directory to the PC, do the clean install, and copy ONLY the TB directory back to the SD, and do a restore?
Thanks for answers,
velizet said:
Hi,
I want to install a new ROM without loosing any data and settings. I have made a Titanium backup.
As I now have only one SDCard, will ti be OK to copy the titanium directory to the PC, do the clean install, and copy ONLY the TB directory back to the SD, and do a restore?
Thanks for answers,
Click to expand...
Click to collapse
If the current ROM is any of the ff:
CM7 Stable (7.0, 7.1)
CM7 Nightly
Phiremod
CM7 MiRaGe KANG
AND the new ROM any of the above as well, you can just do the ff:
Put the new ROM's zip as well as any associated Kernel zips to the root of your microSD card (or anywhere really, doesn't matter. It's just so you can easily see and navigate to it)
Reboot to ClockWorkMod Recovery menu. Advisable if you have the latest CWM installed, which would be 3.2.0.1. (You can get the latest CWM through ROM Manager, which can be downloaded off the Market.)
Once you're there, go to Mounts & Storage.
Format System
Format Cache
Afterwards, go ahead and install your new ROM.
Once it boots up, you will still have all your apps even if you don't use TitaniumBackup since you did not format the "Data" partition.
All of the instructions above is if your install is in your NookColor's eMMC as opposed to running it off a microSD card.
Hope this helps.
les02jen17 said:
If the current ROM is any of the ff:
CM7 Stable (7.0, 7.1)
CM7 Nightly
Phiremod
CM7 MiRaGe KANG
AND the new ROM any of the above as well, you can just do the ff:
Put the new ROM's zip as well as any associated Kernel zips to the root of your microSD card (or anywhere really, doesn't matter. It's just so you can easily see and navigate to it)
Reboot to ClockWorkMod Recovery menu. Advisable if you have the latest CWM installed, which would be 3.2.0.1. (You can get the latest CWM through ROM Manager, which can be downloaded off the Market.)
Once you're there, go to Mounts & Storage.
Format System
Format Cache
Afterwards, go ahead and install your new ROM.
Once it boots up, you will still have all your apps even if you don't use TitaniumBackup since you did not format the "Data" partition.
All of the instructions above is if your install is in your NookColor's eMMC as opposed to running it off a microSD card.
Hope this helps.
Click to expand...
Click to collapse
Did all that,
Booted to CM7.2, lost gmail, lost market. Now trying to roll back.
velizet said:
Did all that,
Booted to CM7.2, lost gmail, lost market. Now trying to roll back.
Click to expand...
Click to collapse
You may need to reinstall gapps.
velizet said:
Did all that,
Booted to CM7.2, lost gmail, lost market. Now trying to roll back.
Click to expand...
Click to collapse
Installing gapps again is part of installing a new ROM, which I forgot to mention. My bad. Just download gapps from ROM Manager, then flash it via recovery or via ROM Manager too.
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
les02jen17 said:
Installing gapps again is part of installing a new ROM, which I forgot to mention. My bad. Just download gapps from ROM Manager, then flash it via recovery or via ROM Manager too.
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
Click to expand...
Click to collapse
Hi,
Now I am back to the latest 7.1 Nightly with everything working, had to install market.apk, than gmail.
The reason I do not want to loose data is, as I am not in US, because of some stupid Google policy, I had to sideload some apks like G+, currents, earth, maps, etc. and I do not want to fetch them again.
So my 2 questions are:
1- If I install gapps again, will I be able to keep these sideloaded apps?
2- Is it worth to move to 7.2 at all? (BTW 7.2 RC0 is around 70 MB, whereas the latest nightlies are all around 100 MB)
Why don't you move those .apk files to another folder, say, the eMMC.
votinh said:
Why don't you move those .apk files to another folder, say, the eMMC.
Click to expand...
Click to collapse
Because I don't know what will happen if I move those to another place, say, emmc.
velizet said:
... I had to sideload some apks like G+, currents, earth, maps, etc. and I do not want to fetch them again.
Click to expand...
Click to collapse
Why would you have to? O-M-G! you aren't one of those, DELETERS are you?
velizet said:
Because I don't know what will happen if I move those to another place, say, emmc.
Click to expand...
Click to collapse
The .apk file is more like the package, let's say, like a .zip file (in Windows), you can make 1001 one copies if you want. You can move it from drive C: to drive D if you want. You can move it to the external hdd if you want. You can store it on the cloud if you want.
Basically, you do whatever you want with it.
You might not understand what I meant, I guess.
Just store it (them) to another storage so you can access it (them) and reinstall later if you need.
MISRy said:
Why would you have to? O-M-G! you aren't one of those, DELETERS are you?
Click to expand...
Click to collapse
If you read my op, you will see the answer.
votinh said:
The .apk file is more like the package, let's say, like a .zip file (in Windows), you can make 1001 one copies if you want. You can move it from drive C: to drive D if you want. You can move it to the external hdd if you want. You can store it on the cloud if you want.
Basically, you do whatever you want with it.
You might not understand what I meant, I guess.
Just store it (them) to another storage so you can access it (them) and reinstall later if you need.
Click to expand...
Click to collapse
I know what you mean, but if you look at the context I'm using, that piece of info is not helpful.
What I don't know is the Android system, where it keeps the applications, what happens when I install the system, how are apks affected etc.
For example in windows, you cannot just upgrade the system and expect every installed application to work.
The main point of the original post was trying to understand these.
Unless you want to become an OS developer, in this case an Android OS guru, then you need to learn and understand clearly the structure of it. If you are just a normal user or power user, why make your life harder digging into what and/or how the system and its associated files work???
Just like in Windows, all you need is the installation package (file), install it, it will install to the default directory, all you have to do next is run the executable file and let it run.
Next time, if you want to re-install, all you need is that "installation package". Why do you need to care what happen w/i those default installed folders such win/system32/xxxx or C:\Program Files\xxx?
Yes, sure, you can dig into it to understand more about, but why would you do that if you are just an user?
Back to your question, if I understand correctly, you want to REINSTALL those apps (if they are not coming back after install new ROM) and that's what I tell you.
Another note: unless you are intending installing the completely new custom ROM, /data need to be formatted, otherwise, no need to bother it.
votinh said:
Unless you want to become an OS developer, in this case an Android OS guru, then you need to learn and understand clearly the structure of it. If you are just a normal user or power user, why make your life harder digging into what and/or how the system and its associated files work???
Just like in Windows, all you need is the installation package (file), install it, it will install to the default directory, all you have to do next is run the executable file and let it run.
Next time, if you want to re-install, all you need is that "installation package". Why do you need to care what happen w/i those default installed folders such win/system32/xxxx or C:\Program Files\xxx?
Yes, sure, you can dig into it to understand more about, but why would you do that if you are just an user?
Back to your question, if I understand correctly, you want to REINSTALL those apps (if they are not coming back after install new ROM) and that's what I tell you.
Another note: unless you are intending installing the completely new custom ROM, /data need to be formatted, otherwise, no need to bother it.
Click to expand...
Click to collapse
First of all, according to my philosophy of life, knowledge does not make life harder in the long run.
Secondly, I really doubt copying an .apk file to a medium as you say makes it install automatically.
Thirdly, I want to know when an application is installed, is it contained in its own directory, or does it write something to somewhere like a registry or what, and also where do the former preferences stay, etc.
Hope I can make myself clear.
velizet said:
First of all, according to my philosophy of life, knowledge does not make life harder in the long run.
Click to expand...
Click to collapse
Absolutely true, no argument with this.
Secondly, I really doubt copying an .apk file to a medium as you say makes it install automatically.
Click to expand...
Click to collapse
There is nowhere that I said it will AUTOMATICALLY install. You INSTALL it when you need it.
Thirdly, I want to know when an application is installed, is it contained in its own directory, or does it write something to somewhere like a registry or what, and also where do the former preferences stay, etc.
Click to expand...
Click to collapse
I leave this question to other Android gurus to help you.
hi today i bought hp touchpad and i'm gonna install CM9 on it. i used the ACMEInstaller and i did the steps as its shown in the guide of CM. MOBoot got installed and CM9 but it doesn't boot. clockworkmod is not installed at all
what to do? anyhelp??
gevamran said:
hi today i bought hp touchpad and i'm gonna install CM9 on it. i used the ACMEInstaller and i did the steps as its shown in the guide of CM. MOBoot got installed and CM9 but it doesn't boot. clockworkmod is not installed at all
what to do? anyhelp??
Click to expand...
Click to collapse
Step by step, what exactly did you do?
gevamran said:
hi today i bought hp touchpad and i'm gonna install CM9 on it. i used the ACMEInstaller and i did the steps as its shown in the guide of CM. MOBoot got installed and CM9 but it doesn't boot. clockworkmod is not installed at all
what to do? anyhelp??
Click to expand...
Click to collapse
Isn't there a war going on practically next-door to you! I wouldn't be worried about your Touchpad...
But nevertheless, did you create a "cminstall" folder with CWM, CM9, Moboot, and GAPPs; then run the AcmeInstaller2 from the command prompt?
Perhaps you got a bad version of CWM! I would try AcmeUninstaller and do it again with a new download! :good:
gevamran said:
hi today i bought hp touchpad and i'm gonna install CM9 on it. i used the ACMEInstaller and i did the steps as its shown in the guide of CM. MOBoot got installed and CM9 but it doesn't boot. clockworkmod is not installed at all
what to do? anyhelp??
Click to expand...
Click to collapse
You probably didn't rename clockwork with update- in front check out my post here it should have all the files you need correctly named plus a link to a good install guide. http://forum.xda-developers.com/showpost.php?p=30249437&postcount=624
I hope this helps.
Maybe this
gevamran said:
hi today i bought hp touchpad and i'm gonna install CM9 on it. i used the ACMEInstaller and i did the steps as its shown in the guide of CM. MOBoot got installed and CM9 but it doesn't boot. clockworkmod is not installed at all
what to do? anyhelp??
Click to expand...
Click to collapse
This thread helped me
http://forum.xda-developers.com/showthread.php?p=31432226#post31432226
sstar said:
You probably didn't rename clockwork with update- in front check out my post here it should have all the files you need correctly named plus a link to a good install guide. http://forum.xda-developers.com/showpost.php?p=30249437&postcount=624
I hope this helps.
Click to expand...
Click to collapse
thnx all so much!!! the problem was because i didn't rename! i found it in a forum. thnx guys.
-SGA- said:
Isn't there a war going on practically next-door to you! I wouldn't be worried about your Touchpad...
But nevertheless, did you create a "cminstall" folder with CWM, CM9, Moboot, and GAPPs; then run the AcmeInstaller2 from the command prompt?
Perhaps you got a bad version of CWM! I would try AcmeUninstaller and do it again with a new download! :good:
Click to expand...
Click to collapse
Brings up a good point for posterity. Make sure you are using ACMEInstaller2, not just ACMEInstaller.
I have had a similar problem, installed CM9, ICS and moboot, didn't realise that I needed to change the Clockworkmod file name to update and didn't get CWM on my boot list.
I have, subsequently, edited the file name and re-run the installation from the novacom step, but this hasn't resolved the issue. Do I need to do a complete un-install and then try again? If so, is the ACME uninstaller the way to go and are there any instructions I need to be aware of.
Thanks in advance
Andy H said:
I have had a similar problem, installed CM9, ICS and moboot, didn't realise that I needed to change the Clockworkmod file name to update and didn't get CWM on my boot list.
I have, subsequently, edited the file name and re-run the installation from the novacom step, but this hasn't resolved the issue. Do I need to do a complete un-install and then try again? If so, is the ACME uninstaller the way to go and are there any instructions I need to be aware of.
Thanks in advance
Click to expand...
Click to collapse
This is the file you need https://www.box.com/s/0dc8571f09a8f285df59 place it in the cminstall folder via webos and then run acme installer.
New link http://db.tt/TofjHEzk
sstar said:
This is the file you need
place it in the cminstall folder via webos and then run acme installer.
Click to expand...
Click to collapse
Thanks for that sstar, only problem is that the file is not accessible due to bandwith issues.
I also already have the tenderloin file, (cm-9-20120923-NIGHTLY-tenderloin) but when I tried running ACMEInstaller 2 again, after renaming to updte-cm-9-20120923-NIGHTLY-tenderloin, it still didn't add CWM to the boot menu - I have to admit to being a bit confused, as a noob, so not sure quite where I've gone wrong.
I followed instructions I found on Liliputing (can't poost the link as a noob)
Pm sent, I will try to upload to another server.
New link http://db.tt/TofjHEzk
Andy H said:
Thanks for that sstar, only problem is that the file is not accessible due to bandwith issues.
I also already have the tenderloin file, (cm-9-20120923-NIGHTLY-tenderloin) but when I tried running ACMEInstaller 2 again, after renaming to updte-cm-9-20120923-NIGHTLY-tenderloin, it still didn't add CWM to the boot menu - I have to admit to being a bit confused, as a noob, so not sure quite where I've gone wrong.
I followed instructions I found on Liliputing (can't poost the link as a noob)
Click to expand...
Click to collapse
ok youre naming the Clockworkmod Recovery wrong. remember theres CyanogenMod nightly roms and then theres ClockworkmodRecovery. the recovery never has nightly releases.
https://www.box.com/s/9fd332052819583a251c here this is the recovery zip file you want to have in the cminstall folder when you run acmeinstaller2. do not change its name, put the whole zip file as is into the cminstall folder.
haxin said:
ok youre naming the Clockworkmod Recovery wrong. remember theres CyanogenMod nightly roms and then theres ClockworkmodRecovery. the recovery never has nightly releases.
https://www.box.com/s/9fd332052819583a251c here this is the recovery zip file you want to have in the cminstall folder when you run acmeinstaller2. do not change its name, put the whole zip file as is into the cminstall folder.
Click to expand...
Click to collapse
Exactly what haxim said, I also edited my post with same CWR.
Thanks sstar and haxin for the help - have downloaded the correct file now and will put it in the cminstall folder and try the ACMEInstaller again, probably tomorrow though as it's getting late now.
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 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
Finally got my Sprint CDMA Gtab with broken internal Sd working on CM10.1. However I can't get the gapps package install and I don't have a working clkworkmod recovery ... It always gets clobbered.
Is there an easy way to install gapps from within Android?
Cm10.1 kernel definitely contains a cwm recovery.
How is yours without one?
Gapps is a pack of apk and files.
Read the updater-script in its META-INF folder and you can do exactly like what the script does, manually.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Cm10.1 kernel definitely contains a cwm recovery.
How is yours without one?
Gapps is a pack of apk and files.
Read the updater-script in its META-INF folder and you can do exactly like what the script does,
Click to expand...
Click to collapse
This is one of those CDMA Gtabs with the busted internal SD so all the partition assignments are screwy. The ROM I've had most luck with is the CM10.1 with the Humberos? Kernel... Don't know if it contains CWM. Every time I flash in the ROM it wipes CWM but if I reinstall CWM then the ROM doesn't boot so right now they are mutual exclusive.
Trying to install a gapp apk file with FileManager doesn't work... It gets going but then says install failed... I presume the partitioning is screwing it up.... Gave it perms and made /system rw, still no go.
Anyways I just reinstalled the whole thing, oddly I have to flash another CM10 ROM first with CWM (which doesn't boot) then follow it with the 10.1 ROM but this time I also did the gapps. Now everything is 'fine' although I still don't have CWM...
UPDATE: I see that others are finding their recovery clobbered with this Rom...
http://forum.xda-developers.com/showthread.php?t=2043421