Related
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.41.6)
https://docs.google.com/uc?id=0B5c3gpyMBJusWi1XN09fZjkzUWM&export=download
aromafm_tass.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusLTk5ZENsNWpudms&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ-Touch Recovery for Galaxy Mini, Tool/Utility for the Samsung Galaxy Mini
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-26
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
GALAXY MINI GOES OFFICIAL NOW!!!!!!
You'll now find Galaxy Mini in the officially supported devices list at the Main thread.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
alexanderq said:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
Click to expand...
Click to collapse
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Faiyaz5yaz said:
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Click to expand...
Click to collapse
You mean, you are always rebooting to recovery and not to your rom?
If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.
Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.
But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Good work bro.:thumbup:
Sent from my GT-S5570 using xda premium
no
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I didn't restore back up..
I reflashed my previous cwm..
it booted normally
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.
Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?
Thanks everyone for reporting....
I'll try to fix this when I get time...
ast00,
Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.
Good news:
My friend @chraso gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Bhargav97 said:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Click to expand...
Click to collapse
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Faiyaz5yaz said:
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Click to expand...
Click to collapse
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .
not that
Bhargav97 said:
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Click to expand...
Click to collapse
I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery
Bro,
please read FAQs, this is a problem of your device sources. For solution, see FAQs.
After that, please give me broader report.
You di not ask the right question:
Does this work for someone , anyone please confirm.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
1. Unlocked bootloader and rooted device
2. Enable USB DEBUGGING
3. Make sure that device drivers are successfully installed
4. Connect to PC
5. Download Partition increased tool from download section
6. Click on " Partition Increaser.bet " file
7. Press ENTER key
8. NOW changes will starts
Note : Don't disconnect DEVICE until tool says SUCCESSFUL
9. Copy all the files which are present in " Partition_Increaser_and_Decreaser_for_tomato / files ........ and save them in your pc for restoring to default partitions
NOTE : for every new cm based installation you have to do this steps
STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system .... and select repair or Change File System .... and select resize
STEP3 Reboot
Partition changer ( Increase / default ) : link
USEFUL LINKS
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@I Putu Tirta Agung S
YU YUREKA
YU YUREKA PLUS
XDA:DevDB Information
[MOD / TOOL ] YUREK PARTITIONS Increasing / Decreasing / Default using easy tool V2.0, Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2016-06-13
Current Beta Version: 1.0
Beta Release Date: 2016-06-09
Created 2016-06-13
Last Updated 2016-09-27
Reserved
Revert Back to default partition values
1. Unlocked bootloader and rooted device
2. Enable USB DEBUGGING
3. Make sure that device drivers are successfully installed
4. Connect to PC
5. Download Partition increased tool from download section
6. Click on " Partitions to default.bet " file
NOTE : Don't disconnect device until tool says successful
7. After successfull device will boot in to TWRP
8. Go to wipe / Advance wipe
9. Select all except MICRO SD-CARE
10. Go to wipe / Advance wipe .... and select system .... and select repair or Change File System .... and select resize
11. Do this for all except Micro SD-card
12. After this you have to flash COS12.1 in fastboot mode [ very important ]
13. After setup os cos12.1 is complete
14. Unlock bootloader
15. flash TWRP
Reserved
Repair tomato if brick using @Annabathina tool
Then here is the solution for it ....
1. make sure that drivers are installed correctly
2. Connect to PC in " Normal mode " or " in recovery mode "
3. Open repair tool v 1.0
4. Open " repair tomato "
*********************** Note ****************************************
5. If tool says successful then device will boot in to TWRP , know wipe every thing including Internal sd card for 2 times
6. After this you have to flash COS12.1 in fastboot mode [ very important ]
7. After setup os cos12.1 is complete
8. Unlock bootloader
9. flash TWRP
Repair tomato if brick : link
Annabathina said:
......NOTE : For every new CM based installation you have to do...
STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system ....
.......... and select repair or Change File System .... and select resize
STEP3 Reboot
NOTE: The above 3 STEPS are not required for MY roms ......
Click to expand...
Click to collapse
Annabathina said:
...5. If tool says successfull then wipe every thing including Internal sd card
6. If you are restoring older rom then you have to restore it for " 2 times "
7. After that go to wip / advance wip
8. select system........... repair or Change File System .... and select resize
9. select data ............repair or Change File System .... and select resize
10. cache .................repair or Change File System .... and select resize
11. reboot your device...
Click to expand...
Click to collapse
i) after resizing partitions, can i restore my nandroid backup?
ii) if yes, how many times should i restore a recent rom (r46)?
iii) just to re-confirm: is the above resizing step required for your new ownrom3.0?
iv) although you mention only system in your op, is it recommended to wipe system, data and cache?
i wanna try your tool and get larger partitions. please DO REPLY and help. thanks in advance.
m0han said:
i) after resizing partitions, can i restore my nandroid backup?.
Click to expand...
Click to collapse
Yes
m0han said:
ii) if yes, how many times should i restore a recent rom (r46)?
Click to expand...
Click to collapse
I don't get this question? What do you mean by this?
m0han said:
iii) just to re-confirm: is the above resizing step required for your new ownrom3.0?
Click to expand...
Click to collapse
You can use any rom after rezising.
m0han said:
iv) although you mention only system in your op, is it recommended to wipe system, data and cache?
Click to expand...
Click to collapse
Yes, it is better to do a complete wipe after the process completed via TWRP
Annabathina said:
......NOTE : For every new CM based installation you have to do...
STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system ....
.......... and select repair or Change File System .... and select resize
STEP3 Reboot
NOTE: The above 3 STEPS are not required for MY roms ......
Click to expand...
Click to collapse
Annabathina said:
...5. If tool says successfull then wipe every thing including Internal sd card
6. If you are restoring older rom then you have to restore it for " 2 times "
7. After that go to wip / advance wip
8. select system........... repair or Change File System .... and select resize
9. select data ............repair or Change File System .... and select resize
10. cache .................repair or Change File System .... and select resize
11. reboot your device...
Click to expand...
Click to collapse
i) after resizing partitions, can i restore my nandroid backup?
ii) if yes, how many times should i restore a recent rom (r46)?
iii) just to re-confirm: is the above resizing step required for your new ownrom3.0?
iv) although you mention only system in your op, is it recommended to wipe system, data and cache?
i wanna try your tool and get larger partitions. please DO REPLY and help. thanks in advance.
tirta.agung said:
Yes
I don't get this question? What do you mean by this?
You can use any rom after rezising.
Yes, it is better to do a complete wipe after the process completed via TWRP
Click to expand...
Click to collapse
ok
"If you are restoring older rom then you have to restore it for " 2 times " (check the hidden quotes). hence the doubt.
"The above 3 STEPS are not required for MY roms" (check the hidden quotes). i mistakenly thought that ownrom release was his.
ok
thank you.
I think I did some mistake now my in my phones file manager when i click on internal storage it says 'the file or folder was not found' and I dont have that much files like in this image as you said.......can you please provide the files
recovery
which recovery r u using....and plzz give a link and guide
Dibesh16 said:
I think I did some mistake now my in my phones file manager when i click on internal storage it says 'the file or folder was not found' and I dont have that much files like in this image as you said.......can you please provide the files
Click to expand...
Click to collapse
Go to OP 3rd poast for it
can anyone explain about this?? is this really required for flashing cm13 or any rom?? or without this also we can flash any cm13 rom?
Annabathina said:
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
1. Unlocked bootloader and rooted device
2. Enable USB DEBUGGING
3. Make sure that device drivers are successfully installed
4. Connect to PC
5. Download Partition increased tool from download section
6. Click on " Partition Increaser.bet " file
7. Press ENTER key
8. NOW changes will starts
Note : Don't disconnect DEVICE until tool says SUCCESSFUL
9. Copy all the files which are present in " Partition_Increaser_and_Decreaser_for_tomato / files ........ and save them in your pc for restoring to default partitions
NOTE : for every new cm based installation you have to do this steps
STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system .... and select repair or Change File System .... and select resize
STEP3 Reboot
Partition changer ( Increase / default ) : link
USEFUL LINKS
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@I Putu Tirta Agung S
YU YUREKA
YU YUREKA PLUS
XDA:DevDB Information
[MOD / TOOL ] Tomat PARTITIONS Increasing / Decreasing / Default using easy tool V2.0, Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2016-06-13
Current Beta Version: 1.0
Beta Release Date: 2016-06-09
Created 2016-06-13
Last Updated 2016-06-13
Click to expand...
Click to collapse
Bro can you help me with below issue ?
Suddenly my Yuphoria crashed and when tried to restart it is getting stuck on YU Logo.
able to go to fastboot mode and tried to flash latest official fast boot images using factory tools but it is unable flash and unable to mount /system /data and /cache partitions.
as per guide from some of the threads , tried boot to TWRP and tried to repair or wipe partitions but it is giving same error and unable to mount those partition. even tried to change file system-type and that too didn't help (ext4, fat etc)
in TWRP went to mount option and there it is showing 0mb for internal storage.
tried to manually mount using terminal (using commands like make_ext4fs) but that also didnt help.
Boot and recovery partitions are safe !
check attached images for more reference.
I think i have lost partitions or internal memory is corrupted ! if partitions are lost or corrupted anyway to rebuild or any other was to fix it ?
please please please someone help !
manthanshah16 said:
Bro can you help me with below issue ?
Suddenly my Yuphoria crashed and when tried to restart it is getting stuck on YU Logo.
able to go to fastboot mode and tried to flash latest official fast boot images using factory tools but it is unable flash and unable to mount /system /data and /cache partitions.
as per guide from some of the threads , tried boot to TWRP and tried to repair or wipe partitions but it is giving same error and unable to mount those partition. even tried to change file system-type and that too didn't help (ext4, fat etc)
in TWRP went to mount option and there it is showing 0mb for internal storage.
tried to manually mount using terminal (using commands like make_ext4fs) but that also didnt help.
Boot and recovery partitions are safe !
check attached images for more reference.
I think i have lost partitions or internal memory is corrupted ! if partitions are lost or corrupted anyway to rebuild or any other was to fix it ?
please please please someone help !
Click to expand...
Click to collapse
Hey MAN your not even reading THREAD TITLE
this tool is for YUREKA [tomato]
Annabathina said:
Hey MAN your not even reading THREAD TITLE
this tool is for YUREKA [tomato]
Click to expand...
Click to collapse
ya i know but thought of just checking.. u might have solution or tool for yuphoria !
manthanshah16 said:
ya i know but thought of just checking.. u might have solution or tool for yuphoria !
Click to expand...
Click to collapse
I have developed this tool for YUREKA only bucz in YU devices I am using YUREKA
and without devices it is very hard to build a tool like this
Getting error message in recovery.
I'm able to repartition successfully but when I resize the system partition in TWRP after flashing stock CM13, I get this message:
"/sbin/resize2fs /dev/block/mmcblk0p25 process ended with ERROR: 1
Unable to resize system."
Tried multiple times. Didn't work.
Mention repartition size
Please metion the repartition size after running you tool.
I did it the size increased. But after flashing rom it again restored to default size. The change was temporary before installing rom. Phone is rooted and tried 6 to 7 times, why does this happens???
Done Successfully: Best Tool
I am used your tool to increase system space and done successfully few days ago, I am on CrDroid 7.1 (2.0 Version), want to upgrade 2.2 version, do I need to resize system space again?
As per crDroid Upgrading Process from earlier version of crDroid:
- Copy crDroid ZIP to your internal SDCard
- Boot into Recovery
- Wipe system and cache
- Flash crDroid zip
- Flash Gapps
- Reboot
i have an issue while formatting userdata....
i tried too many times but i cant able to format the userdata...
can you please help me to solve this issue...
TWRP 3.2.1_r12 Moto Z2 Play (albus)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03
I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.
Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.
3.1.2_r18 version released. Check download link in OP
hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?
fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok
rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.
Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?
Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.
I make a full backup, so can I restore that backup file after LineageOS?
This works when go command fastboot boot .... ?
I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...
Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
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 recovery 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.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.2, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m31-v1.0
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m31
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, exynos-nigg, testers and anyone else who made this possible.
Changelog:
v1.0
Initial Release
More in github release page
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website
FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.
Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Karen3443 said:
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Click to expand...
Click to collapse
nope, you havent bricked. start by flashing stock rom again, the flash twrp, AND BE SURE to flash encryption disabler and format data. thats all and it should boot. if you skip encryption dissabler, then the stock recovery will auto restore itself(which seems your case)
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
drcarlox said:
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Click to expand...
Click to collapse
yes, you'll lose your data. so, backup anthing important
Ahamadmusa said:
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
Click to expand...
Click to collapse
tap tag on the github page of bootlogo patcher and download the latest version
soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
Thanks, it worked. Now waiting for custom rom.
soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
i'm getting 404 page not found error,can you provide link?
kogkita said:
i'm getting 404 page not found error,can you provide link?
Click to expand...
Click to collapse
ok found it by searching through google,thx buddy.
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
If any custom rom comes for m31 in future,is there any possibility to decrease cpu and gpu voltage offsets?(custom kernel support ?)
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
zrekkab said:
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
Click to expand...
Click to collapse
it might be a mistake here(states android 10),but on telegram page it was mentioned android 11 only,try upgrading to 11 and flash,all modules perfectly worked for me.
ensonahmet said:
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
Click to expand...
Click to collapse
htt ps :/ /github. com/corsicanu /TWRP_Bootlogo_patcher /releases/tag/ v1.3 ,remove the spaces and download this 1.3v file
Thanks
Now build v2
I solved the solution by installing the Indian version of SM-M315F INU M315F XXU2BUC1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Features:
* Encrypted build
* Vanilla build (no gapps)
* Selinux enforcing and Safety net passes by default
* More info - Click here
First Time Installation:
* Backup before you begin
* Reboot to provided or TWRP based recovery.
* Format Data , even coming from crDroid 8.x
(otherwise you may not able to boot ROM due to encryption complexities)
* Flash ROM via adb sideload
* Flash Nik Gapps core + Gapps Search addon + Google Device Personalization addon via adb sideload
* Reboot and profit!
Update Installation:
* Backup before you begin
* Ensure you are on provided 12/13 recovery
* Use Updater app to download update and flash
(or download update separately and use Updater app with Local update option)
* No need to flash gapps if already flashed.
Download:
Click Here
Known issues:
* None.
Sources:
ROM: https://github.com/crdroidandroid
Device tree: https://github.com/crdroidandroid/android_device_xiaomi_sm6150-common
Visit official website @ crDroid.net
crDroid sweet/sweetin - crDroid Telegram
Donate to help me in development
crDroid Community Telegram
Donate to help CrDroid team pay server costs
Hello, neobuddy89.
I installed the rom this morning.
I encountered only a "bug" (??).
In developer'options, I choose as usual "File transfer" but it is then automatically set to "No data transfer".
Correction isn't urgent. I can use a USB key.
hi,
i flashed last build and touch issue persists on A13 build
But i still stay on
Nice! Thanks a lot!
Very nice ROM, but it has some issues...
- file transfer in developer option doesn't stay how I want (no data transfer)
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Hellera said:
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Click to expand...
Click to collapse
The same issue here. That's why i'll wait for fixed version. Even Gapps installing just some of packages. There is no option to install any .APK file or to install any Google Play's aplication. Cant install magisk too. Always problem with storege.
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
mnsiw said:
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
Click to expand...
Click to collapse
I clean flashed it in orange fox recovery, latest version., OrangeFox-R12.1_3. Did I do something wrong? Can you provide a specific recovery something else than default one, please? Thank you.
mnsiw said:
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
Click to expand...
Click to collapse
I'm on 3.6.2_12-0. Other ROMs working fine, and i cant find any newest TWRP.
Hellera said:
Very nice ROM, but it has some issues...
- file transfer in developer option doesn't stay how I want (no data transfer)
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Click to expand...
Click to collapse
` Can-dlE ! said:
I'm on 3.6.2_12-0. Other ROMs working fine, and i cant find any newest TWRP.
Click to expand...
Click to collapse
I faced similar issues on some TWRP builds and OrangeFox, storage, APK and Play Store related stuff. Since then I'm on 'TWRP-3.6.2-sweet-Nebrassy-13-09-22' and never faced such issue again. This one works perfect except for some Pulkit builds, where you need KewL version of TWRP.
Try twrp-3.7.0_12-0-sweet.img which can be downloaded here.
1) Recovery -> format -> reboot to Recovery (internal storage unreadable)
2) Recovery -> Install crDroidAndroid-13.0-20221108 (from sd card)
-> Install NikGapps-core-arm64-13-20220908-signed.zip
-> Reboot to System
3) Recovery -> Data decrypted
4) Backup/Restore of data in recovery seem to work too.
I find the rom nice, features rich and good/stable to use except mtp (file transfer) doesn't work. To access files in the internal storage, I have to boot to recovery.
jngiag said:
Try twrp-3.7.0_12-0-sweet.img ...
Click to expand...
Click to collapse
Thank you for your explanation.
I followed the same way to install the rom this wednesday morning (see post 2 of this thread), using also the same twrp.
As workaround to the mtp tranfer problem (awaiting for a quick solution), I simply use a USB key instead of rebooting to twrp.
For having used crDroid 8 for a few months as daily driver, I'm now using crDroid 9 in the place in order to ensure continuity : same environment, same developer.
jngiag said:
Try twrp-3.7.0_12-0-sweet.img which can be downloaded here.
1) Recovery -> format -> reboot to Recovery (internal storage unreadable)
2) Recovery -> Install crDroidAndroid-13.0-20221108 (from sd card)
-> Install NikGapps-core-arm64-13-20220908-signed.zip
-> Reboot to System
3) Recovery -> Data decrypted
4) Backup/Restore of data in recovery seem to work too.
I find the rom nice, features rich and good/stable to use except mtp (file transfer) doesn't work. To access files in the internal storage, I have to boot to recovery.
Click to expand...
Click to collapse
Thanks for this, but how can I acces the phone storage or sd card...? Nothing works! File transfer doesn't work, and that's a big problem!
I'm looking forward to flashing A13 once it's more stable. Also, it's the weekend and I don't want to spend the next few days looking at a recovery screen
Hellera said:
Thanks for this, but how can I acces the phone storage or sd card...? Nothing works! File transfer doesn't work, and that's a big problem!
Click to expand...
Click to collapse
Awaiting the correction of the problem "MTP File tranfer", simply act as follows :
connect your phone to your PC with the cable ;
reboot to twrp ;
on your PC, you will find your device and
;
you can then work as with MTP File transfer
cocopipou said:
Awaiting the correction of the problem "MTP File tranfer", simply act as follows :
connect your phone to your PC with the cable ;
reboot to twrp ;
on your PC, you will find your device and View attachment 5758139 ;
you can then work as with MTP File transfer
Click to expand...
Click to collapse
Yes, I know that... but is frustrating to do this everytime when I need access to the phone storage. Thanks anyway!
Maybe the next build will be corrected.
Hellera said:
Yes, I know that... but is frustrating to do this everytime when I need access to the phone storage. Thanks anyway!
Maybe the next build will be corrected.
Click to expand...
Click to collapse
I agree with you, but we have to be patient.
Don't forget that we have the chance having a developer who makes a great work.
It's a first release of crDroid 9.
Before installing this rom, I installed various A13 roms.
None of them had the problem of MTP file transfer but other disadvantages like "No advanced restart", ...
After flashing Magisk in TWRP, launching the Magisk app results in it saying "Downloading" and loading forever.
tomikaka said:
After flashing Magisk in TWRP, launching the Magisk app results in it saying "Downloading" and loading forever.
Click to expand...
Click to collapse
TWRP version? Magisk Version?
` Can-dlE ! said:
The same issue here. That's why i'll wait for fixed version. Even Gapps installing just some of packages. There is no option to install any .APK file or to install any Google Play's aplication. Cant install magisk too. Always problem with storege.
Click to expand...
Click to collapse
for me its all working.