Hi there, i'm starting here a discussion thread about Team Win Recovery Project 2.x for our HTC One SV.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Click to expand...
Click to collapse
{
"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"
}
Pictures by TWRP
As long as i know it will work for k2_u and k2_ul (LTE), cause both have the same partition layout.
This recovery don't work for boost mobile users!
Notice:
This is not my work, i'm not the developer of it!!! I only start the thread here about it because the dev is a russian guy (and i don't know, if he is here at xda and if he speaks english language).
Please be sure what you are doing, when you flash it, bricks can happen and i am not responsible for damaged devices. Do at your own risk!
Credits:
- xpirt for building it
- Modding.MyMind for his open mind
- MikG for earlier versions
- Team Win Recovery Project
- rollon76 for posting this here on xda
- jmztaylor (for being a great guy and help if needed)
- bkcokota (for his cwm recovery, a start for development)
Important: Recommended for hboot 2.21!
Download:
--------------------------------------------------------------------------------
This is not for boost mobile users!
You can find TWRP Recovery 2.7.0.1 (made by xpirt, credits and thanks to him) here.
Only for k2u & k2ul!
--------------------------------------------------------------------------------
The recovery for boost mobile (K2_CL) users is in the second post!!!
--------------------------------------------------------------------------------
How to install:
Download the img file and rename it to recovery.img
Put it into your fastboot folder and start a command window there.
Boot your phone into fastboot USB mode (bootloader + device plugged to pc)
Enter the following command:
Code:
fastboot flash recovery recovery.img
That's it.
K2_CL ONLY!!!!!
Kernel Source: Click Here!
Changelog Version 2:
Code:
* From commit [URL="https://github.com/ModdingMyMind/android_kernel_htc_k2_cl_twrp/commit/86a317157a741ef12042426696e3c84eeed3e263"]86a317157a[/URL] on my github.
* Kernel built in version 2.7.1.0
* Disabled Module support
Changelog Version 1:
Code:
* From commit [URL="https://github.com/ModdingMyMind/android_kernel_htc_k2_cl_twrp/commit/c34ea02e20b758e78cae9f8b8bc975d268accd84"]c34ea02[/URL] on my github.
* Kernel built in version 2.7.0.2[B]d[/B]
* Added full SELinux support.
* Removed HTC write protection.
---------------------------
---------------------------
TWRP 2.7.1.0 - for 4.2.2
TWRP 2.7.0.2d - for 4.2.2
TWRP 2.7.0.2c - for 4.2.2
TWRP 2.7.0.2b - for 4.2.2 (deprecated)
TWRP 2.7.0.2a - for 4.2.2 (deprecated)
---------------------------
---------------------------
TWRP source was patched from https://gerrit.omnirom.org/#/c/6283/
This patch allows the ability to take screenshots while in the recovery. It has not been merged over to the TWRP source yet so only unofficial builds at this moment will be seen with this feature.
To take screenshots while in recovery just press both the power key and volume down key. The screen will flash. It will naturally store the screenshot in your pictures folder of your sdcard if mounted in either your internal or external.
TWRP Changelogs:
Code:
[U]2.7.1.0
[/U]Built with custom kernel.
- [B]Removed custom theme and reverted back to stock theme.[/B]
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
[U]2.7.0.2d[/U]
Built with custom kernel.
- Added full SELinux support
- Completely removed HTC write protection.
[U]2.7.0.2c[/U]
Fixed init.rc to allow communication with binaries in /sbin.
TWRP 2.7.0.2c is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
[U]2.7.0.2b[/U]
Minor theme adjustment
Upgraded screenshot functionality throughout entire recovery
Note - version 2.7.0.2a screenshots are limited to only the main page
TWRP 2.7.0.2b is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
[U]2.7.0.2a[/U]
Built from CM11 and Omni 4.4 sources.
Extended backup options.
1. System
2. Boot
3. Cache
4. Data
5. Recovery
6. Misc
7. Firmware_radio
8. Firmware_q6
9. android secure
*** I think I listed them all ;)
Built in AromaFM.
Implemented screenshot functionality.
Added offmode charging.
Completely updated to fit with 4.2.2.
Includes Holofied Black Theme.
TWRP 2.7.0.2a is built ready for SELinux, but the kernel is stock. Until they release the source I can't modify the kernel to support SELinux. This is really only needed for having 4.3+ roms but I want to include it in case the day comes and we see CM, AOSP, or possibly other sources.
HTC Dumlock Instructions:
HTC Dumlock Instructions specifically for S-On users but S-Off users can use it as well if they choose to:
1. Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery.* No fastboot booting it.* We need it in recovery so that this build of TWRP will be flashed to your boot.* This new build of TWRP has features in it to easily restore your original boot.
2. Reboot into recovery.
3. Make a backup of your phone.
4. Tap Advanced.
5. Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)
6. Tap Install HTC Dumlock.* This will install the app and binaries needed to make everything work nicely.
7. Reboot your device.
8. Find and open the HTC Dumlock app.
9. If/when prompted, give the app root (SuperUser) permissions.
10. Tap the Execute HTC Dumlock button.
11. Wait patiently for a couple of minutes.* It takes a little while.
If your device doesn't reboot automatically, reboot it manually.* Reboot it normally.* DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.
12. Tap Advanced.
13. Tap HTC Dumlock.
14. Tap Restore Original Boot.
Use your recovery like normal.* Flash a new kernel.* Restore a backup with a different kernel.* Do whatever you please!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Addition
This recovery also works in the ADB mode with root rigths.
In this mode, you can add (delete) files in the SYSTEM
on OS Jelly Beam
And sets the superuser, if superuser is not in the system.:good:
Are you the developer of it?
I hope it is ok for you that i have started a thread for it here?
Anyway, it works great and you have done it very well ! :good::good::good:
Thanks a lot!!
Thank you. Use it. Version 2.5.0.1 is made on the kernel 3.14.10-gf43d146.
Bootloader and boot restored only if you have S-OFF.
where can i download version 2.5.0.1?? i have 2.5.0 and it works great.
---------- Post added at 06:13 PM ---------- Previous post was at 06:06 PM ----------
MikG said:
This recovery also works in the ADB mode with root rigths.
In this mode, you can add (delete) files in the SYSTEM
on OS Jelly Beam
And sets the superuser, if superuser is not in the system.:good:
Click to expand...
Click to collapse
Is compulsory be S-OFF to delete files in system??could you explain how to do it??
thanks
titin83 said:
Is compulsory be S-OFF to delete files in system?
Click to expand...
Click to collapse
A custom kernel can do this also.
old.splatterhand said:
A custom kernel can do this also.
Click to expand...
Click to collapse
And is there alredy a kernel that let us do this?? By the way , what recovery are you using?? if is 2.5.0.1 , could yo tell me where download it?? in the russian page i got an error when i try to sign in there , and the translation with google is rather bad...
thanks
titin83 said:
And there is alredy a kernel that let us do this?? By the way , what recovery are you using?? if is 2.5.0.1 , could yo tell me where download it?? in the russian page i got an error when i try to sign in there , and the translation with google is rather bad...
thanks
Click to expand...
Click to collapse
To sign in there is really painful if you don't speak the language, but as far as i know it does not work as long you are on google translation. The captcha i could only pass with a guy from another board who speaks russian.
The recovery shows 2.5.0.0 but the filename from download page was Recovery_TWRP_2.5.0.1_HTC_ONE_SV.img so i think it is the same.
Kernel can be found here.
old.splatterhand said:
To sign in there is really painful if you don't speak the language, but as far as i know it does not work as long you are on google translation. The captcha i could only pass with a guy from another board who speaks russian.
The recovery shows 2.5.0.0 but the filename from download page was Recovery_TWRP_2.5.0.1_HTC_ONE_SV.img so i think it is the same.
Kernel can be found here.
Click to expand...
Click to collapse
And the last question , can i flash the kernel without installing the whole rom?? i mean , flash it in the rom that i update some weeks ago via OTA or have i to flash the ro that you have in your signature? My SV is K2_U , can i flash this despite be for K2_UL devices??
thanks
You can flash the kernel only and also for k2u (i have too).
If you are not S-off, you need to flash the zip in recovery and the boot.img inside with fastboot.
once i have flashed the kernel , what i have to do to delete some system app??
thanks again
Use a root explorer and go to system/apps/ and delete the one you don't need anymore (or rename it first to see if it causes problems).
But be carefull with what you delete and make a nand backup before!!!!!
titin83 said:
where can i download version 2.5.0.1?? i have 2.5.0 and it works great.
Is compulsory be S-OFF to delete files in system??could you explain how to do it??
thanks
Click to expand...
Click to collapse
Link in the header right.
S-OFF not need.
In the recovery mount SYSTEM. And the button ADVANCED-> File manager can work fine.
old.splatterhand said:
Use a root explorer and go to system/apps/ and delete the one you don't need anymore (or rename it first to see if it causes problems).
But be carefull with what you delete and make a nand backup before!!!!!
Click to expand...
Click to collapse
No, in JB OS files not be deleted.
Instead, use the file manager in the TWRP recovery.
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
sakax said:
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
Click to expand...
Click to collapse
Everything works fine in my device. Flash it again , perhaps something was wrong.
sakax said:
edit: i was too fast... twrp doesnt work for me. it install perfectly but i cannot boot android anymore? does this work for someone else?
Click to expand...
Click to collapse
This twrp recovery work on many device k2_u and k2_ul fine.
MikG said:
This twrp recovery work on many device k2_u and k2_ul fine.
Click to expand...
Click to collapse
my phone doesnt boot anymore after installing twrp recovery? do i have to reinstall kernel and system backup after flashing recovery? the problem is that i only have cwm backup available?
As long as i know, you can't restore cwm backup with TWRP. So you need to flash cwm and restore your backup with that.
Related
This Rom is based off of the newest HTC Flagship device the HTC One (M7) and ported to our device by me... the rom is IMO 99% Functional with only very minor bugs... anyways i hope you enjoy it if you do hit the thanks button or donate if you wish.... There is a FAQ section in the second post please read through them before asking questions to avoid asking already answered questions... Have Fun!!!!!!
{
"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"
}
Features
Based on 1.28.401.6 CL162357 release-keys
Beatsmode Kernel source here
Sweep to wake
Sense 5.0
Jelly Bean 4.1.2
Rooted SuperSu Perms Thanks to koush
Busybox run parts
Mounts tweaks
sysro/sysrw support
Global support (any carrier)
Pure GSM
Vzw SSO support
and more
Bugs
*Zoe
Changlog
v3.0.0
Updated to 4.2.2
Based on my rom for DNA
Initial release
dlxbu1 only for now
v2.0.0
Updated all apps to latest
Complete overhaul
Adjusted audio for sense 5
Added more battery saving tweaks
Added 4x5 and 5x6 options in app drawer
Added extended context menu
Added extra settings to Gallery
Added Vertical EQS
Added Horizonal EQS
Added battery percent
Added HTC Locations
Fixed hdmi
Fixed dlna
Fix Dubugging not working
Added Secure Folder to MMS
Added Block to MMS
Reverted max MMS size back 1.2 (VZW)
Removed VVM
Removed kidmode(available in market)
Removed KM from apm
Removed NFC for D varient
Hid wireless charging notification
Enabled all Rotations
Raised Entropy size
v1.0.6
Fixed Wifi issues
Added New Camera mod ( lots of options )
Fixed continuous burst
Fixed Slow motion
Fixed panorama
Fixed Battery drain Issues
Added performance Tweaks
Fixed some internal control settings
v1.0.1
Updated base to 1.28.401.7 CL162357 release-keys
Added WWE Lang Support
Fixed LTE issues
Fixed SMS character limit
Fixed video chat issues
Fixed continuous burst ( only takes 2 pics for some reason WIP)
Removed ZOE
Added my custom Auto brightness values
Edited default values in framework
Added my speed tweaks
Switched to newest SuperSU
Updated all apps to latest
Fixed usb mounting issue
Fixed MMS
Fixed Front face camera
Added advanced power menu by dunc001
Added some speed tweaks
Theres alot more i did but cant remeber right off let me know if you have any issues
NOTES
1.)Please do not use this rom or any part of it without my permission I put alot of time into it to get it where it is
2.)As always i am not responsible for anything that happens to your device if you flash this
Credits
Forey79: donated device, tester
LlabTooFeR: New base Rom thread here
Mike1986: thread here
Zarboz: Kernel,banner, and others
Koush: Root and SU perms
dunc001: Advance Power Menu thread here
Chainsfire: Superuser
Follow the instructions bellow and everything should be good
DLXBU1
NOS_v3.0.0_dlxbu1_signed.zip
Have Fun
ROM - Sense 5 for X920d and X920e
Hello fellow X920d and X920e users.
Member 'newtoroot' has ported a Sense 5 ROM to the X920d and X920e.
Please donate to, or thank newtoroot for his great ROM and hard work.
Cheers
Aussie
aussie1234 said:
Hello fellow X920d and X920e users.
Yes we are starved of regularly updated ROMS.
Member 'newtoroot' has ported a Sense 5 ROM to the X920d and X920e.
His link is http://forum.xda-developers.com/showthread.php?t=2184706
I claim no credit for his ROM; I only link to it.
Please donate to, or thank newtoroot for his great ROM and hard work.
Cheers
Aussie
Click to expand...
Click to collapse
CALLING X920E / X920D Testers for kernel
please PM me
Zarboz said:
CALLING X920E / X920D Testers for kernel
please PM me
Click to expand...
Click to collapse
PM Sent !
aussie1234 said:
Hello fellow X920d and X920e users.
Yes we are starved of regularly updated ROMS.
Member 'newtoroot' has ported a Sense 5 ROM to the X920d and X920e.
His link is http://forum.xda-developers.com/showthread.php?t=2184706
I claim no credit for his ROM; I only link to it.
Please donate to, or thank newtoroot for his great ROM and hard work.
Cheers
Aussie
Click to expand...
Click to collapse
Master mdeejay share us sense5 ROM too.
Just provide the link for your reference. Credit is mdeejay
http://forum.xda-developers.com/showthread.php?t=2095683&page=50
Tester
Zarboz said:
CALLING X920E / X920D Testers for kernel
please PM me
Click to expand...
Click to collapse
PM sent :good:
Re: ROM - Sense 5 for X920d and X920e
The external SD card is not recognized...
And too bad one of the core features like HTC Zoe is not working yet.
Sent from my HTC Butterfly using xda app-developers app
anyone have htc drivers for this? usb connected, doesn't show a device in windows 8. adb devices doesn't show anything attached either
Try This
chocchief said:
anyone have htc drivers for this? usb connected, doesn't show a device in windows 8. adb devices doesn't show anything attached either
Click to expand...
Click to collapse
Hi mate
Install HTC Sync Manager - available from HTC website.
I have Windows 8 64bit and all working for me. Using newtoroot X920d ROM (from Droid DNA thread) and see both internal and external SD storage on my phone.
Good luck
Aussie
So for us X920d users, just flash the ROM and then do we need to flash any of the update files?
Sense ROM
lombers said:
So for us X920d users, just flash the ROM and then do we need to flash any of the update files?
Click to expand...
Click to collapse
Hello
I installed newtoroot's ROM http://forum.xda-developers.com/showthread.php?t=2184706
In bootloader first did fastboot erase cache then fastboot flash boot boot.img taken from the ROM and last fastboot erase cache.
In TWRP Recovery I wipe cache, davlick and system and factory reset.
Then I flash the ROM - it takes a while to reboot phone so be patient. I didn't flash any update files. They are for different versions of the phone such as DNA Global and USA I think.
For more info and support refer to newtoroot's thread as I cannot take any credit for it.
Cheers
Aussie
Sorry for the dumb question, first time to flash a custom ROM on HTC devices. How do I flash the file NOS_M7_v1.0.0_X920D_signed.zip?
WPMan said:
Sorry for the dumb question, first time to flash a custom ROM on HTC devices. How do I flash the file NOS_M7_v1.0.0_X920D_signed.zip?
Click to expand...
Click to collapse
1. Download the rom and copy to your phone (you've probably done this)
2. Download fastboot tools if you don't have them here
3. Extract the adb folder in the fastboot zip to somewhere (E.g. C:\adb)
4. Open the rom zip and extract the boot.img file to the adb folder
5. Connect your phone to your pc
6. Hold shift and right-click somewhere in the adb folder, select "Open command window here"
7. Restart your phone to bootloader, then select fastboot.
8. Type "adb devices" (don't type the " " for this or the others)
9. It should show your phone's serial number, if not download HTC Sync Manager and install
10. Type "fastboot erase cache"
11. Type "fastboot flash boot boot.img"
12. Type "fastboot erase cache" again
13. Type "fastboot reboot recovery" to get to CWM or TWRP, whichever you have installed
14. Backup your system, data, and cache
15. Factory reset, wipe cache, wipe dalvik cache, format system
16. Install the rom.
17. Reboot and leave it for 10 mins, it will stay on the HTC ONE screen for a while for the first boot
18. ???
19. Profit
Thanks you. Looks like I need a to get an SD card? I don't have SD cards anymore. lol.
I think internal storage is fine, not sure though since I use my sd card for large files like this
I'm confused about this: fastboot flash boot boot.img
Is the boot.img included in the NOS_M7_v1.0.0_X920D_signed.zip for CWM? Whenever I flash that boot.img I still get the stock recovery. I tried flashing cwm using fastboot flash recovery command and it worked, but can't mount SD card.
EDIT: Looks like I finally got it to work. I flashed boot.img from the ROM zip and downloaded CWM from their website and flashed the ZIP. I get a lot of errors on CWM though, can't mount this and that. I was also not able to wipe system etc.
EDIT 2: Does it really have that red warning text on the boot logo?
WPMan said:
Does it really have that red warning text on the boot logo?
Click to expand...
Click to collapse
Yep, as far as I know you can't get rid of it as of yet. I guess when we get S-Off for the x920d and e then we can get rid of it, but as of now it stays there.
One more question (pardon me, really), are the stock Sense 5 wallpapers really not included in the NOS M7 ROM?
WPMan said:
One more question (pardon me, really), are the stock Sense 5 wallpapers really not included in the NOS M7 ROM?
Click to expand...
Click to collapse
They should be, are you sure you installed it right? Since you're also getting errors on cwm. Check the wallpapers, if #4 is a grey leaf with water droplets on it, and #12 is a cityscapy looking thing
chocchief said:
They should be, are you sure you installed it right? Since you're also getting errors on cwm. Check the wallpapers, if #4 is a grey leaf with water droplets on it, and #12 is a cityscapy looking thing
Click to expand...
Click to collapse
No wallpapers at all. I assume since CWM wasn't able to mount system, data, etc. partitions, the ROM wasn't able to extract the files? I'm thinking of flashing stock RUU again, then install CWM (should I go touch or regular one?), then flash boot.img from rom zip and flash it again? It also did not run the setup wizard after the flashing. I'm HTCDev unlocked. S-on.
Main thread + features + install instructions + dev support :
http://forum.xda-developers.com/showthread.php?t=2201860
DISSCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards or you
* getting fired because the alarm app failed.
* YOU are choosing to make these modifications.
Click to expand...
Click to collapse
{
"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"
}
PhilZ Touch 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
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Update 6.43.0 [CWM Base 6.0.4.8] :
PHILZ Changelog
Code:
6.43.0 (02.06.2014)
- nandroid backup: fix 'media' exception:
In CWM, a bug present from the begining was preventing any path/file named media from backup on /data/media devices
This fix will only exclude /data/media path and not other media files/folders
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- comment useless dead code
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @KumaJaya
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices
Preserve recovery settings after a wipe
- on settings change, create a second copy of recovery settings on primary storage (/sdcard)
- on recovery exit, always copy recovery settings to sdcard if no copy is present
- after a wipe, on recovery exit, try to restore settings from the copy on primary storage
- fix save/restore settings menu labels
- libtouch_gui 1.22
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Ali.Filth Changelog
Code:
- Add Ali.Filth Background
- Fix Philz default Background
Screenshoot :
FULL CHANGE LOG : LINK
XDA: Information
CWM 6.0.4.8, a Tool/Utility for the HTC Sensation
Contributors
ali.filth, Phil3759
Version Information
Status: BETA
Current Beta Version: 6.43.0
Beta Release Date: 2014-06-02
Created 2014-04-14
Last Updated 2014-06-02
Special Thank's to : @migui0401 for helping out with testing for the sake of development :laugh:
Credits
Team-SennyC2 for providing device source
@bilal_liberty
@Sultanxda
@shantur
Click to expand...
Click to collapse
DOWNLOAD
Download :
http://d-h.st/users/ali.filth/?fld_id=36885#files
Installation
Instructions : Recovery Tools
If you have are not sure if you have an unrestricted HBOOT
Download Recovery Tools from Play Store
Download phil_touch_6.26.4-pyramid.img above, rename to recovery.img and put to your sdcard
Open Recovery Tools and give Superuser access
Select Flash Other Recovery and select the release that was copied to SDCard.
Done
Instructions : Fastboot
If you have Juopunutbear HBOOT or other that supports unrestricted fastboot flash commands
Download phil_touch_6.26.4-pyramid.img above, and rename to recovery.img
Boot into your bootloader ( Vol Down + Power )
Enter command
Code:
fastboot erase recovery
fastboot erase cache
fastboot flash recovery recovery.img
Reboot Bootloader
Select Recovery
Guide installation : by @shantur
Reserved
i'm not own this device, so please give your feedback, what work and didn't work before I add it in the main thread.
Thanks
ali.filth said:
i'm not own this device, so please give your feedback, what work and didn't work before I add it in the main thread.
Thanks
Click to expand...
Click to collapse
Thanks for this, i use phils recovery on my S3, very good. Does this have all the options like to change background colour, font colour etc etc like on the S3? Dont have time to flash it now n find out
jmcclue said:
Thanks for this, i use phils recovery on my S3, very good. Does this have all the options like to change background colour, font colour etc etc like on the S3? Dont have time to flash it now n find out
Click to expand...
Click to collapse
sure..this recovery have many feature like that..changing background,text color,touch & non touch, aroma file manager, etc..ok..maybe next time you must try this for your htc device too.
ali.filth said:
sure..this recovery have many feature like that..changing background,text color,touch & non touch, aroma file manager, etc..ok..maybe next time you must try this for your htc device too.
Click to expand...
Click to collapse
Just flashed it using PG58IMG method using my phone, its very cool, looks exactly like the S3. :good:
jmcclue said:
Just flashed it using PG58IMG method using my phone, its very cool, looks exactly like the S3. :good:
Click to expand...
Click to collapse
yes, maybe PG58IMG method is best way for flash it.. :laugh:
ali.filth said:
yes, maybe PG58IMG method is best way for flash it.. :laugh:
Click to expand...
Click to collapse
Normaly id use fastboot commands but no access to pc so just created the PG88IMG on my phone. U need to be s-off to use the PG88IMG method aswell, s-on users need to use fasboot
Thank you. Looks fresh for the color background.
-XoRoX- said:
Thank you. Looks fresh for the color background.
Click to expand...
Click to collapse
Yes..also you can change the background at will you.
By the way, you have this device? have you try? Please give your feedback, what working and didn't working..
I need result before put this device on main thread
Send from my Pager using xda-developers app
4ext & CWM(stock) are more better than this recovery(i test it )
if u develope this recovery may it be a Competitor for that
omegfa said:
4ext & CWM(stock) are more better than this recovery(i test it )
if u develope this recovery may it be a Competitor for that
Click to expand...
Click to collapse
Lol..everything is from user..
but until this time, more than 50 device has support this recovery..and everyday a lot of people always request to ported this recovery for their device.
Send from my Pager using xda-developers app
I looked into this recovery when we couldn't flash 4.4 for awhile on the sensation with 4ext. I appreciate your efforts to port a recovery for a device that you don't even own. Kudos to you! I'll try it out when I get ready to flash a new build.
I found anoher bug, the battery status is always presenting 66%, never change. I will keep reporting.
migui0401 said:
I found anoher bug, the battery status is always presenting 66%, never change. I will keep reporting.
Click to expand...
Click to collapse
What version are you use dude? Maybe you can try this version (6.26.4), and give me result.
Thanks
Send from my Pager using xda-developers app
ali.filth said:
What version are you use dude? Maybe you can try this version (6.26.4), and give me result.
Thanks
Send from my Pager using xda-developers app
Click to expand...
Click to collapse
Ok, i'll flash it:good:
---------- Post added at 07:42 PM ---------- Previous post was at 07:27 PM ----------
The same bugs I've mentioned you before are still present.
migui0401 said:
Ok, i'll flash it:good:
---------- Post added at 07:42 PM ---------- Previous post was at 07:27 PM ----------
The same bugs I've mentioned you before are still present.
Click to expand...
Click to collapse
Hemmm..ok..will fix soon..thank's
Send from my Pager using xda-developers app
Here are my thoughts:
1) You might mention that you need to wipe cache and reboot recovery after first booting into recovery.
2) Clean to Install a New ROM tries to wipe /sd-ext which our device does not have (not a big deal, but if the build can be told that we don't have that partition it would be good).
3) Full backup seemed to work fine.
4) Mounting the SDCARD and transferring a ROM file worked fine.
5) Installing Vipers 5.1.0 which uses Aroma fails (can't press Next). I thought Aroma installers were supposed to work, but maybe that is a limitation of this recovery?
6) Battery does always report 66%. I left my phone plugged in for over 10 minutes and the clock changed but the battery percent did not.
I have to get Venom installed before heading to work so I'm reverting to 4ext for now.
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
How it looks :
{
"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"
}
* This must work on all devices model quark (XT1250 and XT1254) or quark_umts (XT1225) * custom ROM may display only quark
To know you device model just open the app Terminal Emulator for Android and see the quark after the @ like below.
Main download folder
Mirror download folder
The folder contains the Mod TWRP version base on the latest official with proper support to all android versions (The one from TWRP site doesn't have the proper support For Nougat, Oreo or newer OS's, I tryed to push the changes so the one from they site can be updated they did not answer me so I give it up), the mod other than having the proper support for all OS that prevent bug as the "Bootloop to TWRP after a Factory Reset" it has extra backup option (Radio/Modem, boot logo etc), NTFS support for USB-OTG devices, all possible TWRP languages, full encryption support (For Nougat and earlier, Oreo and up encryption is not suported) and etc improves...
All the extras featuring can be seen in the Changelog click here
Big thanks:
A big thank for those that donating to thanks for my work on TWRP.
@ChazzMatt for his donation, and his help on many other threads of Moto Maxx on XDA.
Renan R. R. for his donation
And all the other users that I contribute.
On the developer side, thanks to:
@Dees_Troy for his work on TWRP, for the tutorial and help to bring the official support...
@Skrilax_CZ for his hard work on building the first stable CM to this device
@Aadi for a tutorial.
@respider for his original work on TWRP for quark.
Developer donation link:
To donate via paypal click here
No other donation option is available.
XDA:DevDB Information
TWRP For all Quark(Moto Maxx/Turbo and Droid Turbo)
Contributors
fgl27
Source :
Android :
omnirom M source
LineageOS source
Device :
Device tree for omnirom source
Device tree for LineageOS base source
Kernel tree for LineageOS source
TWRP Version: 3.3.1
Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-08-16
Last Updated Check changelog (click here)
I use many tutorial to make this TWRP, here some to help those who want to do the same.
tags: how to port TWRP recovery, how to compile TWRP recovery, how to make TWRP recovery.
http://forum.xda-developers.com/showthread.php?t=1943625
http://forum.xda-developers.com/showthread.php?t=2294800
http://wiki.cyanogenmod.org/w/Build_for_quark#Build_CyanogenMod_and_ClockworkMod_Recovery
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://source.android.com/source/building.html
https://source.android.com/source/building-running.html
https://source.android.com/source/initializing.html
http://review.cyanogenmod.org/#/c/89474/1/recovery.te
Check Changelog click here
How to install it.
Using Fastboot:
Download mfastboot
The fastboot I share is need replace fastboot with mfastboot in the commands below...
Copy the file you download form OP to the folder of fastboot and use the command in the bootloader screen
Code:
fastboot flash recovery recovery_name.img
! replace recovery_name with the name of the file, example:
Code:
fastboot flash recovery twrp-3.0.2-0-quark.img
Via app Flashify (for root users)
If you have root, try Flashify is really simple.
Install the app, download the recovery to the phone internal memory, open the app, chose recovery image, chose from file, confirm and flash, after you will go straight to the new recovery.
Via TWRP:
Yes TWRP can flash images recovery and boot image.
- install
- images... (is in the bottom right of the screen)
- select the image and image type (boot or recovery)
- swipe
- reboot to test, to recovery if flash a recovery or to system if is a boot...
...............................................................................
keep system read only?
This will be asked in the first time you boot to recovery after flash the recovery, if you not accepts it TWRP may be replace by the previously recovery of your device, but read way...
Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
..............................................................................
Note about restore from Stock 5.x.x to 4.4.4 and vice versa:
The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.
I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.
TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.
That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.
To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>
For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS
Swipe to change
Now restore.
But be aware that the data partition is were internal memory is, so if you change the file system you will loose all the files in internal memory
The wipe of internal memory doesn't happening if you only wipe data partition without change file system.
This will not affect custom ROM, but i recommend to use f2fs.
.....................................................................................
Note about encrypt
Test done in Nougat in the link below
Last Nougat test
Test done in Lollipop below
TWRP supports backup a encrypted system, but i only test this on lollipop stock ROM.
This is a simple description how to encrypt backup and restore the encrypted system.
Stock ROM
You can only encrypt if you have stock recovery and no modification to yours ROM, that means no root or rooted app like xposed modules etc, so if you have uninstall everything and do a full un-root.
To encrypt go to setting>secure>encryption the process take a while...
If you already have stock encrypted ROM you can flash TWRP and make a backup of it.
To remove the encryption you need to flash back the stock recovery and do a factory reset in Settings>Backup & Reset>Factory Reset
Factory Reset will deleted all the files of the device! so make a copy of important data...
Wiping all the partition in TWRP will not remove the encryption.
After the device finish the factory reset all the data of you phone will be deleted and the encryption will be gone.
Now you can flash back TWRP again and have fun...
If you need to restore that encrypted backup you can but after it finish restoring you will see that it is un-encrypted.
Custom ROM
I tested encrypt on custom Marshmallow AOSP base ROM (all the CM's), it is not need any recovery the only thing that is need to encrypt is that the encryption block of data be clean before encrypt.
Cleaning the encryption block of data
TWRP can't clean that so if the user encrypt the device the only way of clean that is by erasing the data via fastboot:
Code:
mfastboot erase userdata
The down side of it is that the partition will be erased lost every file of data and internal memory + when the system boot the data partition will be formatted as EXT4 that have a small performance lost over F2FS, to have it back to F2FS is need to give the command then start the OS, after the device finish boot and optimized it will format the partition and is need to go back to recovery and format the data as F2FS, going on wipe > advanced > select data > "repair change..." >change file sys> F2FS... then boot to the device and use it...
Note about official TWRP, USB driver via USB-OTG work, but your driver need to be formatted as FAT32(small drivers) or exFAT (big drivers), on the Mod version I have update the NTFS support and it now works
...........................................................
Collection of "Special_flash_zip" to go with the Mod TWRP
As some things are not directly attainable through TWRP menus, but they can be achieved via extra zips...
Clean_modem_status.zip
Logo_Flasher.zip
Modem_Flasher.zip
Clean_modem_status.zip
as the name implies this will erase the modem status partition, and erase any bad modem status, this can help in situations were the users is with some radio problem, one most famous on Quark is when user can get a GPS lock...
I test the GPS after flashing this and it works... (I did not had a GPS problem, but will test after I get one...)
Logo_Flasher.zip
This is a zip that can flash logo.bin via TWRP, is need of the user to have the logo.bin then place it inside of the root of the zip, then flash it over TWR.
Modem_Flasher.zip,
This is a zip made to flash the Radio.img + Clean modem status, thus achieving the update of Radio and clean any bad old radio status.
This zip is empty need the user to add the files on the future I will make a zip with the radio image inside... the below explain how to put the files inside.
As on Quark the radio.img is complex image that can't be flash via TWRP it is need to have a special zip, this zip contains the content of radio image after the user have flash it via fastboot, then for that I made this tutorial in how to use the zip, see the below hide...
Tutorial how to make this zip to work...
This zip must be used with a full backup of stock Modem image that can be achieve via app using apk called partition backup or via ADB
1# APP process... config the app Click on the tool, then in backup formats section, mark only Raw partition image
The partitions name to backup are
modem
mdm1m9kefs3
the file must be in sd/Partitionsbackups, the file names need to be just like describe below
before you put they on the zip so rename the files according the below...
modem.img
mdm1m9kefs3.img
make no modifications to the files, and place it on the root of this zip
The just flash the zip via TWRP
#############
2# ADB process, you must have SuperSu from Chainfire installed before making this, CM root will not work.
use the commands "adb devices" to check if the device is connected it will show the device serial number if it is...
then do the next two lines
Code:
adb shell
su
* after command "su" press enter 3 or more times... until the cmd displays
[email protected]:/ #
then... do the next 4 lines
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
dd if=/dev/block/mmcblk0p32 of=/sdcard/mdm1m9kefs3.img
the files will be on the internal memory, the file names need to be just like describe below before you put they on the zip
modem.img
mdm1m9kefs3.img
make no modifications to the files or to the file name, and place it on the root of this zip
The just flash the zip via TWRP
The recommendation is to make a modem backup of yours device after you get a GPS lock, and store it to use whenever you need because you have a radio related problem, or make one to share on XDA with other users, be aware to share Radio zip and describe from with device model and ROM you pull it from, because flashing other device Radio may cause problem...
............................................................
This TWRP is theme-able, go to the tread to change the looks:
[THEME][TWRP] TWRP Materialised - Dark / Light / Play
Support, any bugs and errors just post in here, I will answer as soon as possible.
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
icondeg said:
Can I flash it over using flashify?
Thx
Enviado desde mi Moto MAXX mediante Tapatalk
Click to expand...
Click to collapse
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
baybutcher27 said:
i didn't try that only via fast-boot, but i will.
should not give any error, if you try let me know....
yes it work i just did over TWRP 2.8.1 :good:
Click to expand...
Click to collapse
It works fine!!!
Thanks for all
Enviado desde mi Moto MAXX mediante Tapatalk
omg great work! congrats
muito obrigado!
Awesome work! Thanks man! Can't thank you enough!!
Thank you!
Paypal donation sent.
Confirmation number: 08S12817NX2219226.
Thank you guys i really appreciate the supporter. Of every one.
Small, but big improvement change.
Change log in the 2° post. The TWRP now is much faster to wipe, restore or install a ROM, no more lag to format...
Ok
I believe in you men
If you say that this no affect anything, that's fine by me
Regards
Enviado desde mi Moto MAXX mediante Tapatalk
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
baybutcher27 said:
Update my source.
I can now compile TWRP from CM, Mokee and Omni source's.
Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.
My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.
Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.
+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
Click to expand...
Click to collapse
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Jejejeje
Regards
Enviado desde mi Moto MAXX mediante Tapatalk
icondeg said:
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it
A kernel that we can use is the second dream of this forum
Click to expand...
Click to collapse
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
ChazzMatt said:
@w4tchout
@Skrilax_CZ
Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...
I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
Click to expand...
Click to collapse
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
##W4TCH0UT## said:
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
Click to expand...
Click to collapse
I don't know much about Kernel yet so i cant see what is going wrong in yours...
But i find a workaround, to compile the recovery.img without compile the boot.img i generated a boot.img but use pre build dt + kernel.
That way i can compile recovery in under 13 min and without a kernel folder in the source, before it take over 30, and when i'm resolving bug and error, how much fast i can produce a image better.
The workaround i copy from victara and put in the omni folder of my device source, is need the mkbootimg.mk + dtb (dt image renamed) + kernel.
Then check BoardConfig.mk kernel lines, the dt and kernel i use from a previously build of my on, after you have one no need to compile the kernel every time...
Don't know if this will help but this way you may grub a previously working dt + new kernel or vice versa, and combine to see what works.
My CM source folder is working but not update do to that yet but i believe will work in others source other then omni.
if something work or not let me know.
I finished all the tested with TWRP compile in omni source, i update the download link.
No need to change TWRP unless you use a encrypted device, or you wanna to test it.
Put a note about encryption on 2# post.
If any bug found let me know.
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
respider said:
glad to see someone resumed/restarted TWRP work for Maxx. Nice job buddy!
Unfortunately my Maxx was stolen back in Brazil so I wont use this as much as you guys.
Click to expand...
Click to collapse
too bad bro
i hope you're ok
regards!
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo.
Important info:
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4
- Note: Warning! You are the only responsible of your actions, and especially of your use of your phone. Neither I, neither XDA, are responsible of your handling with your phone.
- Note: You must have unlock your bootloader on sony's page
- Note: You need to use the stock bootloader. If you switched to the Open Device Bootloader (D2203), please flash again the old bootloader. Here you have FTF file: (https://drive.google.com/file/d/0B07I-JdP5dQzSWs3SW1uYXVsWjg/view?usp=sharing). If you don’t remember the process, you can check it on Google.
Working
All
Almost working
Cameras are not fully working. You can take panorama pictures but no videos nor photos (with Snap app). In some other apps you can take them sometimes. In cameringo for example you can take everything. Fixed on V4!
Known issues
WiFi MAC address is a default address because TA is not being read yet. We are working to fix it. This only makes that some WiFi networks does not allow your phone to connect because another device with the same address is connected, but this is not usual so you shouldn't have problems with that. Fixed on V4!
Audio bugs:
Songs may pause randomly after some time and continue after some secs.
Some games might have a laggy audio problem (Pokémon Go for example).
Download
You have to download the latest version of boot.img, recovery.img and system.img or flashable zip from this link https://drive.google.com/drive/folders/0B07I-JdP5dQzM1FRbXY4bGt4VzQ?usp=sharing
For Google apps (Play Store, Google account...) go to http://opengapps.org/, choose Arm for Android 7.1 and select any variant you want. We recommend Pico variant as is the smalles one (you can choose stock if you want Pixel launcher).
Install
You need to install adb and fastboot. If you don’t know how to do that, click on the link down below.
https://forum.xda-developers.com/showthread.php?t=2588979
Then, in your file explorer, go to « This computer » and search for the file « adb ».
Next, put files in the folder « adb ». Hold shift and click (right click). Then click on « open terminal » or do « cd » (you need to find the location of your file « adb »).
Boot your phone in Bootloader/fastboot (this is the exact same thing but with different names depending on how you call it).
Before all, you have to start cleaning the device so do a wipe then:
In the terminal, type the command « fastboot devices »
You should see something like this for example :
Code:
CVH7N15B11004115 fastboot
If it isnt’t the case
go to Device Manager
Find your phone
Click on properties
Update the driver for your phone
Choose « Bootloader interface » and retry the command « fastboot device »
Now, you’ve done a big part of the work! You only have to type the following commands.
Commands
Code:
1. fastboot flash boot "name of boot".img
2. (Starting from V4 - 2020-01-23) fastboot flash FOTAKernel "name of recovery".img
[COLOR="SeaGreen"]3. Boot TWRP with Vol - and flash LineageOS zip[/COLOR]
[B][COLOR="Red"]IMPORTANT:[/COLOR] Only if Magisk was automatically installed after flashing LineageOS zip and after the first reboot the ROM is not booting:[/B] [COLOR="SeaGreen"]Flash again any boot.img with fastboot or TWRP (using "Install image" option)[/COLOR]
[COLOR="red"][STRIKE]fastboot –S 256M flash system "name of system".img[/STRIKE] (that was for v1 && v2 )[/COLOR]
You will boot into your new ROM.
IMPORTANT!
If your Xperia E3 model is D2202 or D2212 (3G-only single and dual SIM variants) you may need to flash an additional firmware zip in order to get SIM card working if it does not work after the first boot. Here you have the link:
https://drive.google.com/drive/folders/0B07I-JdP5dQzRG83U2d2aXBmUWM?usp=sharing
Note that there is a zip for each variant, but this is only to avoid confusion. Both are the same zip and you can flash any of them.
Extras
Now all you have to do is to flash the GAPPs in the recovery.
For Magisk go to https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
and download Magisk app and zip (ONLY FOR VERSIONS BEFORE V4: using the boot named Magisk) and its corresponding Magisk version.
Contributors
@rmnhg Ramón Hernández
@infus38 Thomas
@Konstantinosj77
@galaxyfreak
@adfad666
@vinay
@jerpelea
@Ｄｈｒｕｖ
@jpzex
@Nicklas Van Dam
@madcodez
Changelog
- note only last change will be post ( change log for v1 and v2 was remove )
New release 14/02/20 v4.1
Fixed a sensors bug introduced on V4. Now sensors should work as before.
New release 23/01/20 v4
Recovery is now independent from Boot partition! Now you should flash recovery image to FOTAKernel using fastboot or to "recovery" partition using TWRP. With this measure you can flash any Magisk version without waiting us to update boot.img.
Camera fully working now! Torch also works. The only thing you can't do is to enable Noise Reduction on Snap as it is not supported on Stock ROM
Bluetooth and WiFi addresses are now fine. They should be the same as the stock ones.
Compass may work better.
New release 06/01/18 v3
Tethering works now (in WiFi, BT and USB)
NFC works perfectly now
Now no user needs to flash additional firmware blobs This is not always working.
Camera working partially (I recommend you taking photos with panoramic mode and videos with other apps, like Instagram)
TWRP 3.2.1
Magisk v15.2 is now supported
Sony's framework is preinstalled, you are able to download Sony's Apps from Google Play
Safety net passed using Magisk+Magisk Hide
XDA:DevDB Information
LINEAGE-OS OMSv7, ROM for the Sony Xperia E3
Contributors
infus38, rmnhg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: V4.1
Stable Release Date: 2020-02-14
Created 2018-03-23
Last Updated 2020-02-14
Screenshots, do you have? And steal in development?
eladiocesar said:
Screenshots, do you have? And steal in development?
Click to expand...
Click to collapse
Yes i have screenshots i can not now post them the rom work and is very stable you Can try
When I give the 2nd command, a list of commands shows up. What to do?
Edit: Resolved by @infus38 Thomas
First Of all Thanx Everyone Who Has Contributed in the making of this ROM i m glad that Dev Has not left the Users Of E3 in the dark.
So,I hv a Xperia E3 D2203 18.5.0.C.19 Currently i m on Cyanogen 11 ROM UNOFFICIAL.
I hv some questions regarding this ROM-
1-Does this ROM hv any Recovery Installed?
2-This ROM does not hv root access so if i want root cn i flash the SuperSU Zip 2.79?
3-Will u make a flashable Zip Package Of via Recovery for this ROM?
4-Do i need to perform a Wipe Data/Factory Reset in Recovery before flashing this ROM?
5-Are there any Special Features In this ROM?
6-Which Gapps Should i Flash with this ROM?
7-Does This ROM support Substrantum Theme Manager?
I think that's It.
Thanx In Advance.:fingers-crossed::fingers-crossed:
..
device dosn't boot only boot animation are show(D2202) please help.
edit-solved
priyesh9 said:
device dosn't boot only boot animation are show(D2202) please help .
Click to expand...
Click to collapse
We tested on each variant this rom without problem, you can quote me exactly what you did in private message pleas
I will take care of your problem do not worry
Edit now solved
UPDATE: now you have boot.img with latest TWRP included
Edit-Solved
Ali Haide 001 said:
First Of all Thanx Everyone Who Has Contributed in the making of this ROM i m glad that Dev Has not left the Users Of E3 in the dark.
So,I hv a Xperia E3 D2203 18.5.0.C.19 Currently i m on Cyanogen 11 ROM UNOFFICIAL.
I hv some questions regarding this ROM-
1-Does this ROM hv any Recovery Installed?
2-This ROM does not hv root access so if i want root cn i flash the SuperSU Zip 2.79?
3-Will u make a flashable Zip Package Of via Recovery for this ROM?
4-Do i need to perform a Wipe Data/Factory Reset in Recovery before flashing this ROM?
5-Are there any Special Features In this ROM?
6-Which Gapps Should i Flash with this ROM?
7-Does This ROM support Substrantum Theme Manager?
I think that's It.
Thanx In Advance.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
1=For now no we have some problem,But later yes(edit The recovery has just been officially run from 18pm French time , You need to download the boot.img again to get the recovery if you have to download before )
2=Yes this ROM can be root now :flash this in recovery http://tiny.cc/latestmagisk and install apk http://tiny.cc/latestmanager
3=just with the bootloaderfor now you can flash the rom , not with the recovery (you will be able to read the topic all the same I gave myself trouble) ,for now 2 .img same aosp but follow the topic , soon the rom will be just a .zip we worked on
4=Yes you must all whyp but your sd card is not neccesaire of format
5=yes just lineage os
6=you can choos this for gapps http://opengapps.org/ choos arm 7.1 pico and flash in recovery (you can choos stock if you want pixel luncher)
7=This rom supports the substratum legacy theme soon the support of full omsv7
Thank you for your comment,If you have any other question you can ask them
infus38 said:
1=For now no we have some problem,But later yes(edit The recovery has just been officially run from 18pm French time , You need to download the boot.img again to get the recovery if you have to download before )
2=Yes this ROM can be root now :flash this in recovery http://tiny.cc/latestmagisk and install apk http://tiny.cc/latestmanager (If this does not work, wait for the next version of the boot.img it will have to include the root with magisk)
3=just with the bootloaderfor now you can flash the rom , not with the recovery (you will be able to read the topic all the same I gave myself trouble) ,for now 2 .img same aosp but follow the topic , soon the rom will be just a .zip we worked on
4=Yes you must all whyp but your sd card is not neccesaire of format
5=yes just lineage os
6=you can choos this for gapps https://www.androidfilehost.com/?w=files&flid=171931&sort_by=date&sort_dir=DESC
7=This rom supports the substratum legacy theme soon the support of full omsv7
Thank you for your comment,If you have any other question you can ask them
Click to expand...
Click to collapse
Two Question-
1-IS this Rom Support Substratum theme Manager at this Current Stage?
2-Can I flash Those SuperSU Addons Which Are Given On The Official Page Of LineageOS?
Thanks For Ur Help.:fingers-crossed::fingers-crossed:
Ali Haide 001 said:
Two Question-
1-IS this Rom Support Substratum theme Manager at this Current Stage?
2-Can I flash Those SuperSU Addons Which Are Given On The Official Page Of LineageOS?
Thanks For Ur Help.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
1=This rom for now supports partially the substratum( just leagcy) but soon full omsv7 suport
2=for now the boot.img is in the process of modification because any method of root does not work, but in the next verssion the root will be included with magisk su (edit now at the time in french 19 pm new boot with root on cloud you can donwload :laugh: thanks @rmnhg )
rmnhg said:
UPDATE: now you have boot.img with latest TWRP included
Click to expand...
Click to collapse
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
infus38 said:
1=This rom for now supports partially the substratum( just leagcy) but soon full omsv7 suport
2=for now the boot.img is in the process of modification because any method of root does not work, but in the next verssion the root will be included with magisk su (edit now at the time in french 19 pm new boot with root on cloud you can donwload :laugh: thanks @rmnhg )
Click to expand...
Click to collapse
So, Now I don't Need To Flash The Files (For Root Access) Which You Hv Given Me Before
Thanx In Advance.
Downloading Now.
Ali Haide 001 said:
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
---------- Post added at 06:14 PM ---------- Previous post was at 06:08 PM ----------
So, Now I don't Need To Flash The Files (For Root Access) Which You Hv Given Me Before
Thanx In Advance.
Downloading Now.
Click to expand...
Click to collapse
Yes just flahs lates boot_twrp_root.img ??
Ali Haide 001 said:
Thank You Bro, Now We Hv TWRP Included :fingers-crossed::fingers-crossed::fingers-crossed:
Already Pressed The Thanks Button.
One Thing -
1-What Is The Version Of TWRP?
Click to expand...
Click to collapse
You're welcome ?. TWRP is in it's latest version (3.1.1). Material design and multi language.
infus38 said:
We tested on each variant this rom without problem, you can quote me exactly what you did in private message pleas
I will take care of your problem do not worry
Click to expand...
Click to collapse
edit -solved
I was able to flash this ROM. I followed the instructions stated above but my d2203 was just stock at the LOS boot logo. I don't know what I did wrong. I came from stock KitKat rom before I flashed this. If that helps. HELP PLS! I really wanna try this ROM so badly
thanks @infus38 Thomas for helping me solve the problem
Screenshots
Note I'm using custom launcher and custom theme (flux substratum theme)
My review:- I'm using this ROM from 4 days and this ROM is totally awesome. Since I don't use Camera of this device that much I love this ROM.
infus38 said:
Yes just flahs lates boot_twrp_root.img
Click to expand...
Click to collapse
Hey,One More Thing-
1-Do I Need To Flash This ROM above Stock ROM Or It Does Not Matter Cause I Am On CM 11 Unofficial Flamingo?
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
Ｄｈｒｕｖ said:
Screenshots
Note I'm using custom launcher and custom theme (flux substratum theme)
My review:- I'm using this ROM from 4 days and this ROM is totally awesome. Since I don't use Camera of this device that much I love this ROM.
Click to expand...
Click to collapse
So,You Have Flashed This ROM.
How Is The Battery Life?
Can You tell Me What are The Features In This ROM (By Features I mean The Features Which are in cm Roms Like Center Clock,Privacy Guard,Performance Profile,Etc)?
Is Substratum Theme Manager Working Fine?
Thanks In Advance.
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
******************************************
Hi there,
This is the official build (beta) based on TWRP sources and xiaomi blobs ... fully working !
(Mi CC9 meitu Edition)
!!! IT'S NOT MY PROBLEM, IF YOU DON'T READ AND FOLLOW MY INSTRUCTION CAREFULLY, IF YOU DON'T HAVE TIME FOR THIS, OR IF YOU FLASH SOMETHING OR DO A MANIPULATION I DIDN'T MENTION HERE !!!
Installation Procedure (first time) :
- Unlock your bootloader D)
- Enable ADB from your Official MIUI Developer option
- Plug your USB cable to your Windows PC and type :
adb reboot bootloader
- type then :
fastboot flash recovery twrp-3.3.1-0-vela-final (auto-decrypt).img (rename your image just by twrp.img)
fastboot flash vbmeta vbmeta.img
fastboot reboot (keep Vol+ pressed until you see TWRP splash)
- Wait for decrypting ... (if already you set a lockscreen pattern or a fingerprint)
- Format Data (button on the right) + Type "yes" on the keyboard popup
- Reboot
- To boot TWRP from MIUI : reboot menu + keep Volume UP pressed.
- To boot from phone off : power button + Volume UP
TWRP can now auto-decrypt your crypted /data partition so you can make backup with no issue.
This is a big fix that prevent to loose your fingerprint and pattern ...
For MIUI users, you must flash the fstab.zip fix after flashing your MIUI rom !!!
Enjoy ! :good:
Update : 2019-11-05
-version : 3.3.1-0
-busybox update
-terminal fixed
-stable and optimized : setting lockscreen pattern and fingerprint on the first boot is no longer needed !
BE SURE WHEN YOU WIPE YOUR DATA, YOU KEEP THE "4 FOLDERS BELOW + .layout_version". THESE ARE YOU ENCRYPTION DATA. IF YOU DELETE THEM, YOU WILL NOT BE ABLE TO RESTORE YOUR DATA BACKUP UNTIL YOU FORMAT YOUR DATA AGAIN.
TRICK TO SAVE YOUR LIFE : ALWAYS KEEP YOUR BACKUPS ON THE EXTERNAL STORAGE !!!
!!! This recovery is only for flashing "vela" roms in the future. Don't use it to flash pyxis roms. For this, use pyxis recovery instead !!!
Download
link
XDA : DevDB Information
TWRP, Tool/Utility for the Mi CC9 meitu Edition (vela)
Contributors
gringo80
Source Code 1 : https://github.com/TeamWin
Source Code 2 : Prebuilt Recovery Kernel from MIUI
Version Information
Status : Stable
Release Date : 2019-11-05
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
yotamy said:
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
Click to expand...
Click to collapse
It's working now. Thanks
I think it works
gringo80 said:
It's working now. Thanks
Click to expand...
Click to collapse
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
yotamy said:
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
Click to expand...
Click to collapse
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
thanks. Some QA
gringo80 said:
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
Click to expand...
Click to collapse
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
yotamy said:
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
Click to expand...
Click to collapse
this is not a bug. you have to format data after installing twrp.
from twrp homescreen, go to :
Wipe > Format Data (on the right) > type yes from the keyboard
TWRP don't support backup/ restore from encrypted files/folders. You must decrypt by formatting data !
Reboot to system. Install and config your rom then go TWRP to make backup !
Always put your roms and zip on the External SD Card... or sideload them by adb cmd from your windows PC !
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
sorry. i dont understand
gringo80 said:
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
Click to expand...
Click to collapse
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
yotamy said:
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
Click to expand...
Click to collapse
lol
it's inside the zip. go to my mediafire link. you will find everything
yes you flash it on twrp
i cannot thank you enough
thanks again
New Update (TWRP auto-decrypt)
yotamy said:
i cannot thank you enough
thanks again
Click to expand...
Click to collapse
Please update you TWRP ! (Highly recommended). Read OP carefully !
Thanks
:good:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
yotamy said:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
Click to expand...
Click to collapse
Yes, the fingerprint and the lockscreen pattern.
Follow the instruction on the OP !
Are the font files related to this twrp?
There are 2 font files in the link
yotamy said:
There are 2 font files in the link
Click to expand...
Click to collapse
NO, for the roms !
Speaking of roms.....
yotamy said:
Click to expand...
Click to collapse
work in progress
now its working good
gringo80 said:
work in progress
Click to expand...
Click to collapse
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
yotamy said:
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
Click to expand...
Click to collapse
Don't delete TWRP folder on your internal storage, to keep your TWRP settings.
3 way reboot is framework related. Sorry i don't support MIUI for now because i'm busy with GSI. Try to download "Simple Reboot" from the playstore.