Q&A for [DEV][RECOVERY] CWM-based RECOVERY 6.0.4.7
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][RECOVERY] CWM-based RECOVERY 6.0.4.7. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
thanks
this is the best recovery
CWM 6.0.4.7(Swipe Version) is functional
Thanks OP..now I can preserve the life of my hardware buttons saving it from early wear and tear.
Btw, can I also use the 'reboot to recovery' option in apps like ROM Manager, ROM Toolbox?
More Power!
Ook
Recovery Can't Mount
Hi guys, when I go into recovery mode appears these lines:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_og
E: Can't open /cache/recovery/last_log
Why?
Grateful!
Related
Q&A for [FIX]Enable encryption - Check&Shrink ext4 filesystem
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FIX]Enable encryption - Check&Shrink ext4 filesystem. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I had this problem for a looooong time. Thankfully, I seem to have discovered the solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)
Q&A for [DEV][ROM][ALPHA]CM 10.1 Asus MeMO Pad HD7 (MTK)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][ROM][ALPHA]CM 10.1 Asus MeMO Pad HD7 (MTK). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
issue
Hi, I'm new here. Can't find where to download file.
BSydz said:
INSTALLATION:
Flash in a custom recovery:
1. Copy zip to sdcard
2. Boot to recovery
3. Make backup
4. Install zip from sdcard
5. Select custom ROM zip
6. Accept install
7. Reboot
8. Enjoy!
Sideload after build:
In same terminal as the build
Code:
adb reboot recovery
In recovery:
Make backup in recovery if needed
Choose Install from sideload
Code:
adb sideload out/target/product/ME173X/cm-10.1-20140322-UNOFFICIAL-ME173X.zip
You will have to change the date according to the date of build.
Click to expand...
Click to collapse
Wifi problem
Does anyone hava problem with Wifi driver?
Will this work with the ME180A?
easy instructions? upgrade Memopad HD7 to Lollipop
I have never tried to modify an Android device before. My daughter has a password on her Memopad and doesn't know what it is. I tried to do factory reset but a No Command screen pops up. I would like to upgrade it to Lollipop, but I don't understand some of the terminology. Windows I know, but this is practically Greek to me. If I could do it connected to a PC that would be great. For some reason my MicroSD cards say they are write protected, but Windows says they need to be formatted, but says it can't do it. I even tried from Elevated Command Prompt.
Any helps or tips are appreciated.
Are you still in need of help?
dRumMzZ said:
Are you still in need of help?
Click to expand...
Click to collapse
Thanks, I'm good. Got the Memopad restored, sent my 2 SD Cards in for replacement.
When the cm 11 will be released?
Inviato dal mio GT-I9195 utilizzando Tapatalk
Q&A for [App]One Click Unroot[WIP]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [App]One Click Unroot[WIP]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Error
Indirect said:
I am proud to present you with: Nook Tablet Unrooter One click APP!
By Indirect​​
Information?: Well, the way to best unroot the nook tablet (as it's easy to see if you have done mods to it) is to do a factory system restore, so I decided why not exploit that and make it into an application? Well that's exactly what I did and best of all, it's 1 click (technically 3 but i don't count accepting SU permissions as part of the app). You need to grant SU both times it asks for it to automatically reboot.
Code:
//I take no responsibility what happens with this application or your device and assume that any problem during this process if user fault.
//
Download link?:
http://dl.dropbox.com/u/15069134/Nookunrooter.apk
Instructions?:
Install app, open, click button, grant SU permissions (twice), and let it restore. That's about it.
Warnings?:
You WILL lose ALL data on the tablet except the Sdcard. Be sure to back everything up using titanium backup.
Changelog?:
Code:
1.2: Initial release
Credits?:
Code:
Dodgejcr for his code on github so I just had to change a few things as well as his help in IRC. Thanks man
Myself for rewriting parts of the app to be a one click unroot for the nook tablet[/QUOTE]
Every time I try to run the app I get "could not echojava.io.IOException:Error running exec(). Command [su] Working Directory:null Environment:null"
Any recommendations on what i do?
Click to expand...
Click to collapse
Q&A for [PORT][RECOVERY] Modified CWM (non-touch) for porting to all MTK phones
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PORT][RECOVERY] Modified CWM (non-touch) for porting to all MTK phones. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
carliv said:
This is a Clockworkmod modded recovery.
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
I used it as base for my touch recovery. Basically is a CWM 6.0.3.7 for jellybean and CWM 6.0.5.1 for kitkat modified by me with many extra features.
- aroma file manager menu
- rainbow mode menu
- separate power menu
- separate wipe menu
- nvram backup/restore menu
- advanced backup/restore menu
- toggle signature, toggle md5sum.
For port follow my new guide from here
For jellybean version currently there are two lunfile paths in the world of mtk phones. This will make your USB Mass storage to work in recovery or not. Search that path in your device to see what you have.
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file" - this can be found in many devices mt6572, mt6589, mt6589T, and other old ones.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file" - this is related to new devices mt6582, mt6592...
Find where is your path and download the image to port from correct section.
Depending of your resolution width, choose an image which contains exactly that value or one close to it, and follow the tutorial to port it.
JELLYBEAN
Regular MTK phone
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file"
Download your resolution from HERE.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file"
Download your resolution from HERE.
MTK phone with "custpack"
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file"
Download your resolution from HERE.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file"
Download your resolution from HERE.
MTK phone with Ubifs file system
Lunfile path 1 (old): "/sys/devices/platform/mt_usb/gadget/lun%d/file"
Download your resolution from HERE.
Lunfile path 2 (new): "/sys/devices/platform/mt_usb/musb-hdrc.0/gadget/lun%d/file"
Download your resolution from HERE.
KITKAT
Regular MTK phone
Download your resolution from HERE.
MTK phone with "custpack"
Download your resolution from HERE.
MTK phone with Ubifs file system
Download your resolution from HERE.
IMPORTANT:
These are compiled recoveries for porting purposes only. DON'T take any of them and flash it in your phone as it is. It won't work. You need to port it to your device as I show in my guide.
CREDITS:
- Philz-cwm6 - for get partition size method;
- xiaolu - for the new fonts;
- C3C0 - for initial mtk tweack hint - Unused now;
- Koush and all CWM team for the recovery;
- bgcngm for unpack/repack utils;
- sk8erwitskil for aromafm menu
If you want to say "Thanks!" this is how you can do it:
Press the "Thanks" button.
Make a donation and "buy me some coffee".
Share your opinion about my work and write some feedback in my threads.
Advertise my work to your friends.
Rate my thread with 5 stars.
Either way of support you choose is highly appreciated, but it's not expected!
RULES for posting your ports!
If you managed to port this to your device, add proper credits in your thread, post or article.
Click to expand...
Click to collapse
i have xolo one running on lollipop 5.0 mtk6582 chipset what recovery to chose for my phone
Q&A for exFAT and NTFS fuse drivers easy build for any platform
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for exFAT and NTFS fuse drivers easy build for any platform. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Trying on 4.2.1.... It does not work. I got "volume operation failed" after manually run "recovery-update2.sh."
DeepInSleep said:
Trying on 4.2.1.... It does not work. I got "volume operation failed" after manually run "recovery-update2.sh."
Click to expand...
Click to collapse
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.
/system/etc/recovery-update2.sh test
For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
Lurker0 said:
If you manually run the script, be sure you run it as su, and provide it any parameter, e.g.
/system/etc/recovery-update2.sh test
For troubleshooting, edit the script to uncomment the logging and try to figure out the problem from the log file.
Click to expand...
Click to collapse
Problem solved I deleted this part (the script does not run with him. I do not know why)
Code:
#!/system/bin/sh
logfile0=/data/local/tmp/exfat_mount.log
#logfile=$logfile0
logfile=/dev/null
if [ -e $logfile0 ]; then
logfile=$logfile0
I also changed the mount point from the /mnt/media_rw/sdcard1 to /mnt/sdcard2. With a device=/dev/block/mmcblk1p1 some programs have not seen hardware sdcard, only storage/sdcard1 patch. Then I replaced it on device=/dev/block/vold/179:97. Now it works fine for me
UPDATE: crashing with multiple read/write operations. Tested in bittorrent app