Related
Like the title says, does damageless' sprintupdate2.zip have apps2sd enabled? I flashed it and all my apps appear to be installing on the device memory. What am I missing here? I wiped everything before flashing and partitioned my SD card.
I think sprintupdate2.zip was strictly the sprint update + root + busybox - some bloatware.
I wouldn't think he enabled apps2sd on it.
Kcarpenter said:
I think sprintupdate2.zip was strictly the sprint update + root + busybox - some bloatware.
I wouldn't think he enabled apps2sd on it.
Click to expand...
Click to collapse
Okay, follow up question: what's the best method for enabling apps2sd on Hero 2.1?
chapaj said:
Okay, follow up question: what's the best method for enabling apps2sd on Hero 2.1?
Click to expand...
Click to collapse
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Kcarpenter said:
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Click to expand...
Click to collapse
Bust open Damage 2.08.1 and grab his Boot.img and his a2sd script in /system/bin.....then put them in the ROM you are using.
Kcarpenter said:
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Click to expand...
Click to collapse
I've got the partitions ready to go. I just don't know how to pull the script. Does anyone have a guide on how to do this?
Konikub said:
Bust open Damage 2.08.1 and grab his Boot.img and his a2sd script in /system/bin.....then put them in the ROM you are using.
Click to expand...
Click to collapse
Okay, I've added those the sprintupdate2.zip that I'm using. I can then flash that over my existing ROM without wiping?
chapaj said:
Okay, I've added those the sprintupdate2.zip that I'm using. I can then flash that over my existing ROM without wiping?
Click to expand...
Click to collapse
Shouldn't hurt.
Kcarpenter said:
Shouldn't hurt.
Click to expand...
Click to collapse
That didn't work. I get:
E:Wrong digest:
boot.img
E:Verification failed
Installation aborted.
chapaj said:
That didn't work. I get:
E:Wrong digest:
boot.img
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
Did you resign the zip after you modified it?
use fresh kitchen or avabox
Kcarpenter said:
Did you resign the zip after you modified it?
use fresh kitchen or avabox
Click to expand...
Click to collapse
I had no idea i had to do that. I'm researching how to do that now. I don't suppose anyone could do it and throw up here as an attachment?
Post it up.
The first SprintUpdate that Damage released, I put the A2SD add-ons in it. If anyone wants me to do it again, let me know and I'll go do it.
EDIT: That was the SprintUpdate2 that I put the add-ons to. http://www.darktremor.info/files/2.1/sprintstock-21-a2sd-signed.zip
tkirton said:
The first SprintUpdate that Damage released, I put the A2SD add-ons in it. If anyone wants me to do it again, let me know and I'll go do it.
EDIT: That was the SprintUpdate2 that I put the add-ons to. http://www.darktremor.info/files/2.1/sprintstock-21-a2sd-signed.zip
Click to expand...
Click to collapse
I dl'd tkirktons darktremor and followed steps in his discussion thread posted above and worked perfectly. Thanks tkirkton!
Quick question. Can the New OC kernel be added to the damageless sprint leaked rom?
Thanks to anomalous3 over on the vibrant forum he was nice enough to port over his rom to our side based off of the new source code released by samsung
"If you feel like being a guinea pig, or know anyone who does, the deodexed build is here:
http://getyourboneon.com/CaptivateDeodexed.zip
Since I don't have a captivate I can't really test it, but it should work fine. It's based off that UCJH2 build. I didn't include any lag fixes since they've proliferated out of control, but I did include ext manipulation libraries and e2fsck to make life easier for people who want to use one of the lag fixes."
Please note I have NOT tested this rom yet, I don't have my captivate. Please somebody could test this and let us know if there's any problem so we can let him help us fix it.
Again, not responsible for whatever happens to your phone.
Here is the original thread I posted for reference.
http://forum.xda-developers.com/showthread.php?t=746466
EDIT: I'm going to assume you would install this like any other rom via update
EDIT2: anomalous3 has updated the link with corrections. Let us know how it works
Well... since I can't seem to get enough of abusing my phone, guess I'll give this a whirl =P
And I have JH2, So I suppose that makes me a good candidate
Zilch25 said:
Well... since I can't seem to get enough of abusing my phone, guess I'll give this a whirl =P
And I have JH2, So I suppose that makes me a good candidate
Click to expand...
Click to collapse
let us know how it goes
Do I just rename this to update.zip and go recovery and reinstall packages?
And when I try it and my phone crashes I'll blame Zilch because it's convenient.
Sent from my SAMSUNG-SGH-I897 using XDA App
Will do, flashing back to a stock JH2 while I download! I've been waiting for something like this
Clienterror said:
And when I try it and my phone crashes I'll blame Zilch because it's convenient.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It probably was my fault anyway =P
Wait a sec, what does deodexed mean? I looked it up and it means no oxded files, but i don't know what those files are...
damn it, wish this was around 2 hours ago when i was bored! its too late now to ruin my phone haha.. tomo sometime maybe i'll try..
Question...Do I have to install the stock Captivate ROM first as it states in the linked post? I have the stock ROM that is rooted with the AT&T bloatware removed. The only other mod is the lagfix version 2.3...Can I just flash this over that?
you should be able to, according to his original thread on the vibrant forums, the directions were to put on internal sd card and load via clockwork best method. or via recovery mode works too
nammyczc said:
you should be able to, according to his original thread on the vibrant forums, the directions were to put on internal sd card and load via clockwork best method. or via recovery mode works too
Click to expand...
Click to collapse
That's what's taking me so long... seems like JH2 is having some issues with update.zips... namely it's getting to the "Opening installer" then "Install Aborted". The(not new) update.zip for root still works, so I'm tossing on clockwork to see if I can get this thing crammed on here with that.
Installing from Clockwork:
Hoses up during the copying files stage
E:Can't symlink /system/bin/bugreport
E:Failure at line 5:
symlink dumpstate SYSTEM:bin/bugreport
Then install aborts
Zilch25 said:
Installing from Clockwork:
Hoses up during the copying files stage
E:Can't symlink /system/bin/bugreport
E:Failure at line 5:
symlink dumpstate SYSTEM:bin/bugreport
Then install aborts
Click to expand...
Click to collapse
That's because the capitvate uses a different independent bugreport that is not a symlink of dumpstate.
Simply edit the update script in the meta folder and remove that line.
I deodexed the actual captivate files the other day, just havnt tested/posted them, way too busy with school
BuglessPete said:
That's because the capitvate uses a different independent bugreport that is not a symlink of dumpstate.
Simply edit the update script in the meta folder and remove that line.
I deodexed the actual captivate files the other day, just havnt tested/posted them, way too busy with school
Click to expand...
Click to collapse
I'll pm him about this
nammyczc said:
I'll pm him about this
Click to expand...
Click to collapse
Also ask him why superuser.apk is in the xbin folder.
vietphunguyen said:
Wait a sec, what does deodexed mean? I looked it up and it means no oxded files, but i don't know what those files are...
Click to expand...
Click to collapse
-From googling, found on XDA:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
golemaw said:
-From googling, found on XDA:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
This is correct. Deodexed ROMs can be themed...
BuglessPete said:
Also ask him why superuser.apk is in the xbin folder.
Click to expand...
Click to collapse
Good catch on that one Yeah, it surprised me that a lot of the stuff in the captivate doesn't rely on toolbox either. I might even port that over to the Vibrant since I think that toolbox is a stupid vestigial substitute for busybox anyways. Link updated, let me know if it works.
anomalous3 said:
Good catch on that one Yeah, it surprised me that a lot of the stuff in the captivate doesn't rely on toolbox either. I might even port that over to the Vibrant since I think that toolbox is a stupid vestigial substitute for busybox anyways. Link updated, let me know if it works.
Click to expand...
Click to collapse
updated original post with info
Does anyone know how to get Clockwork Recovery on the Xoom so I can flash .zip's? And make nandroid backups. Thx in advance.
Koush is not going to release it until the sdcard works. Making backups to the internal memory is pointless and flashing from internal memory to internal memory is not a great solution at the moment.
-Bauxite
Sent from my Evo 4G
Damn....while agree that making a backup to the internal memory is pointless I just wanted to flash a .zip so that I can get a live wallpaper working. But thanks for the answer.
Sent from my Xoom using XDA App
you dont need to use 'install' zip to install things in the zip, generally flashing zips just cp src dst... take apart the zip, find the updater-script and see if you can just do those steps manually via adb shell (or adb hell if you're feeling evil)
backup to nfs share? smb share? .. would be even nicer
cifs/nfs backup sounds like a project... time to checkout the cwm source!
removed. I had incorrect information.
youngproguru said:
Koush's website indicates that it is now possible to install Zip's directly from ROM manager without having the recovery installed. I'm not sure if this appies to Xoom, however I dont see why not (if you are rooted)
ROM manager does "run: on Xoom.
Check it out:
http://www.koushikdutta.com/2011/01/rom-manager-any-recovery.html
Click to expand...
Click to collapse
This is taken a bit out of context I believe. Koush was stating that you no longer need CWM to do the flashes. He's implemented code that will allow ROM Manager to reboot into other custom recovery mods to do the flashing. At this point though, you still need the recovery mod developer to enable the functionality.
Yep, I think you are correct.
DISCLAIMER: These scripts have worked for me without issue. It would behoove you to ensure you have a solid back up to recover from in the event that something goes horribly wrong. These scripts should be considered a WIP. I will edit them and provide information as needed if something does not work as it should. Please feel free to post here or PM me if you have issues and bear with me if they do not work properly for you. END DISCLAIMER
To be honest, I am lazy. I flash CM nightlies and sometimes themes, and I didn't like having to navigate through recovery over and over again to wipe cache and dalvik-cache. So, I decided to write a script that would just do it for me. Then I got even lazier. I found that I had written several scripts and now I was tired of having to flash them all in a certain order. Which is why I wrote one all inclusive script.
Here I will provide you with two separate scripts. The first does just enough and the second does that much and a few more personal tweaks.
The first script is a rather simple one. It formats your /cache partition and deletes /data/dalvik-cache.
Wipe_Cache_Dalvik.zip
Edify version to work with Clockword Mod Recovery
1. Back up your current rom
2. Flash Wipe_Cache_Dalvik.zip
3. Flash your nightly/theme of choice
4. Reboot
The second script is where my personal preferences come into play. This script is meant to be flashed after you install your nightly rom. This script will format /cache, delete /data/davlik-cache, delete certain system apps that I do not personally use, and then copy an edited build.prop into /system so that the DPI is set to 190 immediately after you reboot from installing the nightly rom. This script will more than likely have to be changed to suit your needs. I understand that people will want different DPI settings and would like to retain the use of apps that I do not use.
Wipe_Delete_Copy.zip
1. Edit the script if you so choose. (Directions will be given in the second post)
2. Back up your current rom
3. Flash your nightly
4. Flash Wipe_Delete_Copy.zip
5. Reboot
Many thanks to Omegasun and his BareBone App and Sense Removal Plus Community Tools Thread.
This was the thread that got me started writing scripts. I learned a lot from him. My script would not have been possibl without his.
Many thanks to unCoRrUpTeD and his unCoRrUpTeD Dual Boot V1 Thread. I did a lot of testing for unCoRrUpTeD on his dualboot setup. I learned a lot from him in regard to using updater-scripts and updater-binaries. Without him I would not have been able to write the second script.
A thank you also to Calkulin for his format_all.zip which was another source of inspiration for the first wipe script.
As always a giant thanks to Cyanogen, Team Douche, TeamWin, and the Snap Team. The information and aid that they have provided to me is second to none. Without them I wouldn't know half of what I do now. Their contributions are what make this community great.
Any gratitude that you may feel towards me for these scripts should be directed towards those mentioned above. I wrote these to benefit myself and now feel that I should give them back to you all. I hope they work as described and make flashing a little bit easier on you.
These are rudimentary directions for the time being. I will edit and make them more precise later tonight. Also included a few things for reference. Like I said, it is basic info for now and it will become more detailed and informative.
You will need a text editor to edit any of these scripts. I primarily use Notepad++ on Windows. If you are on a *nix box then I am sure you are more than able to find a text editor that suits your needs.
1. Unzip Wipe_Delete_Copy.zip
2. Navigate to *\META-INF\com\google\android\
3. You will see two files: updater-script and update-binary
4. Open updater-script with your favorite text editor. (In my case, I right click and choose "Edit with Notepad++")
5. Edit Away
6. Save
7. Rezip
For reference, these are the files deleted from /system/app:
ADW Launcher
Browser
Car Home Google
CM Wallpapers
Development
DSP Manager
Email
FM
File Manager
Google Quick Search Box
Genie Widget (News and Weather)
Live Wallpapers
Live Wallpaper Picker
Pro Tips (The CM Widget that appears after a clean install)
Sound Recorder
VoiceDialer
Notice "ADW Launcher." This means you will need Launcher Pro/ADW EX/etc before you flash this. Or you will need to remove this line from the script.
If you don't want to change your DPI settings:
1. Open up the script in your text editor
2. Delete
Code:
ui_print("");
ui_print("");
ui_print("");
ui_print("Copying build.prop to retain proper dpi");
show_progress(0.200000, 5);
package_extract_dir("system", "/system");
3. Save
4. Delete the "system" folder found in the original zip
5. Rezip
This will be very handy. Thank you, sir.
+1 for this when I get to mess around with it after work tomorrow. Great job
swyped from my cyanogenized and gingerbreaded EVO
i have been thinking about making a cache/dalvik wipe script forever, but never got the will. thanks for making my life easier karadore.
I appreciate the thanks. I know the basic script will work just fine. It is very straight forward. The second one is kind of tricky because it uses an updater/binary. I just recently started working with them and had a few issues to begin with. The more feedback you all give me on this the better. Hope they help.
i dont know how to write in edify, but i would like to. if you dont mind whipping up a little tutorial, that would be fantastic so all the peoplez can stop complaining that they get an error after flashing my zips on cwm 3+. it would help me and a lot of others as well.
dkdude36 said:
i dont know how to write in edify, but i would like to. if you dont mind whipping up a little tutorial, that would be fantastic so all the peoplez can stop complaining that they get an error after flashing my zips on cwm 3+. it would help me and a lot of others as well.
Click to expand...
Click to collapse
I may just do that. Would give me a nice little project in the next few days to help me procrastinate from school and work a little more
Anyway to update these to work on CW 3+ recoveries?
sminker said:
Anyway to update these to work on CW 3+ recoveries?
Click to expand...
Click to collapse
The second script should work because it is written in edify. I will update the first one so that it works. Leaving for work now but I should be able to do it all from my phone. Will post up the new version in a few.
sminker said:
Anyway to update these to work on CW 3+ recoveries?
Click to expand...
Click to collapse
Just did a quick edit from my phone. This new zip should work on all CW Recoveries. Let me know if there are more issues. Will update the op once I am off work.
http://db.tt/sBi95OV
Karadorde said:
Just did a quick edit from my phone. This new zip should work on all CW Recoveries. Let me know if there are more issues. Will update the op once I am off work.
http://db.tt/sBi95OV
Click to expand...
Click to collapse
Awesome. Haven't tested yet but thanks for updating.
All I ask is that you let me know if it works or not. No reason why it shouldn't, but the more R&D the better.
are you still planning on giving an edify tutorial? and if not do you have any helpful pages or just all-telling .zips i can look at? thanks a bunch karadorde
Wait you flash first and then wipe caches? I've always done it the other way around. Does it even matter? Guess not...
Sent from my PC36100 using XDA App
matt2053 said:
Wait you flash first and then wipe caches? I've always done it the other way around. Does it even matter? Guess not...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You can do it either way. I always used to wipe and then flash.
The reason I am wiping after flashing the nightly is because of the other code in the second script. The second script deletes all of those system apps that I don't use and copies my edited build.prop back into /system. If I flashed the script before the nightly, then those system apps would be reinstalled and I would lose my edited build.prop.
dkdude36 said:
are you still planning on giving an edify tutorial? and if not do you have any helpful pages or just all-telling .zips i can look at? thanks a bunch karadorde
Click to expand...
Click to collapse
I have started putting together the thread. I will be adding to it today. I will dig up some other threads for you as well. Here is a link to the one I just started in Evo General.
http://forum.xda-developers.com/showthread.php?t=994940
nice work.. definitely helps me with flashing nightlies.. i would always have to go and remove most of that stuff.. the only thing i wanted to keep was DSP so i went and simply edited script..
works.
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery