Can someone upload a copy of this file?
I try to install ota and failed in this point because stickmount modified this file at install them.
Need this from someone have 5.0 without stickmount installed.
Thanks in advance and sorry for my english.
dacbes said:
Can someone upload a copy of this file?
I try to install ota and failed in this point because stickmount modified this file at install them.
Need this from someone have 5.0 without stickmount installed.
Thanks in advance and sorry for my english.
Click to expand...
Click to collapse
Just flash the new factory image (without wiping data).
How, can you explain this with detail, please?
Solved install factory image without wipes.
Thanks
Related
how do you upgrade the clockworkmod recovery?
I have the 3.0.2.8 and the latest one is 3.2.0.1 is there a update.zip? because I went to http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html and is image file.
carlosraf20 said:
how do you upgrade the clockworkmod recovery?
I have the 3.0.2.8 and the latest one is 3.2.0.1 is there a update.zip? because I went to http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html and is image file.
Click to expand...
Click to collapse
Open up your "ROM Manger" app and click "Flash ClockworkMod Recovery" and it will update it.
using the image file for 3.2.0.1 ? sorry to ask to many questions am new to this. I figure it out now thanks for the the help
carlosraf20 said:
using the image file for 3.2.0.1 ? sorry to ask to many questions am new to this.
Click to expand...
Click to collapse
Don't appologize for asking questions-we all need answers to one thing or another
The first thing you want to do is go to the android market and search for Rom Manager. You already have this installed if you are running CM7, but you need to update it to the newest version.
Then, Just open your app drawer and open up Rom Manager. When it opens, the very top line says "Flash Clockwork Mod Recovery". Tap on that, choose Nook Color, and it will update to the newest version 3.2.0.1.
Hope this Helps!
What's the best way to update recovery on sdcard? Mod manager only updates the internal flash..
Barleyman said:
What's the best way to update recovery on sdcard? Mod manager only updates the internal flash..
Click to expand...
Click to collapse
I downloaded an updated version located HERE and extracted the files and attached them for you. Just download and unzip the files to your current CWM SD card.
Jimbo67 said:
Don't appologize for asking questions-we all need answers to one thing or another
The first thing you want to do is go to the android market and search for Rom Manager. You already have this installed if you are running CM7, but you need to update it to the newest version.
Then, Just open your app drawer and open up Rom Manager. When it opens, the very top line says "Flash Clockwork Mod Recovery". Tap on that, choose Nook Color, and it will update to the newest version 3.2.0.1.
Hope this Helps!
Click to expand...
Click to collapse
OT - That was a nice reply. generally people in this forum are VERY helpful but Kudos for saying it was ok to ask questions.
I am also a complete noob and am learning tons and tons and tons. As always, you guys rock!
GMPOWER said:
I downloaded an updated version located HERE and extracted the files and attached them for you. Just download and unzip the files to your current CWM SD card.
Click to expand...
Click to collapse
Ok, thanks! So you can indeed copy the files as-is.. with Paleolithic dos 3.2 origin, I tend to expect you need to use special app to copy the system files. In any case, I've installed the boot menu on SD card so by defaults I boot internal flash. No need to lose sanity removing the easy-to-lose usd card.. I can also start the recovery from internal flash..
Barleyman said:
Ok, thanks! So you can indeed copy the files as-is.. with Paleolithic dos 3.2 origin, I tend to expect you need to use special app to copy the system files. In any case, I've installed the boot menu on SD card so by defaults I boot internal flash. No need to lose sanity removing the easy-to-lose usd card.. I can also start the recovery from internal flash..
Click to expand...
Click to collapse
Yes, I have updated a couple times by just transferring the updated files onto my bootable CWM card. I have done a number of back-ups and restores without a problem. The files are self-contained file systems, so not much damage from a simple transferring of them. If you want to install a special app for windows to be able to update the SD card in the future, then I would download this very handy tool, ImDisk, it will allow windows to mount the updated img file and extract the files from it.
I have 4.3 ROM installed and i am S-On but Unlocked. I have TWRP installed and can't install any zips. I keep getting "Updating Partition Details". I put CWM on but the files I see on CWM aren't the files I see using a file explorer. Is there anyway to fix this?
Anybody?
XAviierG said:
I have 4.3 ROM installed and i am S-On but Unlocked. I have TWRP installed and can't install any zips. I keep getting "Updating Partition Details". I put CWM on but the files I see on CWM aren't the files I see using a file explorer. Is there anyway to fix this?
Click to expand...
Click to collapse
Could you please say if you are able to get into your OS?
And you said that you see with CWM other files than you see with a regual file explorer... You mean a file explorer in the OS like ES File Explorer?
I once had the same issue and was unable to flash any kind of zips.. So I decided to make a /data backup and then I flashed the ROM again, installed the /data backup and then I was again able to flash whatever I wanted to.. but unfortunately I was unable to determine the exact error. Maybe if you don't have to many patches on your OS it's worth the risk I think..
I'll bite... A bit of a kerfuffel upgrading from ARHD 51 to 52. But, I'd taken a backup of the 51 image and ported it to my laptop using the ROM Manager download server. However, when I try to restore the file (by installing the ZIP it created), it fails on me. Am I doing something wrong? There's no option in ROM Manager to restore the ZIP file. Anyone have this problem and knows how to resolve it?
And yes, I know this may not be the optimal place for this thread, but frankly I can't find a better place. Just looking for someone who may have an idea to help
TIA
diceman725 said:
I'll bite... A bit of a kerfuffel upgrading from ARHD 51 to 52. But, I'd taken a backup of the 51 image and ported it to my laptop using the ROM Manager download server. However, when I try to restore the file (by installing the ZIP it created), it fails on me. Am I doing something wrong? There's no option in ROM Manager to restore the ZIP file. Anyone have this problem and knows how to resolve it?
And yes, I know this may not be the optimal place for this thread, but frankly I can't find a better place. Just looking for someone who may have an idea to help
TIA
Click to expand...
Click to collapse
Well, you can just copy/paste the backup zip onto your pc. Re-transfer it to THE CORRECT DIRECTORY on the internal storage of the One. If you have, it will restore perfectly. I've tried a TWRP backup, that worked like a charm. NO reason why CWM would be different.
raghav kapur said:
Well, you can just copy/paste the backup zip onto your pc. Re-transfer it to THE CORRECT DIRECTORY on the internal storage of the One. If you have, it will restore perfectly. I've tried a TWRP backup, that worked like a charm. NO reason why CWM would be different.
Click to expand...
Click to collapse
Yea, tried that. I may have a corrupt ZIP or something like that. I'll play with it some more.
Thanks for response
Hey all,
Today is not my day...just not paying attention. I accidentally replaced my build.prop file with a modified version but forgot to change the permissions so now I am boot looping. I can still access TWRP, so I was curious if there is any way to get a new build.prop file onto the phone so I do not have to do a full wipe. Any help would be appreciated.
Also, if its possible to flash onto the phone, does anyone have the build.prop file I can use? Thanks in advance.
I guess I can also access the bootloader for fastboot, if that makes a difference. Thanks.
JustROLLIN said:
I guess I can also access the bootloader for fastboot, if that makes a difference. Thanks.
Click to expand...
Click to collapse
You can either use mfastboot to flash the entire system. IMG for the rom you are using (easiest). Or use adb from within recovery to fix permissions on the build.prop....
Good luck :good:
Edit: re flashing just system will not affect you data. Only any modifications made to /system. For instance: if you are using xposed, it will need to be reinstalled. All other apps will be unaffected.
samwathegreat said:
You can either use mfastboot to flash the entire system. IMG for the rom you are using (easiest). Or use adb from within recovery to fix permissions on the build.prop....
Good luck :good:
Edit: re flashing just system will not affect you data. Only any modifications made to /system. For instance: if you are using xposed, it will need to be reinstalled. All other apps will be unaffected.
Click to expand...
Click to collapse
Your idea spurred me to use a method I used the other day, from this thread:
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Worked great and saved all data, thank you!
Hi!
I have rooted my phone, and deleted bloatware using uninstall.
After reboot, the apps returned, so I deleted /system/apps/*.apk (relevant) files (I'd also like to know what are the *.odex files if someone can kindly tell me )
Then, I rebooted again, and again they were... I have read in previous threads that flashing the kernel is needed. Is that so? And if so, how can it be done?
Thanks!
barashe said:
Hi!
I have rooted my phone, and deleted bloatware using uninstall.
After reboot, the apps returned, so I deleted /system/apps/*.apk (relevant) files (Id also like to know what are the *.odex files if someone can kindly tell me )
Then, I rebooted again, and again they were... I have read in previous threads that flashing the kernel is needed. Is that so? And if so, how can it be done?
Thanks!
Click to expand...
Click to collapse
You need a custom kernel with /system write permission (unsecured kernel) .
You will not be able to install ota updates if you mess with /system files.
Thanks!
alray said:
You need a custom kernel with /system write permission (unsecured kernel) .
You will not be able to install ota updates if you mess with /system files.
Click to expand...
Click to collapse
Downloaded and installed ElementalX-m7 kernel and now they are all gone!
barashe said:
Downloaded and installed ElementalX-m7 kernel and now they are all gone!
Click to expand...
Click to collapse
for future reference, you can also stay on stock kernel (dont really know why ) and do the changes in custom recovery (eg TWRP)
if you want a relatively easy file manager for custom recovery, check out Aroma File Manager... that would save you the hassle of using an adb shell
oh, and if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title