Touch enabled ClockWorkMod for LG Optimus 4X HD 4.0.3 ONLY
NOT COMPATIBLE WITH LG EARLY BETA v20a WITH Android OS 4.1.2
ClockWorkMod recovery based on http://builder.clockworkmod.com but of course not using a boot.img here, but a raw ramdisk copy of it.
Todo's
A bootup check function, on external sdcard, for a _boot direct to recovery_ in case you
cannot get regular apps opened, this might be a way to boot recovery in bootloop cases.
HOWTO install
UPDATES: if you are installing an update , remember to press install recovery again, so the changes take effect.
Get your o4x root'd, follow this guide here
make sure busybox is installed correctly and all commands are available in /system/xbin (normally part of rooting installation)
Download the attached zip to this post
extract the apk from inside the downloaded zip file.
install the LG-Optimus-4XHD-Recovery apk on your mobile
after installation reboot mobile once (if you do not, the app might fail installing recovery)
start the LG 4X Recovery app
press - Install recovery - grant superuser access when prompted
wait for success OK, if it fails, something is wrong or SU is not properly installed or denied su access. you should set permissions to granted for this app
after successfull installation, you can press boot recovery and boot into the clockworkmod recovery and make your backups or install custom roms
when you do a backup, remember that CWM v6.0.1.1 got a bug, so you need to specifically chose backup to external sdcard for now.
ChangeLog
05-sep-2012
- uses latest boot base from v10f (OPEN edition), but not much changed
-Found issue with unmount of /system and other filesystems during start of clockworkMod, making it hard to restore backup.
all filesystems are now properly unmounted and services stopped which could use it.
- for adb users, unplug usb cable once, to re-activate adb connection when cwm starts.
current issues
backup to internal sdcard location is not working , use backup to EXTERNAL sdcard (problem is the link in / which point to /mnt/sdcard)
(FIXED in v1.1) factory reset/restore backup - if you restore a backup or factory reset, it will also wipe your internal storage/sdcard location. as LG have chosen to use part of internal store on same partition.
so where possible, always copy your internal storage files to a safe location
(Koush removed this option in v6.0.1.1)external sdcard - mount usb - currently shares only external sdcard storage to pc.general notes
It is to assume, that anything restored from a backup, will include any 4X clockwork recovery, as this is located on your system partition.
so its always good to install the newest apk, after a restore of your backup.
snapshots of recovery running on LG Optimus 4X HD
{
"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"
}
information on the technical solution used
The bootstrap solution used to run ClockWorkMod is based on the 2nd-init function , which has been around for some time now.
Additional functions are used here, based on services started and building small changes into the unsecure ramdisk, so we get the full functionality of our device.
For those technical users, wanting to use my work, just remember to mention where you got it, and i have no problems with others using scripts.
It's also important when booted into recovery, that you restart adb (adb usb) to get full root access.
as this recovery is not started from a clean bootup, some cleanup jobs are required for those, that MIGHT do a custom rom.
i have seen with my works in progress, that jellybean and htc roms use different services and those needs to be included in the bootmeny/bootrecovery script to stop and cleanup what ever service started originally. so when/if someone makes a different rom, remember to update the bootmenu scripts, which i guess you know how to change if you do customroms.
reserved for future
Nice job
Just like my old milestone
Bootloader is locked so restore from recovery is the only method of using custom roms...
Awesome work. Cant wait for a release!
Good Job!!!!!!
Now,I just have to wait for a cleaner root method from you,
that make install busybox from forced to option XDDD
Great news, thanks for your hard work!!!
Gesendet von meinem LG-P880 mit Tapatalk 2
i am working on how to get recovery started and it ain't that easy.
as you know security meassures taken by LG was quite high, so even key chord triggers from boot is disabled in the kernel, so we cannot activate by any keys for now.
great job so now just waiting to work with recovery.
:thumbup:
Inviato dal mio LG-P880 con Tapatalk 2
Ok,
i am almost ready with the complete package for recovery install (NO root install or similar)
requirements will be that you got o4x root'd to run this installer properly.
Since we got no key detect function in bootup(missing in kernel) available or binary app to extract a keypress, this app will need to run to activate recovery at next boot. thats the solution for now.
ill return with the app installer soon
Dexter_nlb said:
Ok,
i am almost ready with the complete package for recovery install (NO root install or similar)
requirements will be that you got o4x root'd to run this installer properly.
Since we got no key detect function in bootup(missing in kernel) available or binary app to extract a keypress, this app will need to run to activate recovery at next boot. thats the solution for now.
ill return with the app installer soon
Click to expand...
Click to collapse
Thanks Dexter,you're GREAT:good:
OTOGY2002 said:
Thanks Dexter,you're GREAT:good:
Click to expand...
Click to collapse
thx also, great done
testing backup/restore function now.
had some issues mounting /sdcard correctly.
i am close to releasing it now. but want to make sure you do not mess up your mobile using it, so i sacrifice my own before going alpha public with it.
First ALPHA-BETA release in post #1
First release is now attached in post #1 .
do note, this can be experimental based on how users get root'd their mobile, if they did not follow guides or experimented.
but generally it should be ok,
i have tested backup/restore and all looks good for now.
its VERY important, you do not just factory reset or restore a backup, since internal storage is mapped to /data/media location, and you will loose all your stored files here. so backup those files before you start restoring or a factory reset as both functions will format data partition.
Thanks man! Works great
I've inattentively read the instructions and do not reboot before install recovery and now have bootloop
Code:
E/ThermalDaemon( 162): waiting for boot complete
E/ThermalDaemon( 162): waiting for boot complete
E/NetdConnector( 258): Communications error
E/NetdConnector( 258): java.io.IOException: No such file or directory
E/NetdConnector( 258): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 258): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 258): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:119)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:88)
E/NetdConnector( 258): at java.lang.Thread.run(Thread.java:856)
E/NetdConnector( 258): Error in NativeDaemonConnector
E/NetdConnector( 258): java.io.IOException: No such file or directory
E/NetdConnector( 258): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 258): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 258): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:119)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:88)
E/NetdConnector( 258): at java.lang.Thread.run(Thread.java:856)
E/ThermalDaemon( 162): waiting for boot complete
Can i fix it without reflashing?
m0b said:
I've inattentively read the instructions and do not reboot before install recovery and now have bootloop
?
Click to expand...
Click to collapse
yes.
if you can "su -" it will be ok.
then
0. su -
1. mount -orw,remount /system
2 mv /system/bin/netd.bin /system/bin/netd
thats the problem. netd is not ok.
Can i fix it without reflashing
Recovery on system partition, that's brilliant.
I'm new with 2nd init, try to read about it so may be I can help somehow.
atipon said:
Recovery on system partition, that's brilliant.
I'm new with 2nd init, try to read about it so may be I can help somehow.
Click to expand...
Click to collapse
any help is appreciated, its not easy to test and get around all the stupid things LG invented here. they more we resolve, less of it will be added if they find it worthless to do (nahh, but sounds good)
Now i cant start it again
Related
First thanks to drgravy who compiled this TWRP build for the LG G Pad 8.3 GPE (V510); device name Palman, a link to the official TWRP download page will be posted once the appropriate section for (Palman) has been created.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DISCLAIMER:
I nor anyone else is responsible for what you do to your device.
but if something goes wrong I will do my best to help
Download:
TWRP 2.6.3.1 V510 Palman
How to flash:
Since this is a GPE Tab simply boot your device into fastboot. Easiest way is to do adb reboot bootloader.
Once booted into the bootloader simply issue this command:
fastboot flash recovery palman.img
Once done reboot into recovery and you should be greeted with TWRP.
CREDITS:
@Dees_Troy and team win for this wonderful recovery
Confirmed working on GPE version.
Unlocok bootloader and flash recovery or you can just do "fastboot boot palman.img" and it will boot in recovery without flashing it (so you get to keep stock recovery in case you need to run an OTA later).
Hi
I get the message "Waiting for the device", so how get the device in fastboot mode?
Thanks
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
Enable usb debugging or check if u have drivers
Enviado do meu GT-I9300 através de Tapatalk
Ver3go said:
Enable usb debugging or check if u have drivers
Enviado do meu GT-I9300 através de Tapatalk
Click to expand...
Click to collapse
Sorry for the dumb question, but where do I get the drivers for the GPE? I used Dalingrin's easy root script for the LGE, but "adb shell" doesn't work with that minimal adb, so I'm assuming I need to grab a different driver?
UPDATE: Still looking for the drivers. I downloaded the latest ADT and had it install the Google USB Driver, but still neither "adb shell" nor "fastboot devices" works properly. Just to answer the obvious question, yes, I've enabled USB Debugging in Developer Options. Any thoughts on how I can get past this hurdle so that I can get to a point where I can root a GPE device?
UPDATE 2: Okay, I figured it out and have GPE all nice and rooted now! Basically just follow the instructions to root a Nexus 5 but use the recovery image on this thread and you should be golden!
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
This package is for "palman" devices; this is a "v 500".
Click to expand...
Click to collapse
Is there any easy way to fix that?
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
I might have an easy answer for you, give me a few minutes to try it out first.
---------- Post added at 04:32 PM ---------- Previous post was at 04:06 PM ----------
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
I think you can do this two ways, flash back to the stock recovery, or just run the stock recovery once from the bootloader. Flashing back to the stock recovery is probably the safest option, however I have an idea if you don't want to have to go back and forth.
Disclaimer, I'm an NOT expert with this so it may not work.....
Ok, for either option you'll need the stock recovery. You can download it from HERE (Stolen from AutoPrime's post).
I recommend putting the update ZIP and recovery image file in a folder of your root path (for me "C:\android\")
Here's my idea, have fastboot just boot the stock recovery once.
Make sure ADB debugging is enabled in "Developer Options"
Connect your USB cable and run
Code:
adb reboot bootloader
Your tablet should reboot and your should see the bootloader screen, once you see the screen run
Code:
fastboot boot C:\android\17-recovery.img
fastboot should show you progress indicator and once it is finished your tablet should see a red exclamation mark. press the power button and then the vol. up button. This should show options 1. Reboot System 2. ADB Sideload, use the volume keys to select adb sideload then press the power key to select.
then
Code:
adb sideload C:\android\a0bd45922b5958a38acef76f577f527268ef90db.signed-KRT16O.L004_user-KOT49H.L004_user_update.zip
I think it will work, not sure if it will keep TWRP or overwrite it. Like I said earlier, I'm not an expert.
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
OTA updates are not working with a custom recovery like twrp. Either flash back to stock or wait for the developers to compile and release the updates as zip packages that you can flash from the custom recovery menu. Look what a developer said about this here http://forum.xda-developers.com/showpost.php?p=48150524&postcount=31
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.
Any ideas for recovering from this?
Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg
Edit: Had TWRP reformat /data, still nothing.
Archon810 said:
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.
Any ideas for recovering from this?
Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg
Edit: Had TWRP reformat /data, still nothing.
Click to expand...
Click to collapse
Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.
djkinetic said:
Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.
Click to expand...
Click to collapse
What can we do right now to try to sort this out? I've also started http://forum.xda-developers.com/showthread.php?p=48593224 to help with the recovery process, which I'm sure folks will find useful in the future.
I'm available for any kind of debugging. Could boot.img have gotten messed up somehow?
Archon810 said:
What can we do right now to try to sort this out? I've also started http://forum.xda-developers.com/showthread.php?p=48593224 to help with the recovery process, which I'm sure folks will find useful in the future.
I'm available for any kind of debugging. Could boot.img have gotten messed up somehow?
Click to expand...
Click to collapse
I have an idea, looking at your screenshot it looks like a similar error that occurred on the N5 and TWRP early on after unlocking the bootloader...After you updated 4.4.2 and then did fastboot oem unlock, did you let the tab boot up? Because after you do that it sets a flag to format the system ext4 on first boot, if you flash a recovery before that happens and boot into recovery first you get errors....do this in recovery delete the file .twrps in /sdcard/TWRP use the file manager advanced...this is the TWRP settings file, once you do that then try to reboot system.
The problem is /sdcard/TWRP/ is completely empty. There are no files in there. I even checked using shell and ls -al.
And yeah, I didn't let it reboot after unlocking.
I actually have a replacement en route from Google to address a yellow tinted display. I think I'll wait until that gets here, let it update to 4.4.2, and then go through this process on that device.
sorry, how do you open the recovery?
djkinetic said:
I have an idea, looking at your screenshot it looks like a similar error that occurred on the N5 and TWRP early on after unlocking the bootloader...After you updated 4.4.2 and then did fastboot oem unlock, did you let the tab boot up? Because after you do that it sets a flag to format the system ext4 on first boot, if you flash a recovery before that happens and boot into recovery first you get errors....do this in recovery delete the file .twrps in /sdcard/TWRP use the file manager advanced...this is the TWRP settings file, once you do that then try to reboot system.
Click to expand...
Click to collapse
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Archon810 said:
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Click to expand...
Click to collapse
I'm probably earlier in the process than you @Archon810. I have similar issues have a decreasing feeling that I will solve this any time soon. At this point, if I fastboot boot the recovery palman.img and try to install the noroot V510 zip image provided, I get the binary link error which was present on my Nexus 7 on twrp for awhile. I backleleveled the twrp to 2.6.3.0 on the Nexus 7 and this stopped that problem. More seriously, after all the stuff I've done to fix things, I fear I have probably borked things more than fixed them.
Now after any attempt at flashing anything in recovery whether I install the recovery or just boot from it, the result is binary file error.
Going to try restoring the default image and doing things again.
Archon810 said:
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Click to expand...
Click to collapse
Flash the stock recovery from here http://downloads.codefi.re/autoprim...Firmware/KRT16O_16_partitions/17-recovery.img
Then reboot in recovery see if it continues the format process from unlocking the BL
Sent from my LG-G2 using Tapatalk
Any way we can get a CWM build for V510 so that we can avoid the binary error from TWRP?
djkinetic said:
Flash the stock recovery from here http://downloads.codefi.re/autoprim...Firmware/KRT16O_16_partitions/17-recovery.img
Then reboot in recovery see if it continues the format process from unlocking the BL
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
Yeah, as per the other thread, this did the trick.
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.
Hi this thread contains Clockworkmod Recovery,Flashtool Backup,ROM Dump,Deodexed ROM,Nandroid Backup,Official Update,Patched Boot.img and Scatterfile
UPDATE
-Will be making Philz touch recovery on december (On my vacation when i have free time) it is a modified,update and better recovery than the CWM......hope you can wait for it TWRP Recovery is way better than Philz Recovery
-Guys who want CWM recovery for the A3500H or F or FW version please post your recovery here i shall try to make it into CWM recovery (On december you can also ask for philz recovery)
-Thinking of making an custom ROM on december also
-Will be posting the Updates/nandroid backup/romdump/Deodexed.zip of the 4.4.2 versions in the middle of next month
-Also i have found a new method of sniffing the URL of the update.zip without any logcat all you need is root and xposed module and a windows OS will be making a tutorial for it soon.Capturing OTA Update URL For Noobs (No logcat required)
Rooting Guide-
1) Flash CWM Recovery using Flashtool
2) Flash UPDATE-SuperSU-v2.02.zip using CWM recovery (Links provided below)
Dodexing Guide-
1) Flash the zip file in CWM to deodex (It help youin theming) (Will upload the deodexed 4.4.2 Soon)
Important-
1) Do not flash Patched boot.img (Gives adb Root shell by default) if you are using 4.4.2 version (Will upload it soon)
2) When making a nandroid backup make sure that you backup and erase all data in your in your internal memory otherwise it shall make a backup of that too.
3) Before Flashing the system partition make a IMEI bacup using Mobileuncle Tool and restore it after flashing or the mobile internet and call will not work.
4) To go to recovery press vol+,vol- and power
Changelog-
04/11/2014
- Added TWRP Recovery
- Added TWRP Nandroid Backup Of A3500HV_A422_01_22_140402_IN
- Patched(ADB Root Shell) And Unpached Boot.img (Kernals) For Android 4.2.2
Press Thanks if it helps (That is if you can find it since the thanks has disappeared in the new forum theme.....lol)
Tools
Tools Required for these procedure-
Drivers-
-ADB Driver (Thought i would give since not all adb driver works on this tablet)
-Preloader VCOM Driver (Required to for SP Flashtool to work)
Tip- If having problem in installing driver in windows 8,8.1 head to the tutorial section blow for detains since unsighned drivers needs to be enabled in these windows version
Windows Softwares-
-SP FlashTool
-ADB Installer (Allows ADB to be used systemwide)
-USB Deview (Checks What Drivers You Have Installed And Helps To Uninstall Them)
Apps-
-MobileUncle Tools
-Flashify v1.7.4.apk
Tutorials
These are tutorials that you must read before doing anything (It will only take 5 Min)-
CWM Flashable Files
These are the list of files that can be flashed by Clockworkmod Recovery
Rooting zip-
-SuperSU.zip
Deodexed App-
-A3500HV_A422_01_22_140402_IN
Flashtool Files
These are the list of files that can be flashed by SP Flashtool-
ROM (Inclusive with CWM Recovery and Patched boot.img)-
-A3500HV_A422_01_22_140402_IN
Recovery-
-Original
-CWM
-TWRP
Boot.img (Kernals)-
-Patched (ADB Root Shell) And Unpatched For Android 4.2.2
Nandroid Backup
This is a nandroid backup of a clean system (I am not sure if it will work on other devices but what the hell....lol)
Important-
Backup and restore IMEI using Mobile Uncle or you will loose your call and internet function
Versions-
CWM-
-A3500HV_A422_01_140402
TWRP- (Do not flash the NVram partition or you will loose your call function also make an IMEI Mobile Uncle Backup)
-A3500HV_A422_01_140402
Official Updates
This is the Official Lenovo Updates Flashable.zip and its links (The Link gives the official lenovo link but the file is 1GB and download Accelerator seems to corrupt it use my link it is exactly the same and the files are broken into 400mb parts and you can use download accelerator on it...:victory
For the updates to work you need to reflash the stock recovery (Link Above) install the update Reflash the CWM then Done
Method 2-This method can only be used for the rooted device to install recovery (Since you need to flash CWM before you rot the device i did not write it above
-extract the original recovery. rar
-open flashify.apk on the tablet
-select recovery.img to flash
-done flashing successful
-reboot now
-recovery now is stock select update.zip
-flash it
-take 2 minutes
-successful
-reboot sysw now
-take 3 minutes
-my system build version and the launcher is updated
-Flash back the CWM recovery with Flashify
Note- Sometimes the update removes the root then you need to follow the rooting procedure again
Updates-
-01) Lenovo_A3500-HV_A442_01_S037_WC69
Links-
-01) Lenovo_A3500-HV_A442_01_S037_WC69
TUTORIAL- Capturing OTA Update URL For Noons (No logcat required)
ROM Dump
This is the ROM Dump of the entire ROM
-A3500HV_A422_01_22_140402_IN (CWM Recovery) (After First Run)
Others
These Folders Contain Other Stuffs-
{
"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"
}
great work
thank you great work ...is there any way to flash update.zip by cwm recovery ? it give me error 7 and installation aborted ..if i toggle signature verification it give me error cant verify whole file
one more question
i already rooted my tablet and have cwm ..if i want to restore the original one must do imei backup .or not?
drabuaiad said:
thank you great work ...is there any way to flash update.zip by cwm recovery ? it give me error 7 and installation aborted ..if i toggle signature verification it give me error cant verify whole file
one more question
i already rooted my tablet and have cwm ..if i want to restore the original one must do imei backup .or not?
Click to expand...
Click to collapse
I guess you have to flash the original recovery then try it if still no results then use use ota rootkeeper (or similar app) to hide root before update if that still does not work remove root through Supersu settings and then try it lenovo has really made this model such that you can not get root easily therefore they must be checking for root before updates after that use the default steps for rooting above .
Above all check your lenovo and see that it is a3500 HV and not simply h or f as the kernel are different
No when you are flash a boot.IMG or recovery.IMG you need not do a backup and while flashing through CWM with the official update you need not since there are scripts in it to transfer the imei or so I guess but but since you are rooted its always best to do one because adding an imei number is more difficult than a restore and the process takes a few seconds and only needs about 120 bytes (you can backup a billion of those and still not run out of space
Better safe than sorry....lol
thank you again
Yes my tablet is a3500 hv and i have the FW 4.4.2.....35 which is the same as .....37 except the lenovo launcher
So i am satisfied with it and waiting if new update arrives i will restore the original recovery
I think there is no more update will land here except if android L is the next one..i dont think so
drabuaiad said:
thank you again
Yes my tablet is a3500 hv and i have the FW 4.4.2.....35 which is the same as .....37 except the lenovo launcher
So i am satisfied with it and waiting if new update arrives i will restore the original recovery
I think there is no more update will land here except if android L is the next one..i dont think so
Click to expand...
Click to collapse
Great but did you root your tablet after you got the 4.4.2 update or before I tried the update and the same error 7 guess need stock recovery also i will be posting a tutorial on how to capture official update links that does not require logcat and only requires to install two software and an app. Found this method while trying to capture offnline setup from online installer (in windows 7 when you use a online setup it quietly downloads a offline setup and then installs it and after installation deletes it I found a way how to capture the link so in that method I use the reverse tethering to take internet from the computer and then capture the link from the computer...lol) Will make a thread in the next two days.
excellent it is new idea
I am waiting your tutorial
I received 5 updates for my tab..three of them is 4.4.2 after i update the 35 version i found the root method above ..flashing cwm recovery then install superiser.zip.
After that i get small update 9.22mb that will replace lenovo launcher and change the build number to 37 ..but cant install it and give me error 7
I catch the update.zip from ggogleota folder and transfer to my external sdcard and try to flash it after toggle sg verification and also toggle assert ...
But also give me installation aborted
I stop trying and i have now original recovery downloaded in my tablet and ready for any new update lol
drabuaiad said:
excellent it is new idea
I am waiting your tutorial
I received 5 updates for my tab..three of them is 4.4.2 after i update the 35 version i found the root method above ..flashing cwm recovery then install superiser.zip.
After that i get small update 9.22mb that will replace lenovo launcher and change the build number to 37 ..but cant install it and give me error 7
I catch the update.zip from ggogleota folder and transfer to my external sdcard and try to flash it after toggle sg verification and also toggle assert ...
But also give me installation aborted
I stop trying and i have now original recovery downloaded in my tablet and ready for any new update lol
Click to expand...
Click to collapse
Cool so if it works please tell me I shall update the official update post of this forum and also tell me if you did the update by changing recovery only or by changing recovery and also unroofing hope it works....:fingers-crossed:
And within one months time after my final exams are over I will try to make a custom ROM nothing fancy just the most updated Updates custom apps deodexed some patches etc etc and so on....just something I am thinking of doing with my new alienware during my Christmas vication.
oh my god
its working
i do this
extract the original recovery. rar
open flashify.apk on the tablet
select recovery.img to flash
done flashing successful
reboot now
recovery now is stock (it is somewhat different i think it is of 4.2.2 FW) select update.zip
flash it
take 2 minutes
(it write delete unwanted files!!!!!!)
successful
reboot sysw now
take 3 minutes (long time)
my system build version and the launcher is updated
---------- Post added at 05:42 PM ---------- Previous post was at 05:22 PM ----------
NB root is removed
good for me
After the second reboot .recovery now the stock of FW 4.4.2 it looks different
Lenovo A3500H MT8382???
anandisrocking007 said:
Hi this thread contains Clockworkmod Recovery,Flashtool Backup,ROM Dump,Deodexed ROM,Nandroid Backup,Official Update,Patched Boot.img and Scatterfile
Rooting Guide-
1) Flash CWM Recovery using Flashtool
2) Flash UPDATE-SuperSU-v2.02.zip using CWM recovery (Links provided below)
Dodexing Guide-
1) Flash the zip file in CWM to deodex (It help youin theming) (Will upload the deodexed 4.4.2 Soon)
Important-
1) Do not flash Patched boot.img (Gives adb Root shell by default) if you are using 4.4.2 version (Will upload it soon)
2) When making a nandroid backup make sure that you backup and erase all data in your in your internal memory otherwise it shall make a backup of that too.
3) Before Flashing the system partition make a IMEI bacup using Mobileuncle Tool and restore it after flashing or the mobile internet and call will not work.
4) To go to recovery press vol+,vol- and power
Press Thanks if it helps (That is if you can find it since the thanks has disappeared in the new forum theme.....lol)
Click to expand...
Click to collapse
Dear anandisrocking007 thank you for enormous effort on rooting lenovo A3500.
I confused if I can use your procedures for my lenovo A7-50 A3500H_A422_01_23_140404_TR, chipset mt8382 , 4.2.2 (update ready but not installed to 4.4.2).
I would like to use phone specification of tablet while I install my SIM card to access internet.
Also I had problem to install MTK driver to use flashtool for CWM recovery.
Thanks in advance for your help.
Cihangir
baycanc said:
Dear anandisrocking007 thank you for enormous effort on rooting lenovo A3500.
I confused if I can use your procedures for my lenovo A7-50 A3500H_A422_01_23_140404_TR, chipset mt8382 , 4.2.2 (update ready but not installed to 4.4.2).
I would like to use phone specification of tablet while I install my SIM card to access internet.
Also I had problem to install MTK driver to use flashtool for CWM recovery.
Thanks in advance for your help.
Cihangir
Click to expand...
Click to collapse
Your version is H not HV (Different Hardware well about 95% same) use thisk link- http://forum.xda-developers.com/android/development/guide-lenovo-a3500-h-t2879208
The kernal might be different so be carefull if you are using this recovery in this thread though the probability of the there being problem for the recovery is low if any problem please contact me and if you want a CWM recovery for the following device just sent me the recovery.img
As for rooting you can use tis update zip it is going to work for over 99% of the mobile in the world
As for the problem for the driver use the tutorial for the installing drivers in windows 8 if you are using that version of windows 8 for me the drivers worked perfectly if not disable the antivirus its 100% not a virus and also you need to be in admin account when you install the driver and not in the guest account.....
At december or so i would be making Philz touch recovery which is a modified and better recovery image based upon CWM recovery
If any more problem feel free to contact me.....:victory::victory:
drabuaiad said:
oh my god
its working
i do this
extract the original recovery. rar
open flashify.apk on the tablet
select recovery.img to flash
done flashing successful
reboot now
recovery now is stock (it is somewhat different i think it is of 4.2.2 FW) select update.zip
flash it
take 2 minutes
(it write delete unwanted files!!!!!!)
successful
reboot sysw now
take 3 minutes (long time)
my system build version and the launcher is updated
---------- Post added at 05:42 PM ---------- Previous post was at 05:22 PM ----------
NB root is removed
good for me
After the second reboot .recovery now the stock of FW 4.4.2 it looks different
Click to expand...
Click to collapse
The recovery is HV not FW 100% sure i know which tablet i have maby in different countries different recovery don't know also did you need to remove root for the update to work or did the update remove the root??????
By the way in december (When i go back home for vecation and have plenty of time) i am thinking of making Philz touch recovery it is a modified updated and better version of CWM recovery.
mmmmm
waiting your new recovery
the update remove the root but still the super user present as a system application ...
The recovery i flashed is not the same as this present after first boot after updating
my tablet now work fine but may i change my mind with your first custom rom
{
"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"
}
ONLY FOR NOUGAT FIRMWARE
Working:
ADB
If can possible make a mount / backup or restore any partition, included DATA, restore, backup, flashing...
The settings are saved on CUSTOM partition, and BACKUP's on external storage
MTP
Dont working:
Tell me
Changelog:
RC2 16-03-2017:
Updated UI
New logo and splash screen
Fixed errors on Backup/Restore
Optimized the code
RC1 11-03-2017:
Updated to TWRP base 3.0.3
Data in whole recovery, mount, unmount, backup, restore, flashing .zip files... NO MORE NEEDED DOWNGRADE TO MM
ADB Now can send command and receive
Optimizations...
b9 15-12-2016:
MTP and ADB works at init thanks to: @LastStandingDroid
ADB Keys working thanks to: @LastStandingDroid
Deleted unneded stuff
b8 14-12-2016:
Reworked MTP
Reworked with kernel B336
Updated banner with correct version of recovery
b7 13-12-2016:
Reworked MTP
Removed unnecesary files
Removed DM-Verity v2
b6 08-12-2016:
New Init logo and banner
Deleted parameters for MOUNTING DATA
Deleted splash2
Reworked init.rc and fstab
b2 03-12-2016:
ADB works but no "auth"
MTP works
Backup & Restore of all patitions working (no DATA backup)
Settings of TWRP saved on CUSTOM partition
b1 02-12-2016:
First version working on Nougat
Images
Attached in bottom of the post.
Download:
For install in Android MM (if dont are now in Android N) or for install in Recovery Nougat b*: https://mega.nz/#!tE1XXIaK!ICq1NO1DpLedfdgB0j5DzH4xtEN6jcz2Di8UXfcqSBE
recovery.img for install with Fastboot: https://mega.nz/#!gU91XJjI!V3RcPQ0tDeFNBJAu04cI1gxMqDypEdxs6TQHGF3h0_o
Regards
BadWolfYe said:
Working:
All dont listed in "Dont Working"
Dont working:
ADB
USB MTP
Mount and manage DATA
Download:
For install in FASTBOOT: https://mega.nz/#!JcNCADDA!f4EvXvIJYEPkALmUrG5WDhB-u7pRpcDZ5DvQpQpxlD8
For install in Android MM (if dont are now in Android N):
Im working in fix the error listed up, when i fix all, i work in Revolution Recovery for NOUGAT
Regards
Click to expand...
Click to collapse
Is for VNS-L21 ? Or not?
Why is this called Android Nougat?
The named its called for only work on Android Nougat Firmware....
Adb/mtp fixed...
Working on data partición fix
Oh god i hope you get it sorted, your my last hope with my brick ..... **** me
WTF?
This is no a job, dont need a review for employer's HAHAHAHAHAHA
News:
Data partition still no working...
In this moment recovery save the settings in CUST partition
Backup of all listed partitions CORRECT (tested)
Only can backup to external sd
ADB no work "unathorized" but MTP yes, for activate, go to mount and disable mtp, after, reenable mtp... an boila!
Installation fails at 7 status error (in this moment caused by data partition)
im deleting all unusued stuff on recovery, and upload in the next hours... BETA 2 xd
OP updated
I do not mean to be rude and I appreciate your work, but how is this different from the regular TWRP and from TWRP by Meticulus? I mean there are two rock-solid versions of TWRP, what is the added value of flashing this one?
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
BadWolfYe said:
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
Click to expand...
Click to collapse
My apologies, I feel super stupid now. Thanks for your contribution!
Thanks for your work
Thread cleaned of stupidity. Next time we'll talk privately. :good:
Cheers,
Darth
Senior Moderator
TWRP not picking up internal storage, please help.
Recovery updated and reworked...
Hello
I do not understand, I can not manage to make it work.
He shows me cust 177mb
Internal storage 0mb
Micro sdcard 0mb
And I get to nothing. thank you
I understood
BadWolfYe said:
Recovery updated and reworked...
Click to expand...
Click to collapse
Now can i flash directly on the reworked twrp? Like if im going to reflash the b329 + data files? And also the camera fix?
Is there somewhere already a supersu file for root
Then you could root it and then downgrade with toolkit because the twrp he has fixed and thus you could zip the zip yes
Thank you for your great work
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
ExodosPL said:
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
Click to expand...
Click to collapse
It must be "fastboot flash recovery RevRecNP9Lite.img"
Thank You, it works
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).