Develop Bugs

[MOD] GT-S5660M Stock & CWM Recovery 5.x [Update: Feb.27.12]

You can find all the features and info here: http://goo.gl/B0qqW
===========Gingerbread GT-S5660M Stock Recovery===========
These are the things I changed:
Code:
default.prop (lifted security)
=======================
Changelog:
Code:
March.1.12 ~ Added Odin file
[B]===================[/B]
Feb.27.12 ~Major Update!
• Fixed All Recoveries's update-binary
• Added Phiexz and Maclaw Roms compatible Recoveries [B](Only Flash if you are flashing their ROMS)[/B]
• My Recoveries named: [B](My Roms)[/B] are only compatible with [B]My Roms![/B]
[B]===========================[/B]
Feb.26.12 ~[B]Added CWM 5.0.2.6[/B]
Feb.26.12 ~Corrected CWM 5.0.2.7's [B]updater-script[/B]
Feb.23.12 ~[B]More Stable![/B]
Feb.12.12 ~Initial Release[/FONT][/SIZE]
Thanks to Darkshado for always giving me tips!
Thanks to Phiexz's for his hard work! (CWM credit to him)
(Phiexz & Maclaw Roms) ClockWorkMod Recovery Modded GIO.RLE ONLY:
px-CWM-v2.zip
ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
ClockWorkMod 5.0.2.6 No EXT Support (MORE STABLE THAN 5.0.2.7) (Hyriand)
(My Roms) ClockWorkMod Recovery Modded GIO.RLE & Build.prop ONLY:
ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
[ODIN]ClockWorkMod 5.0.2.7 ext+rfs [ODIN] (Phiexz)
ClockWorkMod 5.0.2.6 No EXT Support (MORE STABLE THAN 5.0.2.7) (Hyriand)
Stock Recovery
GT-S5660MUGKG3 Stock Recovery (Samsung and I )
READ READ READ:
Not every Installable zip can handle mount system, data & cache.
so you should mount it manually before flash them. mount menu can found on: Mount & Storage Menu
EXT4 FORMATTER (S5660M Mod) (Phiexz)
Galaxy Gio ext4 converter (Darkshado)
*Tested and working on my own Canada phone!
*All zips are signed*​

can you help me about building a cwm recovery for i569？
Sent from my GT-S5660

Well for sure you need Linux. You also need a lot of space on your Drive.
Is it for Stock or Custom Rom (Like CM7)
Try checking this out: Build a custom kernel and [HOWTO] Build custom kernel, libraries and applications on your own
Make sure you're using the right/recommended toolchain but if you pulled directly from the AOSP repo then i guess that's not your problem.

thank you for cwm recovery for 5660m but when I try to clear dalvik cache it reset back to home screen

Peteragent5 said:
Well for sure you need Linux. You also need a lot of space on your Drive.
Is it for Stock or Custom Rom (Like CM7)
Try checking this out: Build a custom kernel and [HOWTO] Build custom kernel, libraries and applications on your own
Make sure you're using the right/recommended toolchain but if you pulled directly from the AOSP repo then i guess that's not your problem.
Click to expand...
Click to collapse
thank you my friend,i will learn it later！
Sent from my GT-S5660

zman4753 said:
thank you for cwm recovery for 5660m but when I try to clear dalvik cache it reset back to home screen
Click to expand...
Click to collapse
That means the Dalvik Cache is cleared even though it doesn't show it
Trust me.

Peteragent5
This customization is much appreciated however I still have two bugs:
1- I can’t mount the sd-ext (I’m using ext2 partition for link2sd); everything else were mounted correctly (cache, system, data and SD )
2- In the last step of backup I had an error when trying to generate the md5 sum (error while generating md5 sum!)
Any thoughts?
Thanks
-----------------------
Darkshado’s great Rom Already installed (ArpegGioMod ROM v0.8) on S5660M

1- Weird.. Try checking the original post and ask for help there or search your problem there
2- Did you try backing up just once or multiple times? Try backing up more than once. I had same problem even without my mods. But i tried what I said above and it works. If it still doesn't work ask in the original thread also and/or search on google

