Database Info

custom mtd on chacha

conclusion first: it was possible.
i searched for custom mtd info for chacha on google, and i found some info in chinese suggested it was possible to apply custom mtd on chacha.
http://wenku.baidu.com/view/b029ab6027d3240c8447ef67.html
i don't speak chinese, but google translation helped. i used Mikevhl's recovery (http://forum.xda-developers.com/attachment.php?attachmentid=749943&d=1318622558), and also FR-Custom-MTD-v1.5.6-boot.zip (http://115.com/file/aqvgn30z#) and FR-Custom-MTD-v1.5.6-recovery.zip (http://115.com/file/aqvgnzmc#) as the chinese instruction said although i don't know where these files came from (maybe somewhere here?)
the procedure itself was the same as desire (bravo) or any other devices, and after the process, i got;
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 214004 32 213972 0% /dev
/dev/block/mtdblock4 5120 1624 3496 32% /cache
/dev/block/mtdblock3 153600 150292 3308 98% /system
/dev/block/mtdblock5 307200 2560 304640 1% /data
yay!!
unfortunately, adlx.xda's v5.0.2.8 didn't work with these patches... sorry, if this info is already around here.
p.s. as usual, this patch automatically mounts /cache to /sd-ext when /cache partition is smaller than 20mb. however, /cache/download won't be created automatically which means vending.apk (market) fails to start. when you set /cache less than 20mb, you'd need create sd-ext partition on your sd card and either add init.d script to create /cache/download ot do it manually.

Interesting, but sorry I don't read chinese :-(. I understand it's for changing the default partition layout on the Chacha.
Isn't it easier to use App2SD?
What are the patches? Do you why it doesn't work with my CWM build (maybe we can improve it so it work).

adlx.xda said:
Interesting, but sorry I don't read chinese :-(. I understand it's for changing the default partition layout on the Chacha.
Isn't it easier to use App2SD?
What are the patches? Do you why it doesn't work with my CWM build (maybe we can improve it so it work).
Click to expand...
Click to collapse
hi adlx.xda,
i don't read chinese, either;-)
it is sure easier for most people to use app2sd or data2sd, but i prefer to keep everything in the internal memory because it is possible if you change the partitions and don't install millions of apps. it is kinda a surprise to me that you didn't know about custom mtd...
anyway, the patches were originally created for htc desire, and adopted to other htc devices with low internal memory capacity like chacha/wildfire/etc.
http://forum.xda-developers.com/showthread.php?t=806321
there were two patches in the package; one for recovery partition and the other for boot partition. the recovery patch allows you to burn a custom rom according to the designated partition info. the boot patch allows you to change the boot image so that the device recognize the new partition info on boot.
when i use your recovery and the recovery patch together to burn a custom rom, chacha does not boot. i guess the patch does not modify something in your recovery correctly. on the other hand, this patch correctly modifies Mikevhl's old recovery. it is strange the patch can be used for the latest recovery for htc desire...
thx for your attention.
qt

could also be the repackaging of the kernel if it's patched. I tried for weeks unsuccessfully to unpackage and repackage a kernel for the status/chacha and had no luck. I was wanting to do some clocking tweaks.

bedwa said:
could also be the repackaging of the kernel if it's patched. I tried for weeks unsuccessfully to unpackage and repackage a kernel for the status/chacha and had no luck. I was wanting to do some clocking tweaks.
Click to expand...
Click to collapse
How do you try to unpack/repack? I wonder why it would fail.

I'll have to look at my setup on my netbook and get back to you. May be a few days. :-\ Kinda swamped ATM.
My Tab makes calls Yo! GT-P6800

i do read chinese, i saw this fews mths back but i dont have time for it... you will left with 24x~26xmb of free space.

I just wanted to update and say that I replied to this thread:
http://forum.xda-developers.com/showthread.php?p=35367602#post35367602
Basically, I'm wondering if the CustomMTD patches might be more compatible with a newer version of CWM compiled for our phone. I built a copy of 6.0.1.5, which mostly works, so if someone wants to give it a try, please do.

I managed to see custom partitions from CWM (not with the patches, but manually altering the recovery). 312MB /system and ~120MB /data (as an example just to try)
Apparently no problem with /system, but /data is not "working":
It appears as Read Only (it shouldn't actually event mount after moving/resizing it). Also not only it mounts, but it appears as 100%full, and won't allow me to do anything. I can't reformat it, remount rw,... I don't know why to be honest.
Now that I think about it, I should check dmesg.

dead links
it looks like all the links are dead.
here are the files you need.

qtotter said:
it looks like all the links are dead.
here are the files you need.
Click to expand...
Click to collapse
I managed to have it working, but I posted on another thread: http://forum.xda-developers.com/showpost.php?p=38029256&postcount=9

adlx.xda said:
I managed to have it working, but I posted on another thread: http://forum.xda-developers.com/showpost.php?p=38029256&postcount=9
Click to expand...
Click to collapse
so what files do we need, and what exactly do we do with them? I'd love to do the same as what you got working.

kronflux said:
so what files do we need, and what exactly do we do with them? I'd love to do the same as what you got working.
Click to expand...
Click to collapse
IIRC I used no files/patch,... It was more a matter of doing the partition table right. I took some notes and made an excel spreadsheet to help me with the conversions.
I'm on holiday starting today, I probably won't be able to review my notes and write anything related to this this month. Ping me again in Septembre so I review my notes and write a post about it .

kronflux said:
so what files do we need, and what exactly do we do with them? I'd love to do the same as what you got working.
Click to expand...
Click to collapse
it came from this thread originally http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1, and it is very common among HTC Desire users.
it is quite easy to change partition sizes, and all the files you need are the three files that i uploaded.
recovery_chacha.img: Mike's old recovery that is compatible with this method. Don't use other recoveries!!
FR-Custom-MTD-v1.5.6-recovery.zip: This will patch recovery so that it can handle new partition sizes.
FR-Custom-MTD-v1.5.6-boot.zip: This will patch boot (kernel) in NAND so that the system can handle new partition sizes.
Procedure for ChaCha:
Make sure your phone is S-OFFed
**Make a backup in recovery first**
Place FR-Custom-MTD-v1.5.6-recovery.zip & FR-Custom-MTD-v1.5.6-boot.zip on SD card
Create mtdpartmap.txt on SD card with size of system & cache like "mtd 125 5". For example, I wanted to use ajeevlal's cm10.1 with Japanese IME and other system apps built in /system, I needed 330MB on /system and only 5MB on /cache (because I didn't need large /cache to use int2ext+.) So, my mtdpartmap.txt was "mtd 330 5". if you want to do this by shell command, it's gonna be like: echo "mtd 330 5" > /sdcard/mtdpartmap.txt
Flash Mike's old recovery above in fastboot like "fastboot flash recovery recovery_chacha.img"
Reboot into recovery
Wipe system, data, and cache
Flash FR-Custom-MTD-v1.5.6-recovery.zip, this patches recovery to use the new partition sizes
Reboot into recovery
Wipe system, data, and cache again just in case
Flash ROM, or restore from backup, and it will be flashed to NAND based on new partition sizes
Prior to rebooting, flash FR-Custom-MTD-v1.5.6-boot.zip, this patches boot (kernel) in NAND to load with the new partition sizes.
Reboot
unless you change mtdpartmap.txt on SD card, you don't need to repeat 1 - 8 every time. once you have decided your favorite partition sizes, you can start from 9. also, if your backup includes a patched boot image already, you can even skip 12 as well.
if you do this with any other newer recoveries, your phone simply does NOT boot. Mike's old recovery cannot backup sd-ext partition, but you can always do it manually like "dd if=/dev/block/mmcblk0p2 of=/sdcard/ext-bkup.img bs=4096" or something anyway.

kronflux's recovery
by the way, i tried your CWM 6.0.1.5 Built From Adlx http://forum.xda-developers.com/showthread.php?t=1989839, but it does not patch boot correctly. so the phone won't boot.
as i repeatedly keep saying, you need mike's old recovery to do this. i have tried so many recoveries, and this old one is the ONLY that is compatible with these patches.

qtotter said:
by the way, i tried your CWM 6.0.1.5 Built From Adlx http://forum.xda-developers.com/showthread.php?t=1989839, but it does not patch boot correctly. so the phone won't boot.
as i repeatedly keep saying, you need mike's old recovery to do this. i have tried so many recoveries, and this old one is the ONLY that is compatible with these patches.
Click to expand...
Click to collapse
it's also too large to fit in the recovery partition properly I believe. would be great if we could come up with a partitioning table that has enough space for it, as well as a little more space for app/rom storage.
so what are you saying, that we need this other recovery to actually do the partitioning? or that only that recovery will work on a custom partition table?
Adlx was just saying above, he doesn't think he used any custom files or patches. naturally we'll see in september what he has to say about it.

I did it with my recovery, not Mike's, and it worked, but again, I did it manually.
Sent from my Galaxy S4 running CarbonRom "Adlx Edition"

kronflux said:
so what are you saying, that we need this other recovery to actually do the partitioning? or that only that recovery will work on a custom partition table?
Click to expand...
Click to collapse
basically, this process patches recovery and boot to rewrite the partition table. Only Mike's old recovery can do both correctly.
talking about other recoveries, the reason why the phone doesn't boot is either recovery patch failure or boot patch failure. because i know Mike's one works and am not a recovery dev, i didn't even try to find which part is not working.
however, you can easily check it by switching the recovery between patching recovery and patching boot. i guess the former part is not working correctly because the latter part is rather straight forward and simple.
i just don't understand what you want, actually. changing the partition sizes or learning the mechanism of changing partition table??

qtotter said:
i just don't understand what you want, actually. changing the partition sizes or learning the mechanism of changing partition table??
Click to expand...
Click to collapse
Essentially, changing the sizes of partitions to accommodate a larger recovery image(so that my CWM6 could be flashed and work properly), as well as add more space to the system partition so that we don't have to worry about flashing lite versions of Gapps, or slimming down roms so that they fit.

kronflux said:
Essentially, changing the sizes of partitions to accommodate a larger recovery image(so that my CWM6 could be flashed and work properly), as well as add more space to the system partition so that we don't have to worry about flashing lite versions of Gapps, or slimming down roms so that they fit.
Click to expand...
Click to collapse
i have already explained how to do it above... now, my /system is 330 MB, and /cache is 5MB to cooperate with ajeevlal's cm10.1, full gapps, additional system apps and int2ext+. i am quite happy with my chacha setting not worrying about free space of /data, and battery lasts almost forever during sleep.
well, it is such a simple procedure, but i don't need to promote it to other people myself. i simply wanted to share the info that i learned over one year ago with people who want to make /system smaller for stock rom or make /system larger for cm10 and above.

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the HTC One S
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16
Created 2013-09-16
Last Updated 2013-09-16

You guys are doing an amazing job, ROM will come these days!

Well, this is version 2.2.1 but wheres the changelog for it ?
I installed it anyway, but I like to see what changed :-3
EDIT:
Nevermind, this is for S3 >.<

Love it! Glad to see s3 getting some love too!
Sent from my HTC VLE_U using Tapatalk 2

Yeaaaaaaaaaah! Yes! Yes! Yesssss! Yeeees! Thank you million times!

Fantastic!

@Dees_ Troy
I seemed to find a little bug. The battery in recovery always shows 66%.

Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium

dsellers2 said:
Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Yeah I've learned that yesterday that this is a well known issue with some of the htc. There is two waya,one you have described to flash it manually in fastboot and the other is a workaround that twrp supports. It is called HTC dumlock,just search on their official page how to use it.
Sent from my HTC One S using xda app-developers app

Thank dev. For S3 development.
Sent from my HTC One S using xda app-developers app

I got my Villec2 Unlocked with htcdev.com site
but i can't flash any recovery, Why?
I found that this recovery works on my hts one s (my i mean villec2)
i tried to do it couple of times with cmd and fastboot, and then with HTS ONE S AIO KIT
every time it says that sending is ok, and writing i ok... but can't go into recovery got only htc sentence...
Do you guys got any solution? whey on that threat above some people with s3 says that they flashed recovery and i can't do it?

Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP

Wyall said:
Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP
Click to expand...
Click to collapse
I tired that method also without any progress,
GooManager downloaded img then i saw little box that recovery installed successfully, But unfortunately still cant use recovery

Do you have root? And did you use the Reboot to Recovery Option in GooManager?

Wyall said:
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
Click to expand...
Click to collapse
I just got unlocked Phone with htcdev, i thought that i need to Flash Recovery before i can Flash superSu like i saw in torxx guide. Can i Flash superSu like i try to Flash Recovery? Which one shall i choose?
With GooManager i restart to Recovery, the result was the same....
And still i count on your help in flashing Recovery on my HTC
Regards in advance

First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/

Wyall said:
First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/
Click to expand...
Click to collapse
So now i got root (method from link above) and i got custom recovery installed with gooManager method. Sweet. i for other users it's very important to got root first

Updated to 2.2.2.0!

Dees_Troy said:
Updated to 2.2.2.0!
Click to expand...
Click to collapse
Hi!! Has full wipe partitions in this recovery?
Thanks?

Do it work with S4 or just only S3? Thanks

[RECOVERY][HeroC]TWRP 2.2.2.0 touch recovery [2012-08-24]

Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)

Going to flash this now and give it a try. Hopefully it works out good.

whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!

thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks

I flashed this a week or two ago and been working awesome! I love it.

i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this

they are in different folders on the SDCARD, im not even sure they are compatible.

ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder

alsp cani get the twrp 2220 in a zip format?

will this recovery work with firerats? on heroc?

dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:

thanks im trying it now, love the use of touch

I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc

I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.

Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?

* DELETE *

There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.

DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app

Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.

[RECOVERY][Unofficial][Epic4G] TWRP 2.6.3.0 touch recovery [2014-02-11]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
Latest Builds Here
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]

Links are up enjoy the light show
Twrp now has haptic feedback.
edit: This is untested.

Wow, finally no more empty zips that bricks the phone. Downloading.

Finally the 2.6.3.0 version
Waited for long time for this
Sent from my Nexus 5 using xda app-developers app

Does this work with all partitions?
Sent from my SPH-D700 using Tapatalk 2

DaKillaWilla said:
Does this work with all partitions?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Yes , it was confirmed working.

Hello all,
I flashed TWRP 2.6.3.0 and now any ROM I try to flash getting FAILED message. Am I missing something...
Thx in Adv

FerociousAndroid said:
Hello all,
I flashed TWRP 2.6.3.0 and now any ROM I try to flash getting FAILED message. Am I missing something...
Thx in Adv
Click to expand...
Click to collapse
Give more info what rom? What recovery etc.
Sent from my SPH-D710 using Tapatalk

