Database Info

[RECOVERY] CWM based recovery v5.5.0.4 + repacked Touch CWM v5.8.1.8

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.

GApps & Root for AOSP KK ROMS Noob-Friendly (Guide)

To root AOSP Based Roms :& Flash GApps.
1. Get any Kernel with a recovery which is from JB 4.2(kernel for example ThunderZap by @varun.chitre15 )
2. Flash it via fastboot. To flash download Flashtool from here.
• Important Note : After flashing kernel don't reboot directly to system and disconnect the phone from PC, then boot and press the required keys to boot to recovery.
3. Boot into Recovery, by pressing vol +or- key when led glows while booting.
4. Download Flashable package of Super SU from here {Official Site)(Also Attached as a Zip flash it by using recovery via install zip option. and then Power Off.
5. Now fastboot again and flash the original supplied kernel and boot the device.
6. Enjoy now you have Super Su check with any root app to confirm root.
•>> Thank me if it helped you And this method is checked thrice by me.
TIP: You can also use this method to flash GApps
Credit : @Me_Shazzy for telling me to make this guide more N0Ob friendly
•>> Added QR of this thread scan to view it on Mobile Devices

For Drivers for PC to connect XL go here http://forum.xda-developers.com/showthread.php?p=46681093
Sent from my C2104 using xda app-developers app

Thanks it works!
But you should have provided more noob friendly guide..
Anyways Appreciate your work

@Me_Shazzy can you elaborate it what all thing can i add to it to make it noob friendly and just press thanks for my efforts
Sent from my C2104 using xda app-developers app

Navneet Suresh said:
@Me_Shazzy can you elaborate it what all thing can i add to it to make it noob friendly and just press thanks for my efforts
Sent from my C2104 using xda app-developers app
Click to expand...
Click to collapse
Ha pressed !
Make step alot clearer and easier Like this
Download the update-su and keep in sd card
1. Flash A kernel with CWM by booting your phone to Fastboot (vol+) To flashtool (by Androxyde ) And flash the the kernel's boot.img
2. Go to recovery And flash update-su
3. Pull out the battery so that the phone turns off
4. Boot into fastboot again and flash KK boot.img
5.wipe cache and Dalvik cache
wait for it to boot

@Me_Shazzy thanks bro for your tip consider it done i will take your points into consideration
Sent from my C2104 using xda app-developers app

Pleasure is mine

I am currently on aospa beta 5 with phantom kernel v5 and my phone apparently doesn't have root :s :/ i can't flash the super su update because in the recovery it doesn't show up anywhere..i can't restore backup ,i literally am stuck!What should i do?:crying:

Do this
arjit mehra said:
I am currently on aospa beta 5 with phantom kernel v5 and my phone apparently doesn't have root :s :/ i can't flash the super su update because in the recovery it doesn't show up anywhere..i can't restore backup ,i literally am stuck!What should i do?:crying:
Click to expand...
Click to collapse
Take out your SD card and insert in your PC
Download Super Su Flashable Zip
Put it in your root of SD card
Flash it.

Navneet Suresh said:
Take out your SD card and insert in your PC
Download Super Su Flashable Zip
Put it in your root of SD card
Flash it.
Click to expand...
Click to collapse
I don't have a card reader to put the sd card in the computer! :/

hmm
arjit mehra said:
I don't have a card reader to put the sd card in the computer! :/
Click to expand...
Click to collapse
Backup flash JB then put the Super su then restore then root via that zip

Navneet Suresh said:
Backup flash JB then put the Super su then restore then root via that zip
Click to expand...
Click to collapse
NAndroid backup?And flash JB as in?stock rom?

yep
arjit mehra said:
NAndroid backup?And flash JB as in?stock rom?
Click to expand...
Click to collapse
Yep take a nandroid backup then flash stock rom get the zip onto root of sd card and then restore to Kitkat

Navneet Suresh said:
Yep take a nandroid backup then flash stock rom get the zip onto root of sd card and then restore to Kitkat
Click to expand...
Click to collapse
Wait wait wait ..i'm confused ..won't flashing the stock rom unroot my device and remove everything?

arjit mehra said:
Wait wait wait ..i'm confused ..won't flashing the stock rom unroot my device and remove everything?
Click to expand...
Click to collapse
Well do this get the zip file via pc connect you xperia l(kitkat) in MTP mode to the pc get that zip to the root of the sd card and then reboot recovery flash zip reboot then download super su from the playstore open it it will automatically fix root
Sent from my C2104 using xda app-developers app

Navneet Suresh said:
Well do this get the zip file via pc connect you xperia l(kitkat) in MTP mode to the pc get that zip to the root of the sd card and then reboot recovery flash zip reboot then download super su from the playstore open it it will automatically fix root
Sent from my C2104 using xda app-developers app
Click to expand...
Click to collapse
"Root of your sd card" ? There isn't any such folder when i connect it to the pc.

Try to pull the zip with adb to external sdcard(sdcard1).Then flash from external in recovery).
Sent from my C2105 using xda app-developers app

