First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire HD. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I haven't been able to test it on the HTC Desire HD, since I don't own one.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-ace.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-ace.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks dude,
if i use sense roms, this will still work fine right?
DubelBoom said:
if i use sense roms, this will still work fine right?
Click to expand...
Click to collapse
I don't know of any issues when flashing Sense ROMs with ClockworkMod recoveries, but then I'm also not using Sense ROMs.
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Thanks..Flash it at once!
Sent from my HTC Sensation Z710e using XDA App
p2pjack said:
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Correct, because of a bug in the ClockworkMod 4.0.0.0 source code. Keep an older recovery handy if you're testing this.
You can get around the bug. Each time you get the error, you can "adb shell umount /sdcard" from your computer. It's annoying, and hopefully we can find a solution for it soon.
p2pjack said:
SD card is not recognized any fix for this ?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
+1 on this Had to return to 3.2.0.0
I edited 4.0.0.2, adding j_r0dd's mods and compiled it. Works well on Nexus One and Nexus S. No more sdcard mounting bug, it's been fixed. Can't test it on any other models myself. Updated first post of this thread.
how do you install this?
Doo Doo said:
how do you install this?
Click to expand...
Click to collapse
Through terminal emulator:
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
dirk089 said:
Through terminal emulator:
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
Click to expand...
Click to collapse
thanks for the info
does this work & are you using it ?
Doo Doo said:
thanks for the info
does this work & are you using it ?
Click to expand...
Click to collapse
since few minutes
and it works great.
also the sd-card mount !
dirk089 said:
since few minutes
and it works great.
also the sd-card mount !
Click to expand...
Click to collapse
Glad to hear it!
Sent from my Nexus S using Tapatalk
will it work on EXT4 roms?
Doo Doo said:
will it work on EXT4 roms?
Click to expand...
Click to collapse
That's a good question.
I just tried flashing it through terminal on my ext4 ROM and I just get a "scanning partitions" error.
when i try to flash it says image not found why when its on my sdcard
SD card working here to thank you zyonee
Sent from my Desire HD using XDA Premium App
p2pjack said:
SD card working here to thank you zyonee
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
That's the work of Koush, I think. Glad it works, though.
Sent from my Nexus S using Tapatalk
Doo Doo said:
when i try to flash it says image not found why when its on my sdcard
Click to expand...
Click to collapse
Try renaming it to something short like recovery.img.
Sent from my Nexus S using Tapatalk
Related
ClockworkMod Recovery - Modified for Asus Transformer
OK, so this recovery will skip /data/media (Internal storage) when performing nandroid backups and also when you perform a factory reset.
This means that we can now perform nandroid backups without backing up our internal media and removing it everytime you want to do a backup.
Thanks to Bigrushdog and MadIndustries for helping out with the concept of the solution for skipping /data/media.
Also thanks to Koush and all the other developers that have contributed to clockworkmod, without you guys the android world would be completely different.
Thanks also to everyone in #xoom & #transformer that tested this.
The source code for all changes etc are available through the github repository. The two other projects that have been modified to make this recovery possible can also be viewed through my github account.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
==============================================
General Notes
When I refer to /data/media, this is the same as /sdcard when the transformer is booted into honeycomb. So any data that is stored in here should be untouched by this recovery.
Nandroid backups and restores don't touch the boot or recovery partitions.
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media.
Versioning of recovery images:
At the moment I don't have a version number as such, instead each recovery image is timestamped in the format of DDMMYY-HHYY. So the file recovery-solarnz-120511-2030.img was produced on 12 May 2011 at 8:30 PM. This versioning is also shown in recovery when it starts.
==============================================
Downloads
Recovery Zip (solarnz-R3-240511-1908) FLASHED THROUGH CWM
MD5: 4470bee75f3318f07ec1eb5ddcee1f96
==============================================
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or any other method
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, be sure to reboot your transformer so it complete the flashing process.
Click to expand...
Click to collapse
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
==============================================
Changelog
Code:
[url=http://dl.dropbox.com/u/13093938/XDA/Transformer/recovery-3.1.0.1-solarnz-R3-240511-1908.zip]3.1.0.1 (R3-240511-1908)[/url]
- Initial release for Asus Transformer
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method.
** Reserved **
Great work. I've tested extensively and have found no problems. this does exactly what it says on the tin.
I can also confirm that this version works fine with restoring pre-existing nandroid backups from the same device.
AT LAST someones done it! Thank you
Why it's specific to Transformer? What about Xoom? Does it has different data layout? I thought it should be standard to Honeycomb...
Sent from my Transformer TF101 using Tapatalk
Will this be compatible with previous backups I have made? Will the previous backups still restore the sdcard folder still?
Also, +1 about why this has to be unique for the TF and can't be honeycomb universal.
anyone install rom manager yet? it says that i don't have CWM recovery installed but i do because i've used it shoudd i reinstall useing ROM manager?
timtlm said:
Will this be compatible with previous backups I have made? Will the previous backups still restore the sdcard folder still?
Also, +1 about why this has to be unique for the TF and can't be honeycomb universal.
Click to expand...
Click to collapse
See this
http://forum.xda-developers.com/showpost.php?p=14090086&postcount=3
Thought I'd give quickboot a try... not working for me. Anyone else use that? It just reboots my device to HC when I do Recovery or Bootloader. Oh well, I'll do it oldskool.
ViViDboarder said:
Thought I'd give quickboot a try... not working for me. Anyone else use that? It just reboots my device to HC when I do Recovery or Bootloader. Oh well, I'll do it oldskool.
Click to expand...
Click to collapse
@ViViDboarder & jtn7040
Neither of these methods will work currently to reboot into recovery. However you can use Quickboot to reboot the TF and hold the Vol Down then press Vol Up to get to recovery.
Cordy said:
@ViViDboarder & jtn7040
Neither of these methods will work currently to reboot into recovery. However you can use Quickboot to reboot the TF and hold the Vol Down then press Vol Up to get to recovery.
Click to expand...
Click to collapse
Good to know going to flash this tonite, hopefully they will be able to get this working like we have on the phones. But like ViviDboarder said I can do it old school for now
Great! Def needed this.
Does anyone know if performing a factory reset/wiping deletes the data in this directory?
Yes, that will wipe the data too.
Thanks for the CWM mod, this will save me the headache of having to backup my music and videos for no reason
Sent from my Transformer TF101
Sweet, thanks.
I'll flash it as soon as another ROM version floats a long.
I cannot use ROM Manager as it says you need to install cwm and the trans is not listed. I emailed about it but have not heard back.
Sent from my Transformer TF101 using XDA Premium App
Hatman41 said:
I cannot use ROM Manager as it says you need to install cwm and the trans is not listed. I emailed about it but have not heard back.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Cwm for the transformer is not supported by rom manager yet
Sent from my ADR6400L using Tapatalk
Crimton said:
Cwm for the transformer is not supported by rom manager yet
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yes I know that. I only said that because the OP has it mentioned that you can flash this new one via RomManager.
Hatman41 said:
Yes I know that. I only said that because the OP has it mentioned that you can flash this new one via RomManager.
Click to expand...
Click to collapse
Oh ok. I just assumed it was a mistake in the op.
Sent from my ADR6400L using Tapatalk
Hatman41 said:
I cannot use ROM Manager as it says you need to install cwm and the trans is not listed. I emailed about it but have not heard back.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Same here! I hope that the TF will be added soon! It's working but for convenience sake I paid for the premium so I expect some service hahahaha
ViViDboarder said:
Thought I'd give quickboot a try... not working for me. Anyone else use that? It just reboots my device to HC when I do Recovery or Bootloader. Oh well, I'll do it oldskool.
Click to expand...
Click to collapse
Modaco has done an app to reboot to the recovery https://market.android.com/details?id=com.modaco.transformerrecoveryboot&feature=search_result
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
Special thanks goes out to everyone who tested for me.
I do not have the device, so I rely heavily on testers to report any bugs.
Here is CWM for the SK4G.
You will need to modify your stock recovery binary to be able to use CWM.
Kernel Devs can also compile CWM into their kernel by extracting the update.zip and building it into their initramfs.
To replace your stock recovery binary with the modified binary:
download this file
DEAD. USE BALI KERNEL
Exatract and take the recovery binary file inside of it and use root explorer or adb push the file to /system/bin.
DO NOT delete the current one there, or rename any files.
Just overwrite it.
I would however, recommend getting Android Commander from www.androidcommander.com It's a lot easier, and a lot more useful.
CWM Final
DEAD. USE BALI KERNEL
Place in the root of your SD.
You can now use Quick Boot from the market, or adb reboot recovery to boot into CWM
I have sent Koush the device tree to have the official update.zip supported within Rom Manager.
UNTESTED:
You can also take the contents from the update.zip and replace the contents that are in noobnl's recovery rerouter/root.
Again, I haven't tested that due to not having the device.
First! Congrats krylon and thank you
Krylon: link 404'd
Sent from my SGH-T839 using XDA App
Thank you very mucho!
Sent from my SGH-T839 using XDA App
i cant dowload recovery zip
I don't know if its just me but the first link is not working
Sent from my SGH-T839 using XDA App
Guys... add a /sk4g to the first url so its like the 2nd url... thank me later
Sent from my SGH-T839 using XDA App
http://www.krylon360.com/file_host/sk4g/recovery.zip
mattpall said:
Guys... add a /sk4g to the first url so its like the 2nd url... thank me later
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Datlilboricua said:
http://www.krylon360.com/file_host/sk4g/recovery.zip
Click to expand...
Click to collapse
Fixed. thanks.
Thanks lilboricua
Sent from my SGH-T839 using XDA App
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Nand backup error
with the new recovery (remapped buttons) i tried to do a nand backup and it wouldnt start and it'd auto matically say error while backing up boot image... can anyone see if they come across this aswell ..
mattpall said:
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
this phone is not basically a galaxy S. heck, when the SGS4G came out people said it was basically a vibrant. NOPE. Wrong.
It would be hard to do, but might be doable.
ayoteddy said:
with the new recovery (remapped buttons) i tried to do a nand backup and it wouldnt start and it'd auto matically say error while backing up boot image... can anyone see if they come across this aswell ..
Click to expand...
Click to collapse
didn't you test this?
mattpall said:
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
if we could get a stock kernel with just the ext4 patch so we would be able to run our system, data and cache on ext4 i'd be pleased enough . idk if anyone with this phone would be able to rebuild the kernel with that patch but if so our phones would easily be 3x faster
I also see the same problem. I didn't think to test backups. What was all changed from the working version to the current version? all that needed to be changed was the lun map and BOARD_USES_CUSTOM_KEYMAP
krylon360 said:
didn't you test this?
Click to expand...
Click to collapse
yes i tested the original one completely and everything worked, the new one you sent me i only tested the buttons and mapping which were fine . but it seems now the nand backup/restore has a problem.
Edit: i just made another nand backup with the original recovery without the back button mapping and it works. seems the edited one got the backup/restore broken somehow
ayoteddy said:
if we could get a stock kernel with just the ext4 patch so we would be able to run our system, data and cache on ext4 i'd be pleased enough . idk if anyone with this phone would be able to rebuild the kernel with that patch but if so our phones would easily be 3x faster
Click to expand...
Click to collapse
not hard to do at all. unpack, add in ext4 mount options, repack, then flash kernel, and script to convert.
sduvick said:
I also see the same problem. I didn't think to test backups. What was all changed from the working version to the current version? all that needed to be changed was the lun map and BOARD_USES_CUSTOM_KEYMAP
Click to expand...
Click to collapse
Omg didn't test backups? :facepalm
Sent from my SGH-T839 using XDA App
ayoteddy said:
yes i tested the original one completely and everything worked, the new one you sent me i only tested the buttons and mapping which were fine . but it seems now the nand backup/restore has a problem.
Edit: i just made another nand backup with the original recovery without the back button mapping and it works. seems the edited one got the backup/restore broken somehow
Click to expand...
Click to collapse
the new one all I did was change key mapping and UMS path... odd.
Ok I did the recovery to system bin and did the update it changed to cwm and I tried nand errors out I reboot and reboot back into recovery I'm back to stock recovery
Sent From My Rooted Sidekick 4g Premium XDA App
I notice you guys don't seem to have one of these, I made one in the O2X dev section so as not to balls up the proper nightly thread, anyone else who likes to build, feel free to add to this thread.
I was asked to build this in lieu of a proper nightly, it contains all commits up to and including the OMAP4 touch to focus one.
http://www.mediafire.com/file/q0gx7iruh2qhguh/update-cm-7.1.0-RC1-G2x-KANG-signed.zip
MD5: e79a5c128bd72c50fa0735cc4551d80f
As this is now based on the EXT4 file system, you might want to convert /data and /cache to EXT4 as well, as they will remain EXT3 (but mounted as EXT4). This zip will sort that for you, although if you wipe cache, it will revert to EXT3 for some reason (at least on the O2X it does, so I'm assuming this is the same): http://www.mediafire.com/file/a9gor6o2b26co8r/p999-ext4.zip
DISCLAIMER:
I do not own a G2X, I have in no way tested this update, you might want to consider some sort of backup before flashing these, even if someone else has already done it and reported all is well.
Has anyone used the ext4 conversion for the rest of the system?
skater4690 said:
Has anyone used the ext4 conversion for the rest of the system?
Click to expand...
Click to collapse
What rest? /cache and such?
Sent from my Google Nexus S using Tapatalk
I have used the converter and it works and there was no data loss or hiccups. To the above poster /cache is converted when flashing as long as you wiped it before hand. It will not convert partitions that have data in them.
Sent from my LG-P999 using xda premium
xsteven77x said:
I have used the converter and it works and there was no data loss or hiccups. To the above poster /cache is converted when flashing as long as you wiped it before hand. It will not convert partitions that have data in them.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'm just asking what "rest"
Sent from my Google Nexus S using Tapatalk
When it says wipe cache, is that during the flash process or anytime you wipe the cache after the ext4 flash it will revert to ext3?
Sent from my LG-P999 using xda premium
No just the usual wipe cache wipe dalvik install nightly fix permissions. It won't revert everytime u wipe.
Sent from my LG-P999 using xda premium
xsteven77x said:
No just the usual wipe cache wipe dalvik install nightly fix permissions. It won't revert everytime u wipe.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
In the op it says if you wipe cache it will revert back to ext3.
Sent from my LG-P999 using xda premium
hitman818 said:
In the op it says if you wipe cache it will revert back to ext3.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yeah that's my experience of my O2X's behaviour, the G2X might not do it. Someone test it, do a cache wipe and check the mounts while still in recovery (it will say EXT4 if you boot to CM7 regardless of what it actually is).
If it does revert to EXT3, you can use the zip again.
PS. There is no need to wipe cache or dalvik cache when flashing a new nightly or kang, it's hashes will be invalid and it gets regenerated anyway.
Rusty! said:
Yeah that's my experience of my O2X's behaviour, the G2X might not do it. Someone test it, do a cache wipe and check the mounts while still in recovery (it will say EXT4 if you boot to CM7 regardless of what it actually is).
If it does revert to EXT3, you can use the zip again.
PS. There is no need to wipe cache or dalvik cache when flashing a new nightly or kang, it's hashes will be invalid and it gets regenerated anyway.
Click to expand...
Click to collapse
I was talking about flashing the utility that will convert to ext4. If we wipe cache will it revert the system as well as the data? Also theres another utility that will convert the data to ext4 in the other kang thread. Are they both the same?
Sent from my LG-P999 using xda premium
Right, now I understand
No, /system won't be changed, just /cache.
The 'utilities' might be very similar, but I doubt they're the same, as I made this one.
Rusty! said:
Right, now I understand
No, /system won't be changed, just /cache.
The 'utilities' might be very similar, but I doubt they're the same, as I made this one.
Click to expand...
Click to collapse
What about the /data will that stay on ext4 or will it revert?
Wiping cache wont hurt it, and apparently wiping/factory reset from recovery (v5.0.2.0) will set it to EXT4, although I've not tested it.
FYI: This kang (and ext4 script) is working great for me so far. Thanks!
Sent from my LG-P999 using XDA App
Are we gonna see updated builds or is this just it?
Sent from a Nexus X by LG
DJ "suMo* said:
Are we gonna see updated builds or is this just it?
Sent from a Nexus X by LG
Click to expand...
Click to collapse
The idea is that anyone can add a build to this thread, so that if an interesting new commit pops up, and people don't want to wait, they post it here. I don't mind running off updated versions if necessary.
I was hoping to emulate the O2X version of this thread: http://forum.xda-developers.com/showthread.php?t=1118091
We have two new commits that I don't think mean much for our phone, but once we get a couple more can we get a new kang pretty please with cherry on top .
Please lets quit talking about the other thread. Its gone and now we have a much nicer, friendlier, and less hostile thread. Lets just enjoy it!
Sent from my LG-P999 using xda premium
Can anyone comment if their fs reverted to ext3 from wiping cache after flashing the ext4 utility? Also can you comment if only the cache gets reverted and not the data?
Sent from my LG-P999 using xda premium
herzzreh said:
Useless whining IMO.
Now, Rusty, where did you pull the kernel from? Also, any errors on pulling the CM source? My pull would eventually crap out even with -f and go nuts about android.git.kernel being down even though I edited the repo script.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I've had it crap out on me with -f as well, I used repo sync -f -j32 with success though, possibly doing 32 things at once helps with it.
As for the kernel, it comes with a prebuilt one as part of the sync (find it @ /devices/lge/p999/kernel), but if you want the source, create a new directory and git clone https://github.com/CyanogenMod/lge-kernel-star.git to download it. You can update it with git pull from then on.
Thread purged of useless posts.
A. For reasons stated in the OP the releases in this thread are NOT the same as Fitsnugly's kangs.
B. This thread is not the place to discuss Fitsnugly or his contributions to XDA and the Android community. This thread is for you to discuss Rusty's Unofficial CM7 Kangs.
C. Fitsnugly is/was a very valued contributor to the forums. He left because of whiny, "entitled" users who ignored his requests in his OPs. Anyone I see complaining about how he chose to leave will be met with a temporary ban.
Let's keep discussion in this thread on topic. This means Rusty's kangs ONLY.
Edit: Thanks herzzreh for the heads up on the post I missed.
This is a clockworkmod recovery built completely from source. It has the latest cwm updates and the latest ics kernel (eMMC erase bug fixed). This should also have the hanging backup bug fixed. I havent had time to make a billion backups to test this but the few i did without the .hidenandroidprogress file worked like a charm If you do get a hanging backup that is all koush's fault as i just used his latest sync to cwm.
To get adb working on this:
add these lines to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
-add them in the section that says [Google.NTx86] and the section that says [Google.NTamd64]. just make it look like the ones that are already there but with this code:
Code:
;
; Samsung Skyrocket
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0231&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
- then right click "my computer" and go to device manager
- you will see a driver with a yellow exclamation point...right click it and click "update driver software"
- click "browse my computer"....then click "let me pick from a list of device drivers on my computer"
- then click all devices
- click "have disk..."
- go to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"
- click to allow installation of driver
- presto
DOWNLOADS:
recovery.img / recovery.tar.md5
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CHANGES:
Changes here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Nice job man!
Good Job! :good:
Will test it in a bit
so i guess we have to use adb, or can we use odin, if not do u think u will make it flashable through odin
thks for the new cwm
vincom said:
so i guess we have to use adb, or can we use odin, if not do u think u will make it flashable through odin
thks for the new cwm
Click to expand...
Click to collapse
there is a recovery.tar.md5 that is already there in the OP....thats made for odin. just flash in the pda tab. in the downloads......
sk8erwitskil said:
there is a recovery.tar.md5 that is already there in the OP....thats made for odin. just flash in the pda tab. in the downloads......
Click to expand...
Click to collapse
great, didnt c that, thks
just making sure that no ones getting bricks from this, and for sure that the emmc thing is fixed
Is this recovery just for ppl who is on ICS roms? Gingerbread roms? Either?
Does it work a 100% now? Was the problem with unable to read external sd card and to format fixed?
Sent from my SAMSUNG-SGH-I727 using xda premium
kinvid said:
Is this recovery just for ppl who is on ICS roms? Gingerbread roms? Either?
Click to expand...
Click to collapse
both
r3dp0is0n2012 said:
Does it work a 100% now? Was the problem with unable to read external sd card and to format fixed?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
i never knew about a "unable to read external sdcard" error. the emmc format brick bug is fixed.
Excuse my noobness , and thanks for all your work
What is the difference between all those recoveries ? this one , you're other modified recovery and this one from CWM website http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.3-skyrocket.img ? apart from being with touch or not ?
Thanks
SK8, now that this base has the bugs ironed out are you planning to theme it like your other recovery?
mahanddeem said:
Excuse my noobness , and thanks for all your work
What is the difference between all those recoveries ? this one , you're other modified recovery and this one from CWM website http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.3-skyrocket.img ? apart from being with touch or not ?
Thanks
Click to expand...
Click to collapse
mostly just the UI.
bluntman420 said:
SK8, now that this base has the bugs ironed out are you planning to theme it like your other recovery?
Click to expand...
Click to collapse
ill just make a tutorial that shows how to change the font and background and colors and stuff instead of making a million different versions. i think that would be easier.
updated links to have all the latest changes to clockworkmod
Can you add "format /boot" option ?
mahanddeem said:
Can you add "format /boot" option ?
Click to expand...
Click to collapse
No problem. It's on the road map. I've just been busy focusing on a backup issue atm. I'll add that today tho
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi, first of all thanks for the recovery, it has been part of all my development. I might play with this over the weekend. My questions are:
1) Will it restore backups created from older version. I have parked on 5.5.0.4 BL14 (I think)
2) Does this include usb mount external sdcard?
TIA
mohan_kr said:
Hi, first of all thanks for the recovery, it has been part of all my development. I might play with this over the weekend. My questions are:
1) Will it restore backups created from older version. I have parked on 5.5.0.4 BL14 (I think)
2) Does this include usb mount external sdcard?
TIA
Click to expand...
Click to collapse
yes it should restore any backups made with any version of cwm.
this version does mount the external sdcard and not the internal. right now its only one or the other. the stock option is the mount the external. i can make a version that mounts the internal and post that if you would like. but until the commits from twrp get picked over its just one or the other.
Flashing in odin failed. File coming up as recovery.tar.tar in odin. someone help please.
---------- Post added at 07:07 PM ---------- Previous post was at 07:01 PM ----------
r3a1ist said:
Flashing in odin failed. File coming up as recovery.tar.tar in odin. someone help please.
Click to expand...
Click to collapse
Figured it out, why the heck was internet explorer changing my filename? Firefox was the answer. Sry.
Any news for T989 (Hercules)? Thanks!