Peteragent5 said:
1- Weird.. Try checking the original post and ask for help there or search your problem there
2- Did you try backing up just once or multiple times? Try backing up more than once. I had same problem even without my mods. But i tried what I said above and it works. If it still doesn't work ask in the original thread also and/or search on google
Click to expand...
Click to collapse
Thank you for the quick response:
1- It's what I did but don't get any response yet.
2- I tried backup for multiple times but bug in the same step md5
Thanks

All right it seems like there's some Bugs with this modded cwm. I'll try to find the problem and fix it Thanks for posting bug

EDIT~
It seems when I Backup on my own phone (without any fix yet), it seems to work!? Keep in mind I also have no SD EXT.

Updated to much stable Recovery

Peteragent5 said:
Updated to much stable Recovery
Click to expand...
Click to collapse
The file on mediafire has the same name... Is this the updated one? Thanks.

koodiifin said:
The file on mediafire has the same name... Is this the updated one? Thanks.
Click to expand...
Click to collapse
Yes it is. Too lazy to rename

Changed file name.

mobilis2009 said:
Peteragent5
This customization is much appreciated however I still have two bugs:
1- I can’t mount the sd-ext (I’m using ext2 partition for link2sd); everything else were mounted correctly (cache, system, data and SD )
2- In the last step of backup I had an error when trying to generate the md5 sum (error while generating md5 sum!)
Any thoughts?
Thanks
-----------------------
Darkshado’s great Rom Already installed (ArpegGioMod ROM v0.8) on S5660M
Click to expand...
Click to collapse
Peteragent5,
I just tested Nandroid backup with your CWM and ArpegGioMod 0.8 and I also get "error while generating md5 sum!". I tried it multiple times.
You mentioned that it works on your phone, but were you testing it with an EXT4 base system or RFS?
Nandroid backup with your CWM on a Ext4 system worked fine for me, but not RFS.

koodiifin said:
Peteragent5,
I just tested Nandroid backup with your CWM and ArpegGioMod 0.8 and I also get "error while generating md5 sum!". I tried it multiple times.
You mentioned that it works on your phone, but were you testing it with an EXT4 base system or RFS?
Nandroid backup with your CWM on a Ext4 system worked fine for me, but not RFS.
Click to expand...
Click to collapse
I actually was testing on RFS lol
My backups work fine?

S5660=S5660M ?
[Sent to the mobile device Gio]
[aOS 2.3.7/CM7.2-RC2-B4 patch1]

Update again! View change log!
Change Log & Original Post

m.ali.ozkaya said:
S5660=S5660M ?
[Sent to the mobile device Gio]
[aOS 2.3.7/CM7.2-RC2-B4 patch1]
Click to expand...
Click to collapse
S5660!=S5660M
Use the search function, it's well documented you oafish troll.

[RECOVERY][CWM] ClockworkMod v6.0.2.7 Touch v14.4.6 | exFAT support (01/11/13)

IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh (updated to fix typo)
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh skyrocket
- it will reboot you into recovery
- starting in v14.2.1 it will automatically start installing and reboot when its done
Note: If your sdcard is not mounted on /mnt/sdcard then open the script and change the line that says path=/mnt/sdcard/sk8sUpdater to match your mount point. i.e. ICS users may have to change it to say path=/mnt/emmc/sk8sUpdater
Click to expand...
Click to collapse
I have ported touch recovery to Clockworkmod 6. I will be making updates to this just like my other touch recovery. I have added a few menu items and tweaks to make it like my CWM5 recovery.
Looking through the cwm code more in depth i have noticed MANY flaws with the code for new(er) phones that use /emmc instead of /sdcard as the main storage. i have now fixed those flaws in v9+.
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.6_hercules.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
[/CODE]
Current Version:
v14.4.6
- added exFAT support
- some under the hood optimizations
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.

Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking)

hellz yes!!!
Sent from my SGH-T989 using xda premium

Thank you and welcome back brother!

Thanks buddy! will report if I come across any bugs

Working great and looks beautiful do u recommend to do the hide the progress option or to not?

casonswag said:
Working great and looks beautiful do u recommend to do the hide the progress option or to not?
Click to expand...
Click to collapse
its up to you. if you want to know how far along the progress is then show it. but itll take a little bit longer to backup. or if you dont care about how far along you are and just want it to be done in the fastest time possible then hide it.

when i go into cwm it says read only file system...?...how do i fix that...cause my system is monted and my sd card is mounted...pleasse help...thanks in advance...

ooo this is sweet , thanx, now i can delet the other thread and leave
only the non-touch version!

if your .android_secure folder lives on your external sdcard then download this file -----------> [url said:
http://d-h.st/PdV[/url]
Click to expand...
Click to collapse
I do see that folder in my external, micro sd right?? So, i just need this file only?? Its the recorvery itself..??
Sent from my SGH-T989

phordych05 said:
when i go into cwm it says read only file system...?...how do i fix that...cause my system is monted and my sd card is mounted...pleasse help...thanks in advance...
Click to expand...
Click to collapse
can you please explain more? what are you trying to do when it says read only file system? are you trying to adb something to your system partition? you need to remount it as rw before you can put something there. thats always the case.
noodles2224 said:
I do see that folder in my external, micro sd right?? So, i just need this file only?? Its the recorvery itself..??
Sent from my SGH-T989
Click to expand...
Click to collapse
yes if you have .android_secure in /sdcard then download the secondary one

I hate to be "that guy" who asks this question, but...
Will this play nice with installing the various ROM's for this phone? Although I have never personally had a problem with installing any ROM's on the various recoveries, people always report problems with certain combinations.

I downloaded this last night and used it right away... This takes waaaay too long to do a backup. Close to 15 mins... too long for me

TWRP all day, everyday. Why bother with prehistoric recoveries.

tikay00 said:
TWRP all day, everyday. Why bother with prehistoric recoveries.
Click to expand...
Click to collapse
Dude why are you going to every thread Trolling making nonsense comments thats not needed ?

sk8erwitskil said:
can you please explain more? what are you trying to do when it says read only file system? are you trying to adb something to your system partition? you need to remount it as rw before you can put something there. thats always the case.
yes if you have .android_secure in /sdcard then download the secondary one
Click to expand...
Click to collapse
Well i have it in /sdcard/external_sd not just /sdcard. Still download the second one right? Sorry but with this samsung internal and external, sometimes just saying sdcard is a little confusing..
Sent from my SGH-T989

scribbles92 said:
I downloaded this last night and used it right away... This takes waaaay too long to do a backup. Close to 15 mins... too long for me
Click to expand...
Click to collapse
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
noodles2224 said:
Well i have it in /sdcard/external_sd not just /sdcard. Still download the second one right? Sorry but with this samsung internal and external, sometimes just saying sdcard is a little confusing..
Sent from my SGH-T989
Click to expand...
Click to collapse
correct. because /sdcard/external_sd is how your OS mounts it. but in recovery it will be mounted as /sdcard. for samsung devices the stock way to mount storage is: internal = /emmc, external = /sdcard. depending on what rom you use though the developer of that rom may change the way that the OS mounts it because he prefers a different way. but in recovery i set it to be internal = /emmc, external = /sdcard

tikay00 said:
TWRP all day, everyday. Why bother with prehistoric recoveries.
Click to expand...
Click to collapse
cool story, bro

sk8erwitskil said:
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
Click to expand...
Click to collapse
Oh ok, thanks sk8er... I was looking for another recovery and hadn't read up on it so... maybe I will give this another shot. (I'm actually coming from your other recovery -CWMR 5.5.0.4)

sk8erwitskil said:
thats already been talked about. the first backup takes longer because of the dedupe format. incremental backups are much quicker. do a google search for koush dedupe clockworkmod 6 and youll see. i dont have the energy to explain it again.
correct. because /sdcard/external_sd is how your OS mounts it. but in recovery it will be mounted as /sdcard. for samsung devices the stock way to mount storage is: internal = /emmc, external = /sdcard. depending on what rom you use though the developer of that rom may change the way that the OS mounts it because he prefers a different way. but in recovery i set it to be internal = /emmc, external = /sdcard
Click to expand...
Click to collapse
I hate to ask this but how do I know if it's located there or not?
Sent from my SAMSUNG-SGH-T989 using xda premium

[RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-08]

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.
Link: TWRP 2.6.0.0 LS970 FLASHABLE
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.
OTHER DOWNLOAD METHODS:
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
THANKS TO :
Dees_Troy
TWRP TEAM
AutoPrime
not trying to jack posts but we didn't get any love... :crying:

Just an FYI/Headsup.
Encryption does not restore data. If you restore an encrypted backup, it'll fail. And when you bootup, you'll have system with no data. I just tried this.
---------- Post added at 02:22 PM ---------- Previous post was at 02:07 PM ----------
Compression seems to work now though.

I don't understand why after all these updates, it still labels the folders with the wrong date...from before the internet even existed lol. Now the button to change the name of the file right before you start the backup is gone, so I'll have to rename it later. Just curious, figured it would have been fixed a couple updates ago. But I do appreciate you doing what you do...makes life much easier for us who can't.

stealth919 said:
I don't understand why after all these updates, it still labels the folders with the wrong date...from before the internet even existed lol. Now the button to change the name of the file right before you start the backup is gone, so I'll have to rename it later. Just curious, figured it would have been fixed a couple updates ago. But I do appreciate you doing what you do...makes life much easier for us who can't.
Click to expand...
Click to collapse
Press the name button at the top. It got moved because of encryption, i think. As for the date, i get about 75% of the dates right. Very strange.
Sent from my LG-LS970 using xda premium

OK cool I'll try that next time I'm in there. Yeah mine likes 1970 lmao, before I was even born.

is there another way to install this? seems that all of a sudden my 2.5 wont even see the flash file, for this and even some kernels i tried to flash

Goomanager, says there is no recovery available for my device. Im currently on Dirty Unicorns.
How did you guys update from TWRP 2.5 to TWRP 2.6?
Did anybody use GooManager or did your flash the file above?

EFEXR said:
Goomanager, says there is no recovery available for my device. Im currently on Dirty Unicorns.
How did you guys update from TWRP 2.5 to TWRP 2.6?
Did anybody use GooManager or did your flash the file above?
Click to expand...
Click to collapse
I always noticed goo was behind the times for the lgog. so i just go to the twrp site and grab the file.

Help
Hello Guys, I by accident formatted the phone. I Have functioning TWRP, but I have no idea as to how get a flashable zip to the phone any pointers.
thanks

nemssn4cer said:
Hello Guys, I by accident formatted the phone. I Have functioning TWRP, but I have no idea as to how get a flashable zip to the phone any pointers.
thanks
Click to expand...
Click to collapse
Here is the help you seek. http://forum.xda-developers.com/showthread.php?p=36270473
Sent from my LG-LS970 using xda premium

Engine, thank you for the assist
Sent from my LG-LS970 using xda premium

nemssn4cer said:
Engine, thank you for the assist
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Anytime. Glad to help.
On another note, I think I found more flaws in 2.6.0.0
While it WILL make Backups, and Restore just fine, It WILL NOT save the TWRP files to your computer. It backs up boot.emmc.win and boot.emmc.win.md5, but nothing else.
I'm alittle paranoid with this phone for messing things up. So I back up EVERYTHING I can to my computer to save my as$.
Just another FYI
EDIT. Reinstalling 2.6.0.0 still has same problem.
Installing 2.5.0.0 works as it should. So back to 2.5.0.0 for me

Thanks!!
sent from my fingers to your face.