arjit mehra said:
"Root of your sd card" ? There isn't any such folder when i connect it to the pc.
Click to expand...
Click to collapse
I meant put that super su zip in the sdcard directly not in any folder
Sent from my C2104 using xda app-developers app

It's already in the external card but in recovery it doesn't show up

hmm
arjit mehra said:
It's already in the external card but in recovery it doesn't show up
Click to expand...
Click to collapse
Weird if you want to flash via external card just go to recovery flash via external card option is there see it.

[ROM][P51xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project

Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!​
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P51xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30

Thank you Andi! I've been hoping for this! Up and running, really really smooth.
Sent from my GT-P5110 using Tapatalk

Thank you Sir.. Can't wait to try it out.
Sent from my Nexus 6 using XDA Premium HD app

stuck at samsung galaxy tab page
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there

luckywang95 said:
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
Click to expand...
Click to collapse
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.

Hello
p5110
installed no problem
thanks
regards

Android-Andi said:
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.
Click to expand...
Click to collapse
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:

luckywang95 said:
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
Click to expand...
Click to collapse
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.
If it boots, boot back into recovery and flash gapps.
If still not work, start clean flash again and get a recovery.log directly after flashing.

Android-Andi said:
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.
If it boots, boot back into recovery and flash gapps.
If still not work, start clean flash again and get a recovery.log directly after flashing.
Click to expand...
Click to collapse
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:

luckywang95 said:
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
Click to expand...
Click to collapse
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?

Android-Andi said:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Click to expand...
Click to collapse
yes. i chose allow changes. my device is p5100. installation failed. i will get recovery.log now and upload to u soon.
---------- Post added at 10:45 AM ---------- Previous post was at 10:31 AM ----------
Android-Andi said:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Click to expand...
Click to collapse
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you?

luckywang95 said:
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you?
Click to expand...
Click to collapse
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send

Android-Andi said:
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send
Click to expand...
Click to collapse
i have sent it to you through private message. i will do it again here.
drive.google.com/file/d/0B3WN3t7uFUZvcFh1cTRlVzdacEU/view?usp=sharing
its google drive.

Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg

and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:

luckywang95 said:
and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:
Click to expand...
Click to collapse
Good to know... Mh... Could you get me a logcat and dmesg?
I had a similar issue on p3110, but i am sure i fixed it on p5100 before compiling... Maybe something else is wrong then...

Android-Andi said:
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
Click to expand...
Click to collapse
but i have the same directory when i flash the cm12?
---------- Post added at 11:58 AM ---------- Previous post was at 11:12 AM ----------
Android-Andi said:
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
Click to expand...
Click to collapse
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...

luckywang95 said:
but i have the same directory when i flash the cm12?
.
Click to expand...
Click to collapse
ok, then it's not the cause
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
Click to expand...
Click to collapse
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use

Android-Andi said:
ok, then it's not the cause
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Click to expand...
Click to collapse
its not connected to computer... i cant use adb.... i tried installing all driver... but still cannot... adb devices shows nothing..:crying:
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
Android-Andi said:
ok, then it's not the cause
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Click to expand...
Click to collapse
sorry, just now is my usb hub not working. not the device. dmesg and logcat i uploaded to google drive. in this folder. it included the recovery.log just now.
https://drive.google.com/open?id=0B...9Ydkw3T0VfZUhWS0ticHdtYnhOQ1hWTFhhRkVtSEh3QVE
logcat is empty. but it is still in the folder.

Hello AndroidAndi
First, thank you for this rom and I have not had any problems during installation.
Full wipe (data, cache, dalvik, format system) and installation of Gapps tk_gapps micro-modular-5.1.1.
If you want sreens? :
Sorry for my English
Dirk

[RECOVERY][TWRP][D290/D295] TWRP Recovery 3.1.0.0 for LG L Fino + Bootloader unlock

TWRP Recovery 3.1.0.0 for LG L FINO + Bootloader unlock​
Notice:
This recovery is compatible with all versions of the L Fino.
Just be sure to pick the right model either
D290X or
D295X
X being sub-model
Disclamer:
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing!
* YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Click to expand...
Click to collapse
Problems/Bugs:
None. Please report in the comments section if any found.
Differences between this and the other TWRP recovery:
You can now enter the recovery using hardware keys combo
The newest TWRP source.
D290 is now using proper DT and kernel images meaning that D290 devices are recognized properly.
People involved:
 @christpp - taking over the TWRP project, as I no longer have the LG L Fino with me.
@meganukebmp - Fixing bugs and coding in general.
@GHsR - Creating the base l70pds tree.
Special Thanks
CaptainThrowback from IRC - Helping me debug and fix.
@lj50036 from IRC - Helping me debug and fix.
@Dees_Troy - Helping me debug and fix.
@_that from IRC - Helping me debug and fix.
Download links / how to install:
Change logs: see 3rd post of this thread
Download links:
D290 ABOOT
D290 RECOVERY
D295 ABOOT
D295 RECOVERY
How to install:
1) You must have your device rooted. Use PurpleDrake method.
2) Download the recovery.img and aboot.bin for your specific device.
3) Place the files in the root of your SD card.
4) Use Terminal Emulator or adb shell to install the recovery and unlock your phone's bootloader:
Code:
su
dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
dd if=/storage/external_SD/aboot.bin of=/dev/block/mmcblk0p6
5) To enter recovery shut down your device. Then hold VOL- + POWER. When the LG logo appears, release the POWER button while still holding VOL- and then immediately hold both buttons again until Factory Reset screen appears.
6) Press YES to both confirmation dialogues. Your phone won't get factory reset. Don't worry.
7) You are in recovery!
Click to expand...
Click to collapse
GitHub LG L Fino TWRP sources:
https://github.com/geekydoc/android_device_lge_msm8610-common/tree/twrp-14.1

