Defy officially doesn't have support for CWM Touch, who other devices have. However, there is a few devices with similar hardware with official support like Optimus Black.
Maybe with porting this, we can have a full compatibility with nandroids made by original CWM Recovery.
Right now, i have extracted ramdisk from CWM Touch Recovery, but really don't know which files a have to touch in order to port sucessfully to our Defy.
A little research about it, show me that i have to make changes in:
+ default.prop
+ init.rc
+ ueventd.goldfish.rc
+ ueventd.rc
+ /etc/recovery.fstab
* and, make a new uevent.moto.rc instead of ueventd.lge.rc
Someone wants to join on this project?
i'm attaching files from extracted ramdisk.
This might help aswell
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html?m=1
I will try and build one tomorrow with this guide since i already have the cm source
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
m11kkaa said:
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
Click to expand...
Click to collapse
But this will only work with ics??? The builder page said so...
Enviado desde mi MB526 usando Tapatalk 2
m11kkaa said:
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
Click to expand...
Click to collapse
oops my bad just realised it just for porting CWM if your device is not already supported .... thanks for the link m11kkaa...
espaciosalter20 said:
But this will only work with ics??? The builder page said so...
Enviado desde mi MB526 usando Tapatalk 2
Click to expand...
Click to collapse
Just flashed it and it works fine! I'm using ics with froyo kernel. It will work with any Rom because we only have froyo and gingerbread kernels. The version of cwm was 5.8.4.3. Remember that to use custom recovery you must launch it from the bootmenu, the reboot to recovery from the power menu launches the stable recovery.
Sent from my MB525 using Tapatalk 2
kadopt said:
Just flashed it and it works fine! I'm using ics with froyo kernel. It will work with any Rom because we only have froyo and gingerbread kernels. The version of cwm was 5.8.4.3. Remember that to use custom recovery you must launch it from the bootmenu, the reboot to recovery from the power menu launches the stable recovery.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I also installed the touch CWM recovery, it looks gud but not better than TWRP.
I tried to restore a nandroid made by normal cwm recovery but it showed MD5 mismatch, I restored the same nandroid with the help of normal recovery. It seems that more work needs to be done but its surely a very gud step forward.
m11kkaa said:
You can't compile Touch-CWM because source currently is not public.
But Koush made a Builder: http://builder.clockworkmod.com/
Ich made a CWM-Version for our defy with his builder and compiled it to an update-package for our lovely bootmenu
This replaces "Custom Recovery"... Have Fun!
Click to expand...
Click to collapse
You're right... it can't compile from source, but there is a workaround: Extract defy kernel from recovery.img of defy and modify the ramdisk that i provide, re-pack it in recovery.img with kernel extracted from defy recovery.img... That's why i was trying to modify the CWM official from another device.
Step by step to do this:
1. Use Linux
2. Get mkbootfs & mkbootimg
3. Get split_boot.zip
4. Grab a boot.img or recovery.img
5. Split it with following code:
Code:
./split_bootimg.pl recovery.img
Click to expand...
Click to collapse
6. Examine
7. You will have two new files based on whatever file name you gave above
kernel will have "-kernel"
YES this is the kernel (compressed) for this .img
you have successfully extracted the kernel
you cannot edit these
you can mix and match
if I know the kernel from older boot works I can just use it with my newly edited ramdisk
ramdisk will have "-ramdisk.gz"
feel free to rename
8. Unpack Ramdisk
Code:
mkdir ramdisk_recovery
cd ramdisk_recovery
gzip -dc ../recovery.img-ramdisk.gz | cpio -i
Click to expand...
Click to collapse
9. Examine
In all ramdisk you will have a few folders and files:
data
dev
etc
proc
res
images for recovery go here
sbin
the actually recovery binary goes here
also adbd
sys
system
tmp
default.prop
init
init.goldfish.rc
init.rc
init.yuhua.rc
init.yuhua.sh
initlogo.rle
10. Pack-up Ramdisk
Code:
mkbootfs ./ramdisk_recovery | gzip > ramdisk_recovery-edited.gz
Click to expand...
Click to collapse
11. Back to IMG
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel recovery.img-kernel --ramdisk ramdisk_recovery-edited.gz -o recovery-edited.img
Click to expand...
Click to collapse
use file good file names! Or you might end up with many test tries and cannot figure out what you did for each
Here you can mix and match kernels
12. Now Flash via recovery or something
All files are attached in zip.
espaciosalter20 said:
But this will only work with ics??? The builder page said so...
Enviado desde mi MB526 usando Tapatalk 2
Click to expand...
Click to collapse
its bootmenu recovery
will work on any system
Sent from my MB526 using xda premium
espaciosalter20 said:
You're right... it can't compile from source, but there is a workaround: Extract defy kernel from recovery.img of defy and modify the ramdisk that i provide, re-pack it in recovery.img with kernel extracted from defy recovery.img... That's why i was trying to modify the CWM official from another device.
Click to expand...
Click to collapse
You know that defy has locked bootloader and we can't boot modified boot/recovery-images?
m11kkaa said:
You know that defy has locked bootloader and we can't boot modified boot/recovery-images?
Click to expand...
Click to collapse
That's partially true. We can't boot modified boot img but it is possible with modified recovery img because we don't mess up with kernel or bootloader. Other Motorola locked devices gets cwm touch officially and even we can't have cwm if modified recovery img was not supported.
Enviado desde mi MB526 usando Tapatalk 2
1) I still don't understand what your "solution" has todo with the fact that the source of Touch-CWM is not public and we only have a web-based builder.
2) Currently we start CWM through bootmenu which works fine and I don't know why you want to modify the stock recovery-image.
However you can't modify the recovery-image in anyway because the complete image is signed, and not the kernel only
Just reporting .....works perfectly with multiboot....but still prefer twrp over this....!!!
Sent from my MB525 using XDA
m11kkaa said:
1) I still don't understand what your "solution" has todo with the fact that the source of Touch-CWM is not public and we only have a web-based builder.
2) Currently we start CWM through bootmenu which works fine and I don't know why you want to modify the stock recovery-image.
However you can't modify the recovery-image in anyway because the complete image is signed, and not the kernel only
Click to expand...
Click to collapse
Cwm touch is a custom recovery. So, I don't want to replace stock recovery. Only porting this custom recovery to our defy.
Enviado desde mi MB526 usando Tapatalk 2
@espaciosalter20 : can u please test the recovery posted by m11kkaa and test if you wanted to do the same?
brajesh.sharma87 said:
@espaciosalter20 : can u please test the recovery posted by m11kkaa and test if you wanted to do the same?
Click to expand...
Click to collapse
m11kkaa made that recovery using builder page of koushik (maker of cwm). I'm going to try it, maybe that "Touch Recovery will only work on ICS and later kernels." wich is stated in builder page, isn't accurate.
espaciosalter20 said:
m11kkaa made that recovery using builder page of koushik (maker of cwm). I'm going to try it, maybe that "Touch Recovery will only work on ICS and later kernels." wich is stated in builder page, isn't accurate.
Click to expand...
Click to collapse
well I checked it on multiboot and it worked with both cm7 and cm9.
however they might be some bug which is not confirmed at the moment.
Does clockworkmod touch have any extra features compared to original? (Apart from touch input ) I ask because I switched over to teamwin last week and love it! The compression option leaves so much more space on my sdcard after backups, also the zip queuing is great and wipes of any kind are faster. My only complaint is it flashes CM7 builds about half the speed clockworkmod does it, but still an awesome recovery, only other problem I guess is if I got a soft brick and had to flash sbf there's no way to install it which means I would have to flash it after flashing 2ndinit, which is one advantage of this if its ported properly as I could restore a backup faster when disaster strikes
Sent from the real world by hacking into the matrix
@non4 said:
Does clockworkmod touch have any extra features compared to original? (Apart from touch input ) I ask because I switched over to teamwin last week and love it! The compression option leaves so much more space on my sdcard after backups, also the zip queuing is great and wipes of any kind are faster. My only complaint is it flashes CM7 builds about half the speed clockworkmod does it, but still an awesome recovery, only other problem I guess is if I got a soft brick and had to flash sbf there's no way to install it which means I would have to flash it after flashing 2ndinit, which is one advantage of this if its ported properly as I could restore a backup faster when disaster strikes
Sent from the real world by hacking into the matrix
Click to expand...
Click to collapse
no extra feature, its all same only touch included.
and dont u have normal cwm recovery in stable recovery? AFAIK Twrp replaces the custom recovery only, isn't it true?
brajesh.sharma87 said:
no extra feature, its all same only touch included.
and dont u have normal cwm recovery in stable recovery? AFAIK Twrp replaces the custom recovery only, isn't it true?
Click to expand...
Click to collapse
Actually it's the custom recovery that stays as clockworkmod for me, I have the touch bootmenu. But I mean the kind of soft brick where only bootloader and stock recovery work, and I don't know any way to.install teamwin from stock froyo without having clockworkmod to flash it
Sent from the real world by hacking into the matrix
Related
Ray offerd server
Mirror
http://psychoray.com/MOTOROLA/모토로라 모토로이/ROM/컴자료실님 ROM/
Download The-FroyoMod
I ported CRT screen.
Camera doesn't work.
Please flash it on ClockworkMod Recovery.
My friend hyunwoo translated
My friend, we don't have ClockworkMod on the XT720. We only have OpenRecovery.
Nice porting though!
Hi good day nice port but must ask what motorio did you port ot on.
We usr open recovery to do are flashing.
It could work if you port motorio xt720 .
Let me know what you port this on.
Sent from my Milestone using XDA Premium App
sktjdgns1189 said:
Please flash it on ClockworkMod Recovery.
Click to expand...
Click to collapse
Do you have a link for the recovery?
it looks to me as update.zip
except that the updater script flash the boot.img... (so a handy backup of boot.img will be a good idea
missing system/persistent so i am not sure what will happen with openrecovery
elsewhere using sh_hijack, some interesting stuff in /system/etc/init.d ...
imho, the safest way to try it is to use the "sh" from openrecovery, and to insert in the zip the /system/persistent stuff from the open recovery (and the "reboot" binary too), and to remove the part of flashing of boot.img
edit:just noticed
Code:
dalvik.vm.execution-mode=int:fast
in the /system/build.prop , also dalvik heap is 29M
about memory
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,5120,7680,11520,14080 from init.maphone_umts.rc
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144 from init.rc
ClockworkMod Recovery for the Transformer TF101
NEW: Repack of Koush's touch clockworkmod recovery v5.8.1.8 to address the reboot to recovery issue.
This recovery is not mine and I take no credit for it. I only made a small change to the official recovery found here
and repacked it into a flashable zip.
Here is a diff of the hacky but working fix.
Code:
diff -Naur org/init.rc new/init.rc
--- org/init.rc 2012-04-02 21:18:24.875745175 +0100
+++ new/init.rc 2012-04-02 20:58:55.855745201 +0100
@@ -31,6 +31,8 @@
service ueventd /sbin/ueventd
critical
[COLOR="Green"]+service clearmisc /sbin/clear-misc.sh
+[/COLOR]
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
diff -Naur org/sbin/clear-misc.sh new/sbin/clear-misc.sh
--- org/sbin/clear-misc.sh 1970-01-01 01:00:00.000000000 +0100
+++ new/sbin/clear-misc.sh 2012-04-02 20:58:55.855745201 +0100
@@ -0,0 +1,4 @@
[COLOR="Green"]+#!/sbin/sh
+# This clears the boot flag from misc which forces
+# this device to continuously boot into recovery
+/sbin/dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13[/COLOR]
Even though these recoveries have been tested by me, I won't be responsible for any loss of data or any damages done by using it.
IF YOU ARE NEW HERE PLEASE READ THE NEXT LINE VERY CAREFULLY!
See here if you are having trouble with a recovery loop from another version of recovery...
Did you get that? Just in case please read it again before posting about not seeing recovery being updated!
Download
Touch Recovery v5.8.1.8 (repacked from official with the fix above)
MD5: 0b7f3c5986847e37c1dffcb53a9b79af
ClockworkMod Recovery v5.5.0.4 roach-tf101-r2
MD5: a352abf783746eb29a0f98159ca3c439
Changelog
v5.5.0.4 roach-tf101-r2
-Standard 5.5.0.4 recovery
-Installs from the Internal sdcard
-Tar backups (Not compatible with backups from version 3.2.0.1 and below)
-Power off option re-added as I find this useful
v3.2.0.1 roach-tf101-r1
- Fixed Dock keys (Left shift and Caps Lock were reversed)
- Added advanced backup from solarnz
- Tweaked mounts to improve performance
v3.1.0.1 (R3-240511-1908)
- Initial release for Asus Transformer
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method
Mod Edit:
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, be sure to reboot your transformer so it complete the flashing process.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credit: http://forum.xda-developers.com/showthread.php?t=1093818
Older versions
v3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1
Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that
gnufabio said:
Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that
Click to expand...
Click to collapse
I'm already on the case, the first post was just a taster of things to come.
Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer
hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards
Working towards rom manager support too?
Sent from my Transformer TF101 using XDA Premium App
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
brookfield said:
Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer
Click to expand...
Click to collapse
It's not currently backed up by CWM because the transformer has no /boot partition. There is however another way to back this data up so you will see this in a future update.
006fazer said:
hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards
Click to expand...
Click to collapse
I had the wrong link. fixed now.
Warboy said:
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
Click to expand...
Click to collapse
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
The ability to Install updated from the internal sdcard will be in the next version.
i download the good file, but upate don't work !
Roach, how did you compile it?
try this http://www.mediafire.com/?o4e36tmkd2xqb11
Roach made a small mistake making the update.zip. You simply have to rename /kernel folder to /recovery
Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App
love you roach!
Sent from my Transformer TF101 using XDA Premium App
david279 said:
Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I uploaded the wrong file lol, fixed now and MD5 updated. Apologies for the inconvenience
gnufabio said:
Roach, how did you compile it?
Click to expand...
Click to collapse
I used ubuntu.
Awesome nice to see Clockwork Recovery being updated. Maybe after you're done working on this one, you could port TeamWin Recovery Project over too for fun or something I used to use Clockwork on my phone but then made the switch to TWRP for a new feel.
Source for TWRP: https://github.com/TeamWin/Team-Win-Recovery-Project/
TWRP Image: http://forum.xda-developers.com/showpost.php?p=16130864&postcount=263
Overall, feels cleaner.
Aside from that suggestion rant, this version looks nice and looking forward to your additional updates for Clockwork Recovery. Hoping for ROM Manager support in the future.
Roach2010 said:
I used ubuntu.
Click to expand...
Click to collapse
I meant: did you used make or android's mm?
gnufabio said:
I meant: did you used make or android's mm?
Click to expand...
Click to collapse
Oh, Sorry. I used make. You will need to setup a full build environment if you want to compile recovery.
Those who struggle to get CWM recovery for thier newer devices and who are facing problem on romdump your stock rom to get stock recovery.img here you have 2 simple steps to get your CWM recovery for your new device
Step -1
Creating A Dump\Backup
Note: Root Required
1. Set "Settings" -> "Display" -> "Sleep" -> "10 minutes"
2. Install or update "Busybox" from play store
3. Set your phone to "Airplane" mode
4. Make sure that the card is not less than 2Gb of free space
5. Use any one of the following:
BakupTool_sdcard.zip saves a backup copy on the path: /mnt/sdcard/backup_v2
BakupTool_sdcard2.zip saves a backup copy on the path: /mnt/sdcard2/backup_v2
6. Extract the BakupTool_* to sdcard. Full path to the file should be: / sdcard / gscript
7. Install program: /sdcard /gscript /"GScriptLite.apk"
8. Open the program "GScriptLite". Press "Menu button" -> "Add Script"
9. Set tick "Needs SU"
10. Click "Load file" and select "back_mt657x.sh"
11. Click the button "Save"
12. Tap on a new script, "back_mt657x.sh". After that give the program root permissions if asked and wait for 5- 10 minutes. Do not use the phone during the process.
A sign of a normal shutdown of the script is:
Message in the terminal:
100% Backup Complite!!!
Saved to / sdcard/backup_v2/GGGGMMDD-ChChmm
Star Time: hh: mm: ss; End Time: hh: mm: ss
The appearance at the root of SD-card phone the following structure of folders and files:
backup_v2
YYYYMMDD-hhmm
* BDRS-YYYYMMDD-hhmm
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
* misk
cache.img
cmdline.info
config.info
cpu.info
nvram.img
nvram.tar
ram.info
rom.info
* over
expdb.raw
full_preloader_part.raw
misc.raw
pmt.raw
sec_ro.raw
seccfg.raw
unknown.raw
boot.img
dsp_bl.img
ebr1.img
firmware.info
MT6577_a4_v2c.info
logo.img
mbr.img
preloader.img
recovery.img
system.img
uboot.img
data.img
step - 2
upload your stock recovery.img to get cwm recovery
kaushik Dutta has developed a clockworkmod recovery builder on the official site....
http://builder.clockworkmod.com/
so upload your stock recovery.img and get exact cwm recovery.img of ur device....and flash it.
if yours is a new devicw please select new device column.
thanks for this awesome build.
- after u upload your stock recovery.img on clicking fro new device just click on Build icon on the last of the page.....
- then u will be qued and u will gwt build number please save it for further refference...
- click proceed to that server and find ur build number,,,if it finished successfully u will see green icon on the left
- then click on your build number then click status there u will get something like this
Project recovery
Last Successful Artifacts
android_device_lge_cayman.zip 5.12 MB
inputrecovery.img 16.00 MB
manifest.xml 53.95 KB
recovery.img 6.92 MB
finally download recovery.img which is ur cwm recovery and flash it via Mobileuncle MTK tools which can be downloaded from playstore
If something goes wrong u can revert back ur rom or stock recovery itself by flashing ur stock recovery.img from the back up folder...or u can flash ur rom back using SP FLASH tools
IF i helped u please press thanks :victory::victory::victory:
anybody tried???
meanwhile how to extract stock recovery.img from stock ICS
I did test it. The image build does boot for me. But the build recovery i got this way did miss some *.ko files my device needed
The site is not new by the way..
Read here how to dump you're recovery...
http://forum.xda-developers.com/showthread.php?t=1935162
Re: clockworkmod for newer devices - now get CWM recovery for every android
[email protected] said:
I did test it. The image build does boot for me. But the build recovery i got this way did miss some *.ko files my device needed
The site is not new by the way..
Read here how to dump you're recovery...
http://forum.xda-developers.com/showthread.php?t=1935162
Click to expand...
Click to collapse
Dumping rom is bit confusing....because I'm a dentist...
Can u please explain in simple steps to get stock recovery.img
I'm having intex aqua flash which is new in the market but it has all the feature of high devices...
One more thing can I do this in windows? Or should I need linux?
Sent from my Aqua flash using xda premium
Trying this right now. Hope the recovery.img from a stock nandroid works.
Re: clockworkmod for newer devices - now get CWM recovery for every android
McJesus15 said:
Trying this right now. Hope the recovery.img from a stock nandroid works.
Click to expand...
Click to collapse
Share in simple steps to extract stock recovery.img after u successfully get ur cwm
Sent from my Aqua flash using xda premium
Re: clockworkmod for newer devices - now get CWM recovery for every android
drganbds said:
Share in simple steps to extract stock recovery.img after u successfully get ur cwm
Sent from my Aqua flash using xda premium
Click to expand...
Click to collapse
My device is different. Technically I have cwm recovery already. It's just only accessible through a fast boot command. This allows me to have a nandroid back up already so I just took the recovery.img from a stock back up
Sent from my Zio using xda app-developers app
check this thread is updated...
I tried this for a Lenovo IdeaTab A2109 to try and build a touch recovery. It already has a unofficial cwm recovery non touch, so I used that as the recovery.img. It put out 2 recovery.img's. One was a recovery.img and the other inputreovery.img. I'm not sure what one I should flash or if I'm supposed to flash both. Would it put out errors if it didn't work?
Thanks for this post and any help you can give.
linsalata28 said:
I tried this for a Lenovo IdeaTab A2109 to try and build a touch recovery. It already has a unofficial cwm recovery non touch, so I used that as the recovery.img. It put out 2 recovery.img's. One was a recovery.img and the other inputreovery.img. I'm not sure what one I should flash or if I'm supposed to flash both. Would it put out errors if it didn't work?
Thanks for this post and any help you can give.
Click to expand...
Click to collapse
Inputrecovery.img is wat u uploaded and recovery.img is wat u get as cwm recovery.
Sent from my Aqua flash using xda premium
drganbds said:
Inputrecovery.img is wat u uploaded and recovery.img is wat u get as cwm recovery.
Sent from my Aqua flash using xda premium
Click to expand...
Click to collapse
Oh OK. What about the question I asked about errors? Will it give any errors if the recovery wont work?
Thanks for the quick reply.
linsalata28 said:
Oh OK. What about the question I asked about errors? Will it give any errors if the recovery wont work?
Thanks for the quick reply.
Click to expand...
Click to collapse
If it gives error like black screen or volume key unfunction means it is not compiled properly but don't worry your device won't brick and u can revert back ur recovery by placing original.img on the root of phone storage and flash through mobileuncle tool..all the best
Sent from my Aqua flash using xda premium
Three Questions and I'm gonna try this out:
1. If the CWM recovery I build from CWM builder doesn't work, can I flash back the stock recovery by Mobile Uncle Tools, I mean won't it brick the device, can I still boot? I have a MT6577 device.
2. Does the script provided here backups up the stock recovery on Ice Cream Sandwich?
3. What else does this script do? Backup the whole phone?
ApplePriest said:
Three Questions and I'm gonna try this out:
1. If the CWM recovery I build from CWM builder doesn't work, can I flash back the stock recovery by Mobile Uncle Tools, I mean won't it brick the device, can I still boot? I have a MT6577 device.
2. Does the script provided here backups up the stock recovery on Ice Cream Sandwich?
3. What else does this script do? Backup the whole phone?
Click to expand...
Click to collapse
1. Yes u can reflash you stock recovery back via mobile uncle tool
2. Yes it will work on ICS
3. I have shown that wat the backup folder will have...it does full backup of your phone....
Sent from my Aqua flash using xda premium
Okay, Thank you.
I will try and update you on this.
Edit: After flashing recovery, I got blank screen in recovery mode.
thanx mate , really a helpfu guide i have Xtouch x714 with Allwinner A13 chip
before i tried many A13 CWM none of them worked not even boot , they nearly damage my tablet
thank god there is Phoneixcard i was able to revive it .
Anyway , your methode of getting the recovery.img from [gscript] did not work for me , it kept give me errors
even though it shows 100% complete
so i used another method to get my recovery.img , hence my tablet is an Allwinner A13 chip, so
i used [ Rom Dump ] which a small and powerful tool run it in Windows from [ http://www.techknow.me ]
it uses ADB so u have to be rooted and enable developer mode in your device and have ADB drivers in your PC
it backup image of your system and boot.img , recovery.img and data
so i used the extracted recovery.img in the site you provide me and i got my new recovery.img and flash it to my tablet via NovoTools 1.0
and i test it , it works like charm , thanx again mate really helpful
step 2 no working....website down?
Black Screen
When I flashed recovery made through it, it gave me a black screen Is there any way to fix this??
the online one is not working
i tried twice for micromax a84... i got the CWM recovery and flashed it via mobile uncle tools...but it didnt work
?
after hitting "build" it states
your build has been queued.The
build id is
9b42b141e21a35c4007c250f45ab2039
continue to the build sever
view the current build output
when i hit either option i get "HTTP ERROR 404.
can anyone else see my build id and if so can you download it and link it to me via PM.
or what can i do to get my image
TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
About the current build:
STABLE.
Reboot to system bug now fixed.
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail
TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved
belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience
jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one
belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.
hi anyone have got it if possible in rar zip for this recovery.
ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail
Ok yesterdeay install with terminal emulator thanks.
*****Keep in mind that I or XDA or anyone else is not responsible for what happens to your device make sure you have a nandroid backup before proceeding
This is based on my personal experience I'm not a Dev
How to enable systemless root on mediatek !!!!
Step 1:
Get the booting of your phone via readback using spflashtool or dumping the ROM IMG !!
Step 2:
Unpack the boot IMG using mkbootimg or carliv IMG kitchen or Android kitchen !!!
Step 3:
Open the ramdisk folder and open the init.rc using notepad++
Step 4
Goto the line
Code:
export PATH /sbin:/system/bin:/system/xbin:/vendor/bin
**The line may vary but it will look similar !!!
Add the path of your su file at the end
Like I was t to install it at my data partition so
Add
Code:
:/data/bin
At the end of the line and save !!
Then change the permissions of /data/bin to 644 else apps won't be able to read the path due to insuffient permission !!!
Then repack the boot.img
Flash the bootimg via sp flash tool of flashify or any other method
Step 6:
***note use the su binaries of your CPU only
Like I used arm 7 binaries for my device !!
To know your CPU type
Download terminal emulator or use adb shell and type cat /proc/cpuinfo
Now using adb push copy the su file to the /data/bin folder or make a flashable zip to do the same !!
If you can't push via adb try doing it in adb supported recovery !!!
You might need to create the bin folder manually
And don't forget to set the permission to 0755 and reboot !!
Plz let me know if it works !!!
And also let me know if it doesn't !!!!
I can't post the flashable zip because I'm still new !!!
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
AlexZap said:
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
Click to expand...
Click to collapse
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
kirito9 said:
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
Click to expand...
Click to collapse
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
AlexZap said:
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
Click to expand...
Click to collapse
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
kirito9 said:
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
Click to expand...
Click to collapse
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
kirito9 said:
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
Click to expand...
Click to collapse
I think you need to read some more on how and why systemless root works and what it is for.
Regular root, the summer you installed, puts a bunch of binaries in the /system partition on your android phone, and while giving you root, it breaks a lot of things because it modifies the stock image, something that android doesn't expect to ever change except for system upgrades.
Systemless root fixes this. It does nothing to the system partition. It creates a mountable image and stores it in the /data partition that contains the su binary and whatever else is needed for root. It then modifies the boot image (the ramdisk that is packed with the kernel) so that on boot, it mounts this su image inside the already mounted system partition. This keeps the system partition stock, but at the same time, gives you root. Things like safetynet are unbroken and you can run things like android pay that check for a modified system image.
In order to do its magic, the systemless root installer has to be able to unpack and repack the boot partition. If you have a mediatek phone, you have about an 80% chance that your boot image is different then the rest of the android world. Mediatek phones have their own header in their images like boot and recovery (except for some very new devices). I am 95% certain that the systemless root installer does not know anything about mediatek headers. So it may unpack something, but clobber the boot image on repack. The author of this thread purports to have it working. I ask how. Is he one of the 20 or so percent without a mediatek header? Or did he do something else
AlexZap said:
.................
Click to expand...
Click to collapse
Yeah lol, first time working with android 6.0 and this systemless root. I know that's what the systemless root does, that's why after flashing the MT6580 device that I have, it didn't boot. Don't think the systemless supports this MT6580 as it uses it's own MTK header and not the standard AOSP.
Seems like OP as disappeared from this thread.
Sorry I took so long to respond
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
uttarayan21 said:
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
Click to expand...
Click to collapse
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Click to expand...
Click to collapse
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
uttarayan21 said:
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
Click to expand...
Click to collapse
I think magisk is better at handling boot image formats.
AlexZap said:
I think magisk is better at handling boot image formats.
Click to expand...
Click to collapse
I agree with @AlexZap and i am using it and it is working perfectly
Sent from my Z14 using Tapatalk
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
MalikDrako said:
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
Click to expand...
Click to collapse
magisk works flawlessly. no need to muck around, just flash it from twrp
Sent from my KFGIWI using XDA Premium 4 mobile app
AlexZap said:
magisk works flawlessly. no need to muck around, just flash it from twrp
Click to expand...
Click to collapse
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
MalikDrako said:
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
Click to expand...
Click to collapse
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
AlexZap said:
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
Click to expand...
Click to collapse
I just tried Carliv's image kitchen, and both boot and twrp port worked first try
How to change Permissions?
i could not understand it
can u help me Please?