engine95 said:
Anytime. Glad to help.
On another note, I think I found more flaws in 2.6.0.0
While it WILL make Backups, and Restore just fine, It WILL NOT save the TWRP files to your computer. It backs up boot.emmc.win and boot.emmc.win.md5, but nothing else.
I'm alittle paranoid with this phone for messing things up. So I back up EVERYTHING I can to my computer to save my as$.
Just another FYI
EDIT. Reinstalling 2.6.0.0 still has same problem.
Installing 2.5.0.0 works as it should. So back to 2.5.0.0 for me
Click to expand...
Click to collapse
In addition to that, it seems that TWRP backups on 2.6.0.0 are saved somewhere other than where they are usually saved, i cant seem to even find the new backups on the sd card. but now that you mention it i should also start backing up to my computer on account of my battery recently got fried and i lost all my hard work when i had to get a new phone sucks not having a micro sd card or removable battery

kMogs17 said:
In addition to that, it seems that TWRP backups on 2.6.0.0 are saved somewhere other than where they are usually saved, i cant seem to even find the new backups on the sd card. but now that you mention it i should also start backing up to my computer on account of my battery recently got fried and i lost all my hard work when i had to get a new phone sucks not having a micro sd card or removable battery
Click to expand...
Click to collapse
It is a pain not having and sd, no doubt. All the more reason to copy to the computer also.
Anyway, do you have the"0" folder? My backups were in the same location. But I also run both Stockish and CM Roms. So TWRP always backs up to the same location. Have you recently started running CM Roms?
Sent from my LG-LS970 using xda premium

engine95 said:
It is a pain not having and sd, no doubt. All the more reason to copy to the computer also.
Anyway, do you have the"0" folder? My backups were in the same location. But I also run both Stockish and CM Roms. So TWRP always backs up to the same location. Have you recently started running CM Roms?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
I do have the 0 folder but i run cm roms pretty exclusively only flash to stock if absolutely necessary. anyhow i finally found the backup location for 2.6 in /data/media/TWRP . hope this will help others looking for it as i was. on a side note i heard that if you adb pull the backup to your computer you may not get permission issues and it should copy all the files from the backup. i havent tried it tho

[RECOVERY][CWM][2013-12-20][SS] Stock kernel with CWM 6.0.4.5 [Unlocked BL]

I just built a new CWM recovery from source and have it combined with stock kernel and ramdisk.
This image contains the kernel from Build 15.1.C.2.8 (dumped from C1905), the stock ramdisk, the CWM ramdisk and a custom root to select which system to boot.
Please backup your data before proceeding! I am not responsible for any data loss!
I've tried on my own Xperia M (C1905) and it can boot, but I haven't tried to restore a backup. You are warned! Not tested on C1904, but it should work though I cannot guarantee anything.
** You need unlocked bootloader to use this. Before you unlock the bootloader, you need to backup all your data and remove the SD card because everything will be deleted! **
Known problems:
If you mount /data, you cannot unmount it from the interface (the CWM code is designed to not allow unmounting it). You can, though, execute `adb shell umount /data` to unmount it if you really do need to.
(Only applicable to CWM 6.0.3.7) There is no "mount USB storage" (connect SD card to computer) function.
Install instructions (skip to step 5 if you already unlocked bootloader, rooted and installed busybox):
Install the latest Android SDK platform tools on your computer.
Root: http://forum.xda-developers.com/showthread.php?t=2457174
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598 (do this if you want to relock in the far future)
Unlock bootloader: All data will be lost! SD card will be formatted!
Download the attached zip and extract the boot image.
Power off your Xperia M, hold the Volume Up button and connect USB cable, release button when blue LED is on.
Execute:
Code:
fastboot flash boot combined-xperia-m-boot.img
Wait for it to show finished.
Disconnect USB cable.
Boot instructions:
Power off your Xperia M.
Power on by holding the power button. Your Xperia M should vibrate once like normal boot
Note that when the LED turns pink, press Volume Up once (no need to hold down).
LED should then turn cyan
You have booted into CWM!
Report bugs here!
Thanks:
CyanogenMod and ClockworkMod for obvious reasons[/url]
Also: Pack any Xperia M kernel with CWM
Check this tool: http://forum.xda-developers.com/showthread.php?t=2481864
Technical information:
The Xperia M doesn't have a recovery partition, therefore the recovery is packed into a boot image. There is an init script which checks whether it should boot into recovery, and if it should, the script will extract the recovery ramdisk and boot it. Otherwise it will extract the boot ramdisk and boot Android normally. The packer linked above is designed to pack the boot image.
Changelog:
2013-12-20
Updated to CWM 6.0.4.5
For whatever reason, mounting sdcard as USB storage now works.
Busybox mount now works like typical CWM
The kernel has kexec-hardboot support
Brightness is tuned down so that it won't hurt your eyes that much in bed
2013-11-15
Updated kernel and ramdisk with the one from firmware 15.1.C.2.8
2013-10-19
Compiled with cm-10.2 sources, CWM 6.0.4.4
Major changes in partition table format to allow CWM 6.0.4.4
Allow mounting external USB storage (using OTG cable) so backup can be stored on USB flash drives
2013-10-15b
Fixed screen shift issue!
2013-10-15
Use the zimage of the stock kernel instead of the uncompressed kernel
2013-10-14
Updates init script
Recompiled recovery to use device-specific key mapping (camera focus key = back)
Click to expand...
Click to collapse
Source code:
Device files: https://github.com/alvinhochun/cyanogenmod_device_sony_nicki (Note: CWM 6.0.4.4 is built using the `cm-10.2` branch)
cm-10.1 branch only tested on cm-10.1, cm-10.2 branch only tested on cm-10.2
Also, I don't update the cm-10.1 branch anymore...
Prebuilt kernel is extracted from stock ROM.
Kernel source: https://github.com/alvinhochun/sony-xperia-m-kernel
To build, use `lunch cm_nicki-eng` and then `make combinedimage`. Boot image is output as `combined.img`.
If you want to use your custom kernel and ramdisk, simply replace `kernel` and `stock-boot-ramdisk.gz`.
Extra notes:
***: as obvious as the filename
combined-xperia-m-boot-2013-10-19.img.zip is the newer CWM 6.0.4.4 version, with kernel/ramdisk from 15.1.C.2.8.
combined-xperia-m-boot-2013-10-15b.img.zip is the older CWM 6.0.3.7 version.