Screenshots:

Changelogs:
05.07.2017 ===================================
Update TWRP to 3.1.0.0
F2FS Support
06.02.2016 ===================================
Updated TWRP to 3.0.0.0
Fixed /data partition format.
TWRP Logo now appears.
05.02.2016 ===================================
Fixed internal storage mount and data partition format
04.02.2016===================================
Initial build

Sources ?
Thx Josh

lj50036 said:
Sources ?
Thx Josh
Click to expand...
Click to collapse
Sure, I will share github links today! I just need to push the updates for D295 (l70pds) and I will give links for both devices.
Edit: I added the sources to the thread!

Thanks!! The new build looks great too. But why isn't there a format data option in wipe? Or is it placed somewhere else?

Ky$h said:
Thanks!! The new build looks great too. But why isn't there a format data option in wipe? Or is it placed somewhere else?
Click to expand...
Click to collapse
Not really sure why it's missing..
I will look into it.

the recovery link of the D295 is down

ValenBe said:
the recovery link of the D295 is down
Click to expand...
Click to collapse
Fixed links.
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
NEW BUILD Guys!
Fixed internal storage and formatting of /data
Updated the links just download and flash again.

i have other TWRP recovery how do i install this one?

ValenBe said:
i have other TWRP recovery how do i install this one?
Click to expand...
Click to collapse
There are instructions. Doesn't matter what ROM or Recovery you are using ATM.
Just follow the instructions. Just be very careful not to make a typo