Unjustified Dev said:
Give more info what rom? What recovery etc.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Fashed from CMW 5.0.2.7 to Twrp_6.3_Unofficial_20140211_d700.zip. Then tried installing any of the following:
cm-7.2.0-epicmtd.zip
cm-10.1.3.1-epicmtd.zip
Try to go back to cwm-5.0.2.7-epic4g.zip
ThePeoplesROMv2.22_BML.zip
ThePeoplesROMv2.22_MTD.zip
I odin back to "pit & Deodexed-FC09.zip" and then installed CMW 5.0.2.7. I'm on CM10.x. Didn't bother with TWRP. I could be have been the new Samsung 4GB micro SD card I was using who knows.
Thx any way.

FerociousAndroid said:
Fashed from CMW 5.0.2.7 to Twrp_6.3_Unofficial_20140211_d700.zip. Then tried installing any of the following:
cm-7.2.0-epicmtd.zip
cm-10.1.3.1-epicmtd.zip
Try to go back to cwm-5.0.2.7-epic4g.zip
ThePeoplesROMv2.22_BML.zip
ThePeoplesROMv2.22_MTD.zip
I odin back to "pit & Deodexed-FC09.zip" and then installed CMW 5.0.2.7. I'm on CM10.x. Didn't bother with TWRP. I could be have been the new Samsung 4GB micro SD card I was using who knows.
Thx any way.
Click to expand...
Click to collapse
I second this, my backups & flashable zips that worked fine with 2.6.0.0 are no longer working in this TWRP version, even though the md5 checks out. There is a problem with this new release, imo, as this was an occurrednce with both of my Epics.