The combined boot image is updated. Please check the first post.

Thanks it's very useful, i've tried first version without light notify.

Jack.daniel said:
Thanks it's very useful, i've tried first version without light notify.
Click to expand...
Click to collapse
You're welcomed. No need to say thanks, just press the "Thanks" button of the post.

I've fixed the screen shift issue! Please flash the new version!

i find problem when backing-up data
when the backup almost done, error notif suddenly appear
"error while making backup image of /data"

xzn said:
i find problem when backing-up data
when the backup almost done, error notif suddenly appear
"error while making backup image of /data"
Click to expand...
Click to collapse
Did you choose to backup to sdcard or external sd? Only external sd will work. "sdcard" will not work because it is actually the internal storage.

xzn said:
i find problem when backing-up data
when the backup almost done, error notif suddenly appear
"error while making backup image of /data"
Click to expand...
Click to collapse
u should have did it in internal sd card. external will work fine!

alvinhochun said:
Did you choose to backup to sdcard or external sd? Only external sd will work. "sdcard" will not work because it is actually the internal storage.
Click to expand...
Click to collapse
thanks, its work :good:

I noticed some issue with recovery, when I enter recovery from Advance Power Menu, I can't reboot onto system anymore, I tried anyways, reboot system, power off, reboot to bootloader (on this way device entering fastboot mode). This issue dissapear when I wipe cache & dalvik-cache.
for notice, i use recovery that packed on ElixER1.0 kernel, not tried Elixer1.3 yet because there is some bug on wi-fi.
Sorry for my bad English

AyamPushUp said:
I noticed some issue with recovery, when I enter recovery from Advance Power Menu, I can't reboot onto system anymore, I tried anyways, reboot system, power off, reboot to bootloader (on this way device entering fastboot mode). This issue dissapear when I wipe cache & dalvik-cache.
for notice, i use recovery that packed on ElixER1.0 kernel, not tried Elixer1.3 yet because there is some bug on wi-fi.
Sorry for my bad English
Click to expand...
Click to collapse
Yeah, if whatever tool creates `/cache/recovery/boot` to trigger enter recovery, for once the script won't work because it didn't remove that file afterwards.
But I remember I've already fixed it in a previous version. Are you using the latest version?
Sorry about that. I was constantly fixing bugs and had released a few version of the CWM files. Even I myself may have messed up some files, so if you notice that the problem is still there in the newest version, please inform me of that.

