Related
I like Fresh rom, and Cyanogen. I have only been rooted for a few days.
However, I would like to customize these roms even further.
First, is this frowned upon? Messing with other peoples roms for my personal use?
Second, is there a process I need to follow, or can I just simply delete .apks from the file before I copy it to my SD card then flash to my phone?
I did do a search, and found people saying to unzip, delete .apk's, then re-zip... And other people said unzip, delete, sign, then re-zip...
I'm lost... sorry for being such a noob.
Thanks. Even the littlest help is greatly appreciated.
You can delete apk's from a ROM before flashing and nobody is gonna give you trouble for personalizing their ROM for your personal use. Just be sure that if you're going to release your work to others, you ask the original developer first and give proper credits.
When removing apk's from a ROM before flashing, be sure you know what you're removing, and that it wont cause issues for you. I would recommend flashing the complete ROM and removing apk's one at a time until you are familiar with what does what and what may cause boot issues and/or battery drain. If you remove a bunch of stuff before you flash it, and it boot loops, it may be hard to tell what exaclty the problem was caused by. So, start small and build up to fully customizing, you'll be in the kitchen in no time.
Myself, I use 7zip for opening zips without having to unpack them. So, get 7zip installed on ur cpu. Then right click on the zipped ROM, drag over 7zip and pick open archive. You will now be inside and can modify to your hearts content. Add, remove, swap out, whatever you want. When your done, just close out and the changes are saved. Flash away.
I always make some changes to the build.prop file in /system for reference. such as changing the ro.build.description to something else, so I know which modded version it is. This is what is seen under menu > settings > about phone > software information > build number on ur phone. To edit the build.prop, you will first have to copy it out of 7zip and edit it with word pad or something, then copy it back in. There's lots of fun to have, so go for it! Lots of people here to help if you run into trouble.
Lots of good info above (thanks for the tip on ro.build.description, have to try that now ), but I always resign if I add or remove files.
Sent from my blah blah blah blah
fachadick said:
Lots of good info above (thanks for the tip on ro.build.description, have to try that now ), but I always resign if I add or remove files.
Sent from my blah blah blah blah
Click to expand...
Click to collapse
Yeah, I've gotten lazy ever since going to Eng HBOOT .76 and Amon RA 1.8, no more signature required to flash anything. Not sure if thats always a good thing
Although, you do still have to re-sign non system and market apk's if you want them to install.
JTNiggle said:
Yeah, I've gotten lazy ever since going to Eng HBOOT .76 and Amon RA 1.8, no more signature required to flash anything. Not sure if thats always a good thing
Although, you do still have to re-sign non system and market apk's if you want them to install.
Click to expand...
Click to collapse
Wow thank you for all that info! It's extremely helpful! I feel confident enough to start playing with roms now
Thanks again!
Sent from my HTC Evo 4G.
Welcome,
I've compiled ClockWorkMod 3.0.1.4 and I made some changes to it, copying BlaY0's work for the HTC Legend.
Changes:
Removed menu entries for updating via /sdcard/update.zip
[*]Stripped some "No" line entries from confirmation menus (only 1 left)
[*]Removed some insane size values from partitioning list
[*]Recovery is closed using pkill instead of ps and grep
Installation
Code:
Copy the desired update.zip to your sdcard and apply it from ClockWorkMod
Extras:
Install noconfirm to remove the "no" lines. Works on all clockworkmod-based recoveries.
Thanks to BlaY0, Cyanogen and Koush
Thanks. Thanks a ton! You actually addressed what annoyed me most with this recovery. I have to admit, I do miss RA on the Vision...
But no complaining here, thanks for your work!
Edit: Ugh, I don't get it with the .no_confirm file. Put it where...?
Going to try this, sounds good =))
Sent from my HTC Vision using Tapatalk
Aha i just moved this in clockwork recoveries files then i just renamed the rec.img with the recovery of the g2 then flash it...
Sent from my HTC Vision using Tapatalk
So this still has the fix for power off while charging? And just the menu for sdcard update has been removed that can be noticed other than that, the other two updates to it is file size or so??
Sent from my HTC Vision using Tapatalk
noodles2224 said:
So this still has the fix for power off while charging? And just the menu for sdcard update has been removed that can be noticed other than that, the other two updates to it is file size or so??
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
It still powers on when charging
And he did remove the other "NO" from the list, so now it's a lot easier
Hey hey! I like what you've done with the source file. I was using your recovery while in the process of making a backup and thought it was pretty neat because I couldn't for the life of me figure out where and what to edit in source since nothing is commented out by anyone. I can read the code but have a difficult time tracing it through. I'm still newbie with the C++
But anyways, while backing up, I was reminded of how annoying it is to backup the system, data, cache, sd-ext, boot, and etc folders into img files for every backup of CM7 when the only thing that really needs to be backed up is the data folder to data.img which contains all the userdata, settings and applications downloaded from the market. The only exception would be if I had changed keymap files, changed stuff inside /system/app/ folder, or any other folder/files other than data since the previous backup of the same rom.
So, if I was to make ONE backup of CM7 Tuesday morning, and wanted to make a backup of the very same rom later on in the day (containing more recent apps, emails, settings, etc. ) I would have to delete the old backup already saved and start the backup process over again from the beginning, or I would have to keep making duplicates of the same backup that differs only by the data.img file, wasting precious space on a baby **** sized microsd. IMO it completely ruins the purpose of the automatic backup feature of Rom Manager since I have to remind myself to delete the previous backup everyday. However, I do think it'll be useful if clockworkmod can be modified.
SO, I was wondering, where should I be looking in the source to add an option such as "backup data only",
that when selected,
1.) Looks for an extra line in the md5sum file for every folder in /sdcard/clockworkmod/backup/ that specifies the android version (cm7, cm6, date, w/e)
2.) Compares extra line with what it's about to back up (via contents of /system/build.prop ) and
3.) if they match up
calls only the function that backs up the data folder excluding calls for the backup of system, cache, boot, etc.
Sorry, if its confusing how I've explained it. Its quite late here in soFla, and I didn't get no sleep 8(
But I'm sure you get what I mean considering that you know some code. That's a very rough pseudo-code I guess.
Another method that probably is a lot easier, if possible, would be to figure out what command/message Rom-Manager leaves behind for clockworkmod before rebooting to clockworkmod. If it is a small script like I hope it is, backing up only data.img would be a heck of a lot easier since I'm pretty sure the source has an individual definition call for backup for each partition.
so how do i fix this powering on issue.. its starting to piss me off -.- lol,. least how to fix it on stock recovery.
CaliBoyPhillip said:
so how do i fix this powering on issue.. its starting to piss me off -.- lol,. least how to fix it on stock recovery.
Click to expand...
Click to collapse
I think this issue is caused by the hardware on the desire z and thus is unfixable. If you press power off from the menu will it just power on again? Because then the entry should be renamed to reboot recovery.
thrice43 said:
Hey hey! I like what you've done with the source file. I was using your recovery while in the process of making a backup and thought it was pretty neat because I couldn't for the life of me figure out where and what to edit in source since nothing is commented out by anyone. I can read the code but have a difficult time tracing it through. I'm still newbie with the C++
But anyways, while backing up, I was reminded of how annoying it is to backup the system, data, cache, sd-ext, boot, and etc folders into img files for every backup of CM7 when the only thing that really needs to be backed up is the data folder to data.img which contains all the userdata, settings and applications downloaded from the market. The only exception would be if I had changed keymap files, changed stuff inside /system/app/ folder, or any other folder/files other than data since the previous backup of the same rom.
So, if I was to make ONE backup of CM7 Tuesday morning, and wanted to make a backup of the very same rom later on in the day (containing more recent apps, emails, settings, etc. ) I would have to delete the old backup already saved and start the backup process over again from the beginning, or I would have to keep making duplicates of the same backup that differs only by the data.img file, wasting precious space on a baby **** sized microsd. IMO it completely ruins the purpose of the automatic backup feature of Rom Manager since I have to remind myself to delete the previous backup everyday. However, I do think it'll be useful if clockworkmod can be modified.
SO, I was wondering, where should I be looking in the source to add an option such as "backup data only",
that when selected,
1.) Looks for an extra line in the md5sum file for every folder in /sdcard/clockworkmod/backup/ that specifies the android version (cm7, cm6, date, w/e)
2.) Compares extra line with what it's about to back up (via contents of /system/build.prop ) and
3.) if they match up
calls only the function that backs up the data folder excluding calls for the backup of system, cache, boot, etc.
Sorry, if its confusing how I've explained it. Its quite late here in soFla, and I didn't get no sleep 8(
But I'm sure you get what I mean considering that you know some code. That's a very rough pseudo-code I guess.
Another method that probably is a lot easier, if possible, would be to figure out what command/message Rom-Manager leaves behind for clockworkmod before rebooting to clockworkmod. If it is a small script like I hope it is, backing up only data.img would be a heck of a lot easier since I'm pretty sure the source has an individual definition call for backup for each partition.
Click to expand...
Click to collapse
I understand the issue. I do have an idea for you which I will work on later today. It's an update.zip with a script in it which will yaffs up the data partition and put the data.img into /sdcard/clockworkmod/backup/*foldername*/
Next is should take the md5sum and write it to md5sums.txt
Like this you can restore your backup. I can cook you a custom recovery which has added update from /sdcard/update.zip baked in, but changed to /sdcard/clockworkmod/backupdata.zip
I know this isn't the easiest way to do it, but it is the easiest to code for me, so I'll use it untill I expand my knowledge
schaggo said:
Thanks. Thanks a ton! You actually addressed what annoyed me most with this recovery. I have to admit, I do miss RA on the Vision...
But no complaining here, thanks for your work!
Edit: Ugh, I don't get it with the .no_confirm file. Put it where...?
Click to expand...
Click to collapse
Ah how stupid of me, it should go in sdcard/clockworkmod/
I'll confirm and update the first post, thanks for pointing it out
Mikevhl said:
I think this issue is caused by the hardware on the desire z and thus is unfixable. If you press power off from the menu will it just power on again? Because then the entry should be renamed to reboot recovery.
Click to expand...
Click to collapse
Yeah, it happens regardless If i plug in my charge and pull of battery and back in or pull out battery and put back in and plug charger haha... same with power menu ugh... =( I'm on a T-Mobile USA G2 if that helps but its pretty much a DZ
CaliBoyPhillip said:
Yeah, it happens regardless If i plug in my charge and pull of battery and back in or pull out battery and put back in and plug charger haha... same with power menu ugh... =( I'm on a T-Mobile USA G2 if that helps but its pretty much a DZ
Click to expand...
Click to collapse
Nah I'm on a Desire Z so it's the same. Since this does not happen on other devices, the problem isn't caused by clockworkmod. The bootloader is just coded to boot into recovery when AC plugs in. I don't know if this happen the stock recovery as well. It could be caused by gfree, but also it could just be that the stock recovery forces the system to be shut down. Whatever it is, we won't be able to fix it..
Mikevhl said:
I understand the issue. I do have an idea for you which I will work on later today. It's an update.zip with a script in it which will yaffs up the data partition and put the data.img into /sdcard/clockworkmod/backup/*foldername*/
Next is should take the md5sum and write it to md5sums.txt
Like this you can restore your backup. I can cook you a custom recovery which has added update from /sdcard/update.zip baked in, but changed to /sdcard/clockworkmod/backupdata.zip
I know this isn't the easiest way to do it, but it is the easiest to code for me, so I'll use it untill I expand my knowledge
Click to expand...
Click to collapse
Damn... Why are you so OG? I would appreciate that so much. How many source files were actually modified from the original clockworkmod source? If its not many, would you mind commenting out some important bits of code so I can pick up from somewhere when looking through the code and have a better understanding of the basic/general algorithm used by the original dev? Its cool if you don't though lol. I still appreciate what you've already put together.
thrice43 said:
Damn... Why are you so OG? I would appreciate that so much. How many source files were actually modified from the original clockworkmod source? If its not many, would you mind commenting out some important bits of code so I can pick up from somewhere when looking through the code and have a better understanding of the basic/general algorithm used by the original dev? Its cool if you don't though lol. I still appreciate what you've already put together.
Click to expand...
Click to collapse
Do you mean the things that I've removed and added? If you take a look at the sources you will aee that there is a line on which the modification takes place, next a + or - which indicates if the line was added or removed. Is that what you mean?
Mikevhl said:
Do you mean the things that I've removed and added? If you take a look at the sources you will aee that there is a line on which the modification takes place, next a + or - which indicates if the line was added or removed. Is that what you mean?
Click to expand...
Click to collapse
Whoops yes I understand the layout now. sorry. I was curious as to where, and which file to begin looking to unstand customizing cwm
Mikevhl said:
Nah I'm on a Desire Z so it's the same. Since this does not happen on other devices, the problem isn't caused by clockworkmod. The bootloader is just coded to boot into recovery when AC plugs in. I don't know if this happen the stock recovery as well. It could be caused by gfree, but also it could just be that the stock recovery forces the system to be shut down. Whatever it is, we won't be able to fix it..
Click to expand...
Click to collapse
actually, it DOES happen on other devices, and it IS a clockwork issue that, to my knowledge, Koush is aware of and is looking to fix. Before I came to the g2, I had a red mytouch 4g which, when rooted and CWM was installed, would boot into recovery from a powered down state when it connected to the charger. The explanation I heard back then was that the stock recovery for the phone would boot up upon connecting to a charger while off, but that it would somehow keep the screen off. however, when the recovery is replaced with CWM, it still exhibits this behavior, but it does not keep the screen off.
Just an fyi, though, in the mexDroid forum OP, there is a modded version of CWM which, when installed, will keep the phone off while charging. I have personally verified that it works (now if only someone would find a way to have android start up and shut down at preset times, like to have an alarm go off.. that would be awesome).
Would it be safe to assume that this'll also work on my galaxy tab?
Sent from my GT-P1000 using XDA Premium App
JasonTCelum said:
Would it be safe to assume that this'll also work on my galaxy tab?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
no, that's a bit of a stretch, as each recovery is made for the device that uses it, not device-agnostic. However, if you would like to try it out and dont mind taking the risk, you never know, you could get lucky.
mt4g?
Currently loving this on my G2 is there any chance of it becoming compatible for the mytouch 4G?
Ill be the Guinea!
so i have the bell pay as you go edition of the gio
and when i got it, i just uninstalled as much crap as i could
one of those happen to be 'Talk', which i now discovered is google talk (thought the app was called gtalk)
uninstalling it makes it disappear forever and you cannot find it in the market
in addition to that, i uninstalled whatever app/service needed to run live wallpapers
so if someone could rip/backup those apps and upload it here, many thanks
(i tried installing the talk apk on it's own, and the talk service apks, it does not like me install for some reason)
last question is,
any 5660m users got adobe flash running, i tried the stand alone armv6 apk, installed it, and does nothing
the other flash apk with loading the lib files into the root dir, i have not tried, if i can get the standalone apk working, i'd rather do that
any other tips for the 5660m would be great
thanks
edit - see post #9 (need help with stock browser)
Promise you'll back things up the next time?
Look at my stock rooted ROM for the files you shouldn't have deleted. You should be able to read (not write, at least not in a way the phone can handle) the RFS partitions with MagicISO among others. (Basically any program capable of handling FAT partition images.)
ADB push back the files into place, make sure their permissions are correct.
Can't help you for Flash, I've never tried it myself and my Gio is out of order for the time being.
For flash you need root and push LIB files to /data/data/com.adobeflash***/lib ant set permissions
Sent from my GT-S5660 using Tapatalk
Darkshado said:
Promise you'll back things up the next time?
Look at my stock rooted ROM for the files you shouldn't have deleted. You should be able to read (not write, at least not in a way the phone can handle) the RFS partitions with MagicISO among others. (Basically any program capable of handling FAT partition images.)
ADB push back the files into place, make sure their permissions are correct.
Can't help you for Flash, I've never tried it myself and my Gio is out of order for the time being.
Click to expand...
Click to collapse
so this is something i cant just grab someone's titaniumbackup files and install?
That too, if you have another rooted Gio at your disposal. I answered based the info I got.
ya, sorry, that's sorta what i meant in the first post,
i was actually asking for someone's to backup the gtalk/talk service/app and the live wallpaper service/app with titanium backup and upload it
if someone could do that for me, much appreciated
Try this and let me know if it works.
View attachment TitaniumBackup.rar
thanks, that did the trick
additionally i want to ask:
is the reason 5660m incompatible with most of the custom roms is the slight difference in hardware?
if i were to change microsd card, is a drag and drop to the new card sufficient or are there hidden/protected files that cannot be copied
lastly,
if i were to update the rom/install custom rom, is there any way to back up settings and apps or would i have to do stuff all over again?
gonna bump this again,
I need the stock browser this time, if someone would kindly back up from titanium backup
i'm just testing some compatibilities on certain websites
anonxlg said:
gonna bump this again,
I need the stock browser this time, if someone would kindly back up from titanium backup
i'm just testing some compatibilities on certain websites
Click to expand...
Click to collapse
Enjoy.
FusiveR said:
Enjoy.
Click to expand...
Click to collapse
finally got around, i tried installing it, doesnt work
it starts installing, then resets and browser does not appear in app list
tried both app and app+data
anonxlg said:
thanks, that did the trick
additionally i want to ask:
is the reason 5660m incompatible with most of the custom roms is the slight difference in hardware?
if i were to change microsd card, is a drag and drop to the new card sufficient or are there hidden/protected files that cannot be copied
lastly,
if i were to update the rom/install custom rom, is there any way to back up settings and apps or would i have to do stuff all over again?
Click to expand...
Click to collapse
Only the roms flashed from Odin usually aren't compatible with our phone anything else such as CM7.1, CM7.2, CM9, and all the other roms able to be flashed from
Recovery mode are mostly compatible with our version of gio hope I helped
Sent from my GT-S5660M using xda premium
What isn't compatible are the baseband and the bootloaders.
As long as an Odin-flashable ROM contains only system and boot.img you're in the clear. This is mostly a problem with early Europe/Asia 5660 ROMs.
Drag and dropping your files to the new SD card should do the trick. Hidden files and folders for Android (and Linux) have a dot at the beginning of their name, e.g.: /.android_secure/ and by default there shouldn't be any files with the FAT32 "hidden" attribute set on the SD card. The settings of your Windows Explorer will influence whether or not the latter copy over or not.
Backing up your applications and their settings can be done by applications like Titanium Backup. Most should transfer well from one ROM "family" to another. (As in: from stock to CM7, or CM7 to CM9, or CM9 to stock...) Your mileage will vary if you try to transfer system apps, or system settings.
so why do you (have to?) use odin, i thought there is CWM for gio, isnt that better than odin?
and still looking for a titanium backup of stock browser
maybe i should just install the ics rc
anonxlg said:
thanks, that did the trick
additionally i want to ask:
is the reason 5660m incompatible with most of the custom roms is the slight difference in hardware?
if i were to change microsd card, is a drag and drop to the new card sufficient or are there hidden/protected files that cannot be copied
lastly,
if i were to update the rom/install custom rom, is there any way to back up settings and apps or would i have to do stuff all over again?
Click to expand...
Click to collapse
I dunno what you are talking about, My canadian Gt-S5660M runs all custom firmwares, kernels, scripts etc just fine.
Odin and CWM are different and each serves their purpose.
Odin works with the lower level Download Mode, and can recover from situations CWM can't. It is also the usual way to install CWM in the first place. (You could also do it with a clever dd command on a rooted phone.) It is however cloakware, undocumented, difficult to install, buggy at times and just quirky overall.
CWM is more stable, doesn't require a computer to run, and is generally much safer to use.
AlwaysDroid: If you look at very early posts about the 5660M, many users encountered major issues after flashing European 5660 ROMs. Screen brightness all over the place and no network connection.
The problem was that those ROMs were Odin flashable "One Package" files that contained bootloaders and radio images as well. Those files were required for users upgrading from Froyo to Gingerbread, as stock Gio 5660s were also sold with 2.2 unlike the 5660M.
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
0Capita said:
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
Click to expand...
Click to collapse
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
BWolf56 said:
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
Click to expand...
Click to collapse
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
0Capita said:
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
Click to expand...
Click to collapse
That's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
B said:
Wolf56;371questions it's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
Click to expand...
Click to collapse
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
0Capita said:
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
Click to expand...
Click to collapse
Yes, that's the whole point of the cwm update. Now to flash it!
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
BWolf56 said:
Yes, that's the whole point of the cwm update. Now to flash it!
Click to expand...
Click to collapse
Well here's my latest problem... I tried to update CWM with an .img however when I tried to run it in the terminal it said there was not enough space... I don't know what to do... there is definitely a couple gigs free so I don't know what is wrong...
mrhaley30705 said:
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
Click to expand...
Click to collapse
the cm nightly thread? So theres a zip that would make 4.2 go back to 4.1?
Okay update:
I managed to flash update the new version of CWM... still can't use backup... I get a /system fail
It doesn't downgrade you're ROM. It fixes the 0 folder issue
mrhaley30705 said:
It doesn't downgrade you're ROM. It fixes the 0 folder issue
Click to expand...
Click to collapse
Ugh Okay I've given up... I dont know what else to try. Now that I've updated my CWM I cant flash the old CM10 because it reads it as a 4.1 and uncompatable... FML.
Can anyone point me to where I can find the Odin stock factory? I guess I'll just start from scratch...
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Helloworld294 said:
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
OOOMMMMMGggg ahhhhhh, that would have been so helpful but I've already started to factory reset it. Thanks though!
ahhhhhhhhh
Forget cwm it sucks use twrp and be done with all the problems
Sent from the scary door....
Basically what the title says. I was changing boot animations and when I went to undo my changes, something went askew and so now the sprint boot animation wont work. I had to rename the regular one to make android think it was the sprint one just so I could power off. Also, all of the sound files don't work. So yeah. I need an unmodified copy of /system/media/. Ive tried getting it from a stock rom but that went nowhere fast.
Honestly I can not thank you enough. I especially appreciate that you used Dropbox specifically. My phone wasn't mounting to my computer for whatever reason and I had my Dropbox signed in in ES Explorer. Again, thank you.