Luthiensdad said:
I second this, my backups & flashable zips that worked fine with 2.6.0.0 are no longer working in this TWRP version, even though the md5 checks out. There is a problem with this new release, imo, as this was an occurrednce with both of my Epics.
Click to expand...
Click to collapse
Probably because of the updates etc that were done. I can't guarantee older backups will be compatible.

Unjustified Dev said:
Probably because of the updates etc that were done. I can't guarantee older backups will be compatible.
Click to expand...
Click to collapse
I don't think that's the case, the problem occurs when flashing ROM & kernel zips too, not just when attempting to restore existing backups. I re-downloaded a couple (& checked md5) again to confirm this. (Of course, I also checked md5 for this new recovery prior to installing it)

Luthiensdad said:
I don't think that's the case, the problem occurs when flashing ROM & kernel zips too, not just when attempting to restore existing backups. I re-downloaded a couple (& checked md5) again to confirm this. (Of course, I also checked md5 for this new recovery prior to installing it)
Click to expand...
Click to collapse
Well sorry I guess this won't be fixed because I quit developing. I can do no more than answer questions.

flash off of CWM and now I got stuck on the Samsung screen. any help?

Nexus11 said:
flash off of CWM and now I got stuck on the Samsung screen. any help?
Click to expand...
Click to collapse
Give me some time to compile a new one I have to update both epic 4g and epic 4g touch.

[MOD][CM11] Classic sdcard mount