alvinhochun said:
Yeah, if whatever tool creates `/cache/recovery/boot` to trigger enter recovery, for once the script won't work because it didn't remove that file afterwards.
But I remember I've already fixed it in a previous version. Are you using the latest version?
Sorry about that. I was constantly fixing bugs and had released a few version of the CWM files. Even I myself may have messed up some files, so if you notice that the problem is still there in the newest version, please inform me of that.
Click to expand...
Click to collapse
I use that I got from ElixER1.0 kernel package, so I didn't try newest version ( on ElixER 1.3 I tought), because I backward to ElixER 1.0
Let wait for icoolguy1995 fix the kernel and I will tell you

Does anyone know if CM is being ported???
Sent from my C1905 using xda app-developers app

7lucky7 said:
Does anyone know if CM is being ported???
Sent from my C1905 using xda app-developers app
Click to expand...
Click to collapse
Yes
Sent from my Sony Xperia M (C1905)

I've compiled a CWM 6.0.4.4. This version supports mounting external USB storage connected via an OTG cable, so if you don't have a big SD card you can use an USB flash drive to perform backup.
But still, I haven't tested the restore function of this CWM yet, so if someone tried it please report back.

tried the new one. looks clean tried taking a backup, worked perfectly. dint try restoring yet.
y the storage/sdcard0 storage/sdcard1instead of internal and external storage?

ramprasad5394 said:
tried the new one. looks clean tried taking a backup, worked perfectly. dint try restoring yet.
y the storage/sdcard0 storage/sdcard1instead of internal and external storage?
Click to expand...
Click to collapse
The internal storage is `sdcard0` and the external is `sdcard1`, while the USB storage is `usbstor0`. I am not sure how I am supposed to do that, I just referred to some other devices and that is what it seems to be, although none of the devices I've looked into actually has the internal storage.
I dug into the code a little bit and it seems that what I did should be fine, so I did it this way.
It may require some modifications before it can be used with CyanogenMod 10.2, but it currently works with CWM alone. It works anyway so I am going to stick with it at the moment.

plz provide for xperia m dual c2004..
thanks in advance.

alvinhochun said:
The internal storage is `sdcard0` and the external is `sdcard1`, while the USB storage is `usbstor0`. I am not sure how I am supposed to do that, I just referred to some other devices and that is what it seems to be, although none of the devices I've looked into actually has the internal storage.
I dug into the code a little bit and it seems that what I did should be fine, so I did it this way.
It may require some modifications before it can be used with CyanogenMod 10.2, but it currently works with CWM alone. It works anyway so I am going to stick with it at the moment.
Click to expand...
Click to collapse
Tried restoring nandroid, worked perfectly

Can I flash your recovery on my C1904 running C2005 4.2.2 firmware?

Twrp.3.1.0-0 ??? Just a few questions....

So the newly released twrp 3.1.0-0 has been released and i was wondering if it will be better than my unreleased twrp 3.0.4-1 and in better i mean will it be more compatible and stable with nougat on oneplus 3 , i chose version 3.0.4-1 because everyone seemed to be having problems with the official versions if anybody has any knowledge about this new recovery then please comment , here is a list of updates to the new twrp -
Vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
ADB backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
Tweak MTP startup routines (mdmower)
Support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
Support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
Better indicate to users that internal storage is not backed up (Dees_Troy)
Improve automatic determination of TW_THEME (mdmower)
Minimal getcap and setcap support (_that)
Try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
Shut off backlight with power key (mdmower)
Timeout during FDE decrypt (Dees_Troy and nkk71)
Support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
Boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
Support for AB OTA zips (Dees_Troy)
Support new Android 7.x log command (Dees_Troy)
Update recovery sources to AOSP 7.1 (Dees_Troy)
Numerous bugfixes and improvements by too many people to mention

