-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root CWM Recovery v6.0.1.2 Beta for the Triumph
- Thread starter BSydz
- Start date
-
- Tags
- motorola triumph
jamesd1085
Well-Known Member
I have tried restoring a few different roms using this recovery. I only had success with cm7...wouldnt restore any of my froyo or ics roms.
b_randon14
Android Expert
Hey bsydz, does the sharp roms mount everything as ext3? Or ext4? Because it don't make any sense why auto wouldn't work on the sharp roms. So will it just nor mount any partition or what?
I have for the recovery to backup and restore the /hidden and /hidden/data partitions and I'm working on the mobile vfat boot partition so that a nandrois backup will truely back everything needed up.
I am also going to look into USB mass storage and adb as well.
Right now I have it use auto on system data and cache, ext3 on hidden hidden/data and sd-ext, the latter because u believe having sd-ext as auto was causing issues while using app2sd after the recovery mounted or unmounted the sd-ext partition, on the next boor it couldn't mount /sd-ext causing you to loose data but after another reboot it mounted fine. Dogging through the logs I found that it detected it as an unknown filesystem. So by specifying ext3 on sd-ext, which is what cwm partitions it as ans what cm mounts it as, I hope it will solve the issue for those app2sd users.
As for the sharp roms, I personally have never flashed one or tried to back it up but I want to get a recovery that works right all.across the board and has everything working right. For now I am at a loss as to the sharp rom backup issues. Once I get the mobile partition backing up and restoring, I will start posting test builds for people to test out and report issues then we can try to get this thing working right!
And on a side note, I'm working on a fully working TWRP v2.3 recovery as well. As of now it works pretty good there are just things I need to iron our before I start posting test builds of it.
Once I get these recoveries down I'm gonna create a new thread and encourage everyone to use these instead of some of the more outdated ones to make everything more user friendly and less confusing for new comers and seasoned vets alike!!
I have for the recovery to backup and restore the /hidden and /hidden/data partitions and I'm working on the mobile vfat boot partition so that a nandrois backup will truely back everything needed up.
I am also going to look into USB mass storage and adb as well.
Right now I have it use auto on system data and cache, ext3 on hidden hidden/data and sd-ext, the latter because u believe having sd-ext as auto was causing issues while using app2sd after the recovery mounted or unmounted the sd-ext partition, on the next boor it couldn't mount /sd-ext causing you to loose data but after another reboot it mounted fine. Dogging through the logs I found that it detected it as an unknown filesystem. So by specifying ext3 on sd-ext, which is what cwm partitions it as ans what cm mounts it as, I hope it will solve the issue for those app2sd users.
As for the sharp roms, I personally have never flashed one or tried to back it up but I want to get a recovery that works right all.across the board and has everything working right. For now I am at a loss as to the sharp rom backup issues. Once I get the mobile partition backing up and restoring, I will start posting test builds for people to test out and report issues then we can try to get this thing working right!
And on a side note, I'm working on a fully working TWRP v2.3 recovery as well. As of now it works pretty good there are just things I need to iron our before I start posting test builds of it.
Once I get these recoveries down I'm gonna create a new thread and encourage everyone to use these instead of some of the more outdated ones to make everything more user friendly and less confusing for new comers and seasoned vets alike!!
This is still being worked on, I haven't had a lot of time lately. I am not sure about the mounting issue yet. By any chance do you remember which version it was? This should restore any older backups, and if the system is ext3 by default then that is the issue with restoring backups made with this. Basically a lot of Froyo ROMs are ext3 and this recovery makes the backups as ext4. If you get stuck at the boot logo after a restore, you can try to rename the files that are ext4 to ext3 and open the md5 file and change the names in that to ext3 also. This has been an issue since after 5.0.2.?, it used to have an option for two different file systems.
Yes, the Sharp, U9000, and a few other Froyo ROMs are set up as ext3. I am pretty sure that is the Froyo restore issue with the newer recoveries. With it set to ext4 I can just rename the files like I said above, and the backups restore just fine. I have to get my kernel worked out, before I can change it over to ext4, I posted an incremental Sharp Ver7.5, that has a custom kernel -OC included, that I can see if changing the updater-script to ext4 will work. Basically, the Sharp ROM should act just like the stock ROM, as far as backups go, cause it is using the stock zImage and is set to format as ext3. But that is not fixing the recovery issue. They already have 6.0.1.4 out, but that was just the last time I checked. I just got a new Vertex 4 SSD, so I have been migrating my system over and had to juggle some files. I am all back up and running now so hopefully this weekend I can get some work done on the recovery and my kernel and possibly CM7.
b_randon14
Android Expert
So if you set the system data and cache to auto in the fstab for the recovery, will it still mount those partitions in the new recoveries running a sharp or x6 based rom. Cause if so and it will backup and stuff I will use auto but if not ill have to figure something else out. And yeah I make sure to keep my upstream synced with cm sources. So the recovery will be up to date. And if you want to switch to ext4 you will need to have the init.RC mount the partitions as ext4 as well as change the update script to format as ext4.
But I should get a test build out in a couple days after I make sure it will backup and restore the mobile vfat bootloader partition.
Then we can start checking on USB and adb issues and stuff like that!
But I should get a test build out in a couple days after I make sure it will backup and restore the mobile vfat bootloader partition.
Then we can start checking on USB and adb issues and stuff like that!
So have you tested it on the Stock ROM? Cause if it works on auto with the Stock ROM then it might be on the ROM side. I didn't do many tests with auto once it wouldn't restore a backup, I started looking in to ways to add more than one filesystem. I've only had a couple hours with 6.0.1.4, so I don't know if or what was fixed. I also looked at your github, and wasn't sure which one to pull down, then got lost looking at all the stuff you had in there. I'm working on my kernel right now, something in the defconfig is breaking wifi, I can use the stock one and wifi works but when I use mine it breaks it. I think that may have been why the bkernel zimage broke wifi when I tried it in the Sharp and U9000 ROMs. Once I get this figured out, I'm gonna get back on this recovery and test a few things. Good luck!
EDIT: The only thing breaking wifi was this line:
CONFIG_LOCALVERSION="$(KERNEL_LOCAL_VERSION) -perf"
I had changed it cause I saw that you had changed it for bkernel. Man that was killing me, glad I know now.
b_randon14
Android Expert
Yeah to fix that you can pull in the commits we made to force module loading because the wifi modules were compiled against a 2.6.32.9-perf kernel so when it see 2.6.33.9-bKernel it throws a version magic mismatch and won't load in the modules. There is a commit somewhere on my kernel that enables fotce loading of kernel.modules then you just enable it in the Config.
It comes in handy when applying patches. That'd why when mantera first started patching these kernels they broke wifi so he kept manually changing the version back down to 2.6.32.9!
And I haven't tested restoring a stock rom backup yet. Ill probably try to do that today and see how it goes! I know it will back it up as ext3 but I don't know about restoring yet. Ill post back and let you know!
Oh yeah and adb works fine in cwm but I couldn't get it to mount USB mass storage on Linux mint. Going to look into that!
It comes in handy when applying patches. That'd why when mantera first started patching these kernels they broke wifi so he kept manually changing the version back down to 2.6.32.9!
And I haven't tested restoring a stock rom backup yet. Ill probably try to do that today and see how it goes! I know it will back it up as ext3 but I don't know about restoring yet. Ill post back and let you know!
Oh yeah and adb works fine in cwm but I couldn't get it to mount USB mass storage on Linux mint. Going to look into that!
b_randon14
Android Expert
Okay so I backed up and restored a stock rom all ext3 on my current recovery build and it also backs up the mobile vfat partition as well.
Still haven't dug into USB yet but I'm going to work on it!
Anyone got any ideas on the can't mount errors? Its not a bog deal as it still functions correctly but it just annoys me everytime it shows can't mount recovery command and stuff. I'm thinking about just removeing the sprintf lines where it logs mount errors lol!
But all in all its turning out to be a solid recovery! Oh and I updated to 6.0.15 today as well!
Still haven't dug into USB yet but I'm going to work on it!
Anyone got any ideas on the can't mount errors? Its not a bog deal as it still functions correctly but it just annoys me everytime it shows can't mount recovery command and stuff. I'm thinking about just removeing the sprintf lines where it logs mount errors lol!
But all in all its turning out to be a solid recovery! Oh and I updated to 6.0.15 today as well!
I just pulled in 6.0.1.5, currently running through manteras kernel to see what can be done about the usb mounting. I found this in a forum somewhere #define BOARD_UMS_LUNFILE "/sys/devices/platform/msm_hsusb/gadget/lun0/file" for the extendedcommands.c. I just can't seem to find what ours would be, I tried that one but it didn't work. There are so many dead ends trying to search for a fix, it's driving me crazy. I'm gonna try to rework the kernel to see what I can do. Maybe I can make some headway with the camera while I'm here. I saw your changes to incorporate the hidden and mobile partitions but didn't see an fstab anywhere. I was wondering how to use the fstab to specify the lun file, in extendedcommands.c it says "If recovery.fstab specifies a LUN file, use it".
Well that is all I have for now, just figured I'd post what I have so far.
b_randon14
Android Expert
Another update, I replaced the mount USB code in extended commands with the USB code from cwm 5 and it built fine but still no USB mass storage. If anyone can confirm which recovery had working USB mass storage I will roll the USB code back to then. Its not a big Sexton of code so it wont be to hard to change and hopefully I can get USB mass storage working!!
b_randon14
Android Expert
I can confirm successful restore of the mobile vfat partition so its backing up and restoring all the partitions I added in. Still nothing on USB storage. I really need someone to confirm which recovery had USB storage working!
I'm still having the sd-ext issues, but it may just be my sdcard going bad. When I post some test builds I want some people who have a 2nd sdcard partition to test back up and restores to see of it works!!
I'm still having the sd-ext issues, but it may just be my sdcard going bad. When I post some test builds I want some people who have a 2nd sdcard partition to test back up and restores to see of it works!!
I have been racking my brain trying to figure out the usb mount issue, I was wondering if it had anything to do with a loop device. I am also having a hard time finding a recovery that actually mounts usb mass storage.
I am also kinda hesitant about backing up and restoring the mobile partition, considering what is stored in there. I do think it would be a good option, but as an every time thing I'm just not sure. It would be nice to have like an advanced backup like the advanced restore.
I found that the sd-ext needs to be set to ext4 or else I get errors trying to wipe it.
"NOTE: Issue with creating backups as ext4 filesystem, will cause issues with some Froyo ROMs.
Workaround: If you run into this you can just change the file names in the backup from ext4 to ext3 and also change the names in the md5 file. There is no need to redo any of the md5 checksums."
Okay, I can see where to change the ext4 to ext 3 in the cache, data, and system files. Then, in the nandroid.md5 file, open in edit and change the names of the cache, data, and system files from ext 4 to ext3. Is that correct?
Also When I change the name of a backup file for easier identification of what it is, I always get a checksum error is that normal?
If I backup with one version of CWM, is it possible to restore with another?
And as a last resort what CWM version works with Sharp normally?
Thanks for all your efforts and improvements Bsydz!
Workaround: If you run into this you can just change the file names in the backup from ext4 to ext3 and also change the names in the md5 file. There is no need to redo any of the md5 checksums."
Okay, I can see where to change the ext4 to ext 3 in the cache, data, and system files. Then, in the nandroid.md5 file, open in edit and change the names of the cache, data, and system files from ext 4 to ext3. Is that correct?
Also When I change the name of a backup file for easier identification of what it is, I always get a checksum error is that normal?
If I backup with one version of CWM, is it possible to restore with another?
And as a last resort what CWM version works with Sharp normally?
Thanks for all your efforts and improvements Bsydz!
Yes, you are correct, that is how to rename the files. I am assuming the checksum error is because you can not have spaces in the name of the backup folder. And 5.0.2.7 is the most stable CWM we have at this point, and seems to work with all the available ROMs that i have tried. The backup process should work across all versions, I am pretty sure that the only issue is having the correct file system format for the ROM, which is controlled by the naming scheme.
Aaarrgghhh!!!!
I changed all the names to ext3 and tried a restore and got the MD5 mismatch. I did not touch the name of the backup file.
Did you make sure that the names matched in the md5 file? Cause if all you did was change the file names then there will be a mismatch. Otherwise, for it to get a mismatch the contents of the file have to be different. You can rename a file to what ever you want and the md5 checksum should never change. As for nandroids, all the info in the md5 file has to match.
Also I find the best way to rename the backup folders like this Sharp_Ver7-2012-07-16.15.51.23, basically just add the name before the numbers with out spaces, either using underscores or dashes as spaces. I have all of my backups renamed in my backup folder.
Hope this helps, if you continue to have issues, I would suggest that you revert to 5.0.2.7 until either b_randon or me get things all worked out.
b_randon14
Android Expert
Yeah after thinking, the mobile partition is a very delicate partition. What I may do is have it default to back it up, but not restore it default but it will still show under the advanced restore. Tonight I should have some time to fool around with it.
And about the sd-ext, it's weirding cause cm mounts it as ext3 and cwm partitions it as ext3 so I don't understand why it acts weird when formatting as ext3. Ill probably set it to auto for now. And yeah the USB thing has got me baffled. Its such a small section of code even on cwm 6 so its not much to go through though. Wish I nknew more about how it worked!
And about the sd-ext, it's weirding cause cm mounts it as ext3 and cwm partitions it as ext3 so I don't understand why it acts weird when formatting as ext3. Ill probably set it to auto for now. And yeah the USB thing has got me baffled. Its such a small section of code even on cwm 6 so its not much to go through though. Wish I nknew more about how it worked!
That sounds like a good idea, but just made me think about what the size of the backups are gonna be. That would be an extra 225 MB with the hidden and mobile partitions. We can make an nb0 for our device fairly easy like tj_style did for Andro-id 3.3. It seems like that is kinda where you are going with the being able to backup more of the phone.
I have had my sd-ext partition since before I jacked up my phone with my experiments, and it has always been ext4. Where are you seeing that it mounts it as ext3?
I am in the same boat, wishing that I knew more about how things work, except I wish I knew how to properly write code, instead of having to reference somebody else's work to get an idea of what needs to be done.
So, with the fs set to auto on everything, is it backing up as ext3 then? Cause when I set it to auto it defaulted to ext4 still, maybe it was because you are using the older file in your build.
Anyway, good luck and good work.
b_randon14
Android Expert
Its only another 60mb on my latest backup. And yeah but nb0s are not very user friendly and everything. But yeah see as I have it now, with auto on system data and cache, on a fresh cm7 install, it backs up system as ext4 and data and cache as ext3 where they don't get formatted during the install. On my stock rom it backs them all up as ext3.
But did you partition your sdcard on your computer? If so you probably did format it as ext4. But if you use recovery to partition the sdcard it makes an ext3 partition. And the sd-ext mount script included with cm7 code calls to mount as ext3. See I used cwm to partition my sdcard so its ext3 and I'm running cm7 so it mounts it as ext3 at boot.
But I'm trying to make it as universal as I can so if someone has a ext4 sd-ext it will not mess that up.
But yeah its gonna take some tinkering with USB to get it working I'm afraid!!
But did you partition your sdcard on your computer? If so you probably did format it as ext4. But if you use recovery to partition the sdcard it makes an ext3 partition. And the sd-ext mount script included with cm7 code calls to mount as ext3. See I used cwm to partition my sdcard so its ext3 and I'm running cm7 so it mounts it as ext3 at boot.
But I'm trying to make it as universal as I can so if someone has a ext4 sd-ext it will not mess that up.
But yeah its gonna take some tinkering with USB to get it working I'm afraid!!
So, is that 60MB with all of the partitions or just mobile?
I partitioned the card before I had Ubuntu, so it was done in either 5.0.2.6 or 5.0.2.7.
I found that with my kernel set to mount ext4 it works fine with an ext3 setup. I read somewhere that ext4 would work with ext3 or lower. So I setup the new U9000 kernel to mount as ext4 and there were no issues.
If you want to post a test build you are more than welcome to. I've been working on getting a proper camerahal wrapper for CM9, and working on manteras kernel.
Thanks once again. Yes, I had changed the three names in the md5 file. I did revert back to 5.0.2.7 and adding the name before the numbers works great for identifying the backups.
b_randon14
Android Expert
Yeah ext3 can be mounted as ext4 I believe as well. But yeah 60mb is the hidden hiddendata and mobile partitions.
And I may try just setting it to ext4 and leaving it and see how it does on sd-ext! Good luck on the ics work man!!
And I may try just setting it to ext4 and leaving it and see how it does on sd-ext! Good luck on the ics work man!!
b_randon14
Android Expert
Okay so changing sd-ext back to ext4 seems to resolve my issues with the /sd-ext mouting in cm7.
I have also set it to default backup the /mobile partition, but not default to restore it so there is less of a chance for something to go wrong writing to it. You can still restore it through he advanced restore menu though. Also I made it to where /mobile does not show up in the mount and partition menu so you can't format it that way either.
I still haven't made it anywhere with usb mounting though. This is what I am focused on now!
I am posting the latest build of my CWM in both CWM flashable and just the recovery.img so people can test and report on their outcomes. This should still be able to restore backups made that don't contain the hidden and /hidden/data backups as well as the /mobile back ups. But if for some reason it won't, just go back to the older recoveries for now and I will look into it. Also adb should work and as far as I know, USB mounting is the only thing that does not work as of right now!
Hope everyone enjoy's!
CWM Flashable Zip:
CWM_6.0.1.5_b_randon14.zip
Recovery Binary Img File:
recovery.img
I have also set it to default backup the /mobile partition, but not default to restore it so there is less of a chance for something to go wrong writing to it. You can still restore it through he advanced restore menu though. Also I made it to where /mobile does not show up in the mount and partition menu so you can't format it that way either.
I still haven't made it anywhere with usb mounting though. This is what I am focused on now!
I am posting the latest build of my CWM in both CWM flashable and just the recovery.img so people can test and report on their outcomes. This should still be able to restore backups made that don't contain the hidden and /hidden/data backups as well as the /mobile back ups. But if for some reason it won't, just go back to the older recoveries for now and I will look into it. Also adb should work and as far as I know, USB mounting is the only thing that does not work as of right now!
Hope everyone enjoy's!
CWM Flashable Zip:
CWM_6.0.1.5_b_randon14.zip
Recovery Binary Img File:
recovery.img
Bob Blaylock
Well-Known Member
Would you please seriously consider going back to the color scheme used in the 6.0.1.2 version that you posted last month?
I see some new features that make this newer version worth using, but the new color scheme hurts my eyes. I mean this literally. It causes me physical pain to look at it for more than a few seconds at a time. It's very harsh and glaring and very, very, very uncomfortable. And beside that, it makes it impossible to read the menu item that is highlighted. I cannot read white text against a bright yellow-green background. The color scheme in the older version was much, much better, in terms of comfort, and in terms of usability.
b_randon14
Android Expert
Is there anyway you can remember which version of this you used for the USB storage to work? If so I can take the USB mass storage code from that version and try it on the latest CWM!
If you read in my thread, I stated I am making different themes of my recovery.