This mod for CM11 on moto_msm8960 brings back the classic sdcard mount we know from devices like the Nexus One.
No more cluttering of /data with files which should go to sdcard.
Features:
- External sdcard mounted as /sdcard
- Internal memory fully available for /data
Installation:
- Have a nandroid backup of /boot and /system at hand if something goes wrong
- Simply flash the zip over your existing CM11 installation
- Wipe data is not necessary but will help if you have problems.
Deleting only the data of the concerned apps should be sufficient. (Only apps storing data on sdcard are effected)
- Files which were on the emulated sdcard can be found at /data/media/0. This is also the location where you have to put your zip files to be able to flash them with OpenRecovery.
Method:
Adjusting of following CM11 files to be in line with Nexus One example configuration according to:
http://source.android.com/devices/tech/storage/config-example.html
boot.img
- init.qcom.rc
- fstab.qcom
framework-res.apk
- storage_list.xml
See my github for details: https://github.com/S-I-M-O-N/android_device_motorola_moto_msm8960
Disclaimer:
This was developed and tested on a Photon Q but should work on all moto_msm8960 devices with CM11.
I cannot be held responsible if anything goes wrong while using this mod.
Thank you to everyone this work is based on: Cyanogenmod team for providing CM11, Google for providing Android and everybody else
Download
I will try to keep this thread updated and provide a flashable zip for the latest CM11 snapshot.
See attachment at the bottom.
Regards,
Simon
Downloads for:
cm-11-20140609-SNAPSHOT-M7-moto_msm8960.zip
cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip
cm-11-20140916-SNAPSHOT-M10-moto_msm8960_jbbl.zip cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip
cm-11-20141112-SNAPSHOT-M12-moto_msm8960_jbbl.zip

Cool, Thank you

Any updated version for CM11 M8 build?

I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.

S-I-M-O-N said:
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
Click to expand...
Click to collapse
Yeah..I've tried it over M8 and my phone stucked in bootloop. Thanks for your work. I've missed my sdcard as primary storage since JellyBean days. I'm glad I can use my 32gb sdcard usefully.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app

Download for M8 added.

S-I-M-O-N said:
Download for M8 added.
Click to expand...
Click to collapse
Thanks a lot..Downloading it now.

Hmm so I'm guessing the likelihood of this working on nightly builds isn't good?

You could give it a try.
Nandroid backup boot and system, then flash the mod.
If it screws up, just go back and restore boot and system.
Apart of that I think we should wait a few days to see if we get a moto_msm8960_jbbl M9 build. If yes I will, make the patch for it. If no, I will pick the latest nightly.

After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon

Please...!
A new version.
The M10 CM is out now for the Photon Q!
S-I-M-O-N said:
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Click to expand...
Click to collapse

Download for M10 added. Have fun!

Download for M11 added. Enjoy!

Are there any issues with this mod when flashing a new ROM? Say you're going from a snapshot build to a newer snapshot build, or even from a snapshot build to to a stable build?

Flashing a new ROM will overwrite the mod. So you are using the emulated sdcard on internal memory. Apps which stored data on the sdcard will not find their data, just like when you install the mod the first time.
Nevertheless if you stick to CM11 snapshots for which the mod has been adapted and you flash another release, just flash the mod for this release while you are still in recovery and you will have no problems.

Made the mistake of installing a nightly restored my backup. But can't get the classic sdcard back. Have re flashed no joy. Is there a way to get it back, with out doing a clean install?

Did you create the backup including the mod?
Did you restore system and boot?
Did you try to just flash CM11 M11 + MOD for M11?
Do you have bootloops?

YDid you create the backup including the mod?
No
Did you restore system and boot?
Not sure about the boot, will check.
Restored backup m11 and flashed sddcard mod.zip.
Do you have bootloops?
No
Might be a mute point.
The restore is eating my battery!
Doing a clean m10 updating to m11 Now.
Will install sdcard mod and see how it goes.
Thanks.
I should know here in the next 15 min.
OK!
With out flashing sdcard mod after m11 installed I now have
4 gig.
My guess is my back up was not m11 or JB bootloader?
Thanks for the fast reply!

The PQ has no KK bootloader, so every (working) ROM for the PQ is based on the JB bootloader.
As long as you haven't modified your /system after updating to M11 and flashing gapps and sdcard_mod, you should be fine by just do the same again.
But it's always risky, from a nightly to a snapshot. Downgrades are also risky and might not work.
You might just wait until M12 comes out and use your backup to restore it.

M12 is here