OT : You sound like some random private channel Indian reporter..

sarus_b said:
OT : You sound like some random private channel Indian reporter..
Click to expand...
Click to collapse
Hahahaha i don't know how on earth you came up with that assumption but no i am a white male that lives in the UK...

I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...

Xceeder said:
I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...
Click to expand...
Click to collapse
Are you using F2FS for data and cache? Also pls report if first boot of new 3.1 TWRP has wiped Internal storage files (/sdcard) like it did for many using f2fs for data..

arvindgr said:
Are you using F2FS for data and cache? Also pls report if first boot of new 3.1 TWRP has wiped Internal storage files (/sdcard) like it did for many using f2fs for data..
Click to expand...
Click to collapse
I had that issue but it only happened when I used open gapps. They seem to be having a lot of issues with this device.
EDIT: Nope, it happened using dynamic gapps too. Has happened on multiple ROMS, must be a TWRP/F2FS issue.
Double Edit: Happened on EXT4 as well.

JohnHorus said:
I had that issue but it only happened when I used open gapps. They seem to be having a lot of issues with this device.
Click to expand...
Click to collapse
Seems unreleased 3.0.4 is really stable on Nougat F2FS devices., Until update for official 3.1 comes fixing those issues, I'll stick with prev. version. Thanks for trying and posting here..

arvindgr said:
Seems unreleased 3.0.4 is really stable on Nougat F2FS devices., Until update for official 3.1 comes fixing those issues, I'll stick with prev. version. Thanks for trying and posting here..
Click to expand...
Click to collapse
Haha... yeah. Nah. It actually just happened for me using dynamic gapps, so forget about that. I had it happen all the time on Lineage, so I assumed it was Lineage at first. I switched to AOSP-Extended, and only had it happen once, when I tried using open gapps. I switched to dynamic gapps for other reasons, and it never happened in 4 or 5 flashes, so I assumed it was open gapps.
BUT it just happened to me, maybe 20 minutes after posting that, using AOSP-Ex and dynamic gapps. So at this point I'm like 100% positive it's this messed up TWRP, not sure if it's F2FS related or not as I've only ever used F2FS, but after this I may just start using EXT4.
Edit: AANNNDD it happened on EXT4 as well... at least it only happens during initial setup.

Xceeder said:
I am gonna go ahead and flash the new version if there are any problems with restoring nandroids or anything i will report back...
Click to expand...
Click to collapse
There shouldn't be any issues since 3.0.4-1 was developed by a member of TWRP team (jcadduono) specifically for the 3 and the 3T and TWRP seem to have merely polished it and posted it as 3.1.0
If you read the description of 3.1.0 on the TWRP site, you will see that it also mentions jcadduono as the developer.

JohnHorus said:
Haha... yeah. Nah. It actually just happened for me using dynamic gapps, so forget about that. I had it happen all the time on Lineage, so I assumed it was Lineage at first. I switched to AOSP-Extended, and only had it happen once, when I tried using open gapps. I switched to dynamic gapps for other reasons, and it never happened in 4 or 5 flashes, so I assumed it was open gapps.
BUT it just happened to me, maybe 20 minutes after posting that, using AOSP-Ex and dynamic gapps. So at this point I'm like 100% positive it's this messed up TWRP, not sure if it's F2FS related or not as I've only ever used F2FS, but after this I may just start using EXT4.
Click to expand...
Click to collapse
I only have the data partition as f2fs if that's any help and my device is not encrypted... As for the recent twrp it works fine with me i can back up and restore nandroids as well as flashing zip files..

tnsmani said:
There shouldn't be any issues since 3.0.4-1 was developed by a member of TWRP team (jcadduono) specifically for the 3 and the 3T and TWRP seem to have merely polished it and posted it as 3.1.0
If you read the description of 3.1.0 on the TWRP site, you will see that it also mentions jcadduono as the developer.
Click to expand...
Click to collapse
Yeah i thought everything would be fine i was just testing it for other people...