so.. it did format my phone i enter for like a sec and it run like a script amd reboot

ValenBe said:
so.. it did format my phone i enter for like a sec and it run like a script amd reboot
Click to expand...
Click to collapse
You have to flash the recovery first!

meganukebmp said:
You have to flash the recovery first!
Click to expand...
Click to collapse
i did it with the commands

ValenBe said:
i did it with the commands
Click to expand...
Click to collapse
Are you sure you flashed the right recovery image?
I am not experiencing this problem.
What device?

hm yes, i have downloaded the ones that are from my device

ValenBe said:
hm yes, i have downloaded the ones that are from my device
Click to expand...
Click to collapse
What device are you using? Model?

meganukebmp said:
What device are you using? Model?
Click to expand...
Click to collapse
D295g

ValenBe said:
D295g
Click to expand...
Click to collapse
You are most likely flashing the wrong files. Make sure that recovery.img and aboot.bin are the only files with those names in your SD card. Also make sure they are in your SD card not in any folder.
Tested on my device and everything works fine.

Installed it through the Terminal Emulator, restarted and used the button combo as said in the instructions.
It turned the recovery without any problems on my D290N.

[GUIDE] How to remove data encryption/password in TWRP for mediatek devices

Your warranty is now void. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
1. Root with magisk / superuser or however
2. Download root browser and give superuser rights
3. Navigate to vendor/etc/fstab.6765 Open as txt file
4. Search for these lines
wait,check,quota,formattable,resize,forcencrypt=/dev/block/platform/bootdevice/by-name/metadata
Click to expand...
Click to collapse
5. Change it to
wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/metadata
Click to expand...
Click to collapse
6. Do the same changes in vendor/nvdata/fstab.mt6765 (if you have this file. Skip if this file does not exist)
7. Boot to twrp and flash your stock recovery.
8. Reboot to stock recovery. Wipe data and reboot.
9. Coplete the setup and flash twrp using official twrp app or flashify. You can use fastboot.
Done! Encryption should have gone. Tested on Micromax Infinity n12. Please comment if it works

Hi I got this CUBOT NOTE 7 and I found working TWRP for it, and instead of what you typed I got something similar but not the same, I got the fstab.mt6735 file (MT6737 CPU) and instead of "wait,check,quota,formattable,resize,forcencrypt=/dev/block/platform/bootdevice/by-name/metadata" the closest thing I could find is "wait,check,formattable,quota,reservedsize=128m,formattable,resize,checkpoint=fs,fileencryption=aes256-xts", I assume I have to change "fileencryption" to something else, I have no idea if you go to XDA often but I posted this just in case somebody finds it useful
Sent from my desktop using Windows 8.1.

As you found a working TWRP, you can basically flash the file attached below after flashing magisk. If that doesn't work,
replace
"wait,check,formattable,quota,reservedsize=128m,formattable,resize,checkpoint=fs,fileencryption=aes256-xts
With
wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/metadata

Tab E said:
As you found a working TWRP, you can basically flash the file attached below after flashing magisk. If that doesn't work,
replace
"wait,check,formattable,quota,reservedsize=128m,formattable,resize,checkpoint=fs,fileencryption=aes256-xts
With
wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/metadata
Click to expand...
Click to collapse
I tried
Tab E said:
As you found a working TWRP, you can basically flash the file attached below after flashing magisk. If that doesn't work,
replace
"wait,check,formattable,quota,reservedsize=128m,formattable,resize,checkpoint=fs,fileencryption=aes256-xts
With
wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/metadata
Click to expand...
Click to collapse
That is a line you showed earlier which might brick this phone and I don't want to flash all of android back onto it