Database Info

[DEV][RECOVERY] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 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.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.

DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

About the current build:
STABLE.
Reboot to system bug now fixed.

Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2

TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail

TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.

My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.

Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:

Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail

TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved

belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail

jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience

jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one

belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail

jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.

hi anyone have got it if possible in rar zip for this recovery.

ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.

swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail

Ok yesterdeay install with terminal emulator thanks.

[RECOVERY] TWRP 2.8.7.0 for Onda v919 Air CH DualOS

Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Or you can use this method: http://forum.xda-developers.com/android/development/root-how-to-root-access-tablet-onda-t3396299
Download

Work fine!!
I just installed!
Excellent!
Thank you

ViAlexSt said:
Actually the first working version of custom recovery for Onda v919 Air CH DualOS -> TWRP 2.8.7.0.
This is the port TWRP for Teclast x98Pro provided by user Dani Basabe on this resource, for which many thanks to him, honor and respect.
All basic functions are working: touch, install, wipe, backup and restore, OTG-function (can make a backup on a flash drive) & etc.
Only no vibration feedback. I suppose it's not the worst thing in life...
With the appear of TWRP can install different system mods, for example, audio. After taking a backup copy of the system, of course.
I have to say: xposed on this device doesn't run! After installation bootloop.
Installation:
Place twrp.img in the root of internal /sdcard and run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/android_recovery
(I described the usual and most simple way for me. With devices through adb-interface I'm working with Total Commander with the plugin. We can try to install TWRP through fastboot commands:
adb reboot bootloader
fastboot flash recovery twrp.img)
To enter in TWRP after selecting "Android" in the main boot menu, hold down volume "-" before the advent of the service menu where the volume keys select "Recovery Mode" and press the power button.
Download
Click to expand...
Click to collapse
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.

mismamente said:
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
The difficulty is that I have sound. How do I determine whether sound on other devices? I have tried to use Viper-mod, but for some reason it stubbornly refuses to install the driver. You can try different audio mods from this forum, after making the system backup. Mods based on Viper most likely will not start, therefore it's necessary to try with another engine.
I currently run an interesting RemixOS: version 2.0 starts successfully, but no wifi and sound. While thinking about it, what libraries to take from stock firmware.

mismamente said:
Thank you very much!
Please, try to do the mod to enable audio on latest firmware with old bios.
Click to expand...
Click to collapse
Try Remix OS - boot 20160429, but system audio libraries other.

ViAlexSt said:
Try Remix OS - boot 20160429, but system audio libraries other.
Click to expand...
Click to collapse
thank you, I will try.

I have a cube tablet which has the same processor (intel bay trail), how did you port the twrp? I would like to do the same from my stock recovery (if you don't mind). Thanks. All I want is advice/tips... The recovery that I've ported just reboots when entered on recovery from Droidboot.

XDA_h3n said:
I have a cube tablet which has the same processor (intel bay trail) ... The recovery that I've ported just reboots when entered on recovery from Droidboot.
Click to expand...
Click to collapse
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.

ViAlexSt said:
I can't say for sure how identical processors in terms of porting TWRP (Cherry Trail <=> Bay Trail). May need more significant changes to the original TWRP. General method for porting one: from stock recovery move to port kernel and recovery.fstab. Further it's necessary to look and compare other files. Unpack/pack images possible using Carliv Image Kitchen for Android. But in your place I would have found TWRP for a more suitable tablet. What is your model? Maybe I will prompt the object of porting.
Click to expand...
Click to collapse
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
I've been using the Teclast X98 twrp, as their rom actually works on our tablet without any modifications needed other than a couple of framework changes with resolution as it causes issue with the system ui being bigger.
Anyhow, thanks for your help, I'll try to see what I can do from the tool you've provided, as I used to unpack and repack the images using another kitchen tool. It quite off-topic from this thread; thanks for you help. Here's my stock recovery if you do have free time.

XDA_h3n said:
Well, I've tried the method of replacing zimage and dtb images and the recovery.fstab, which was the image I created before. It just doesn't work. I would think it's something to do with an partition layout issue.
Click to expand...
Click to collapse
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!

ViAlexSt said:
I'm pretty sure that your chances of success will increase significantly if you select TWRP for a more suitable machine. I suggest to try TWRP for Onda v820w, as most similar devices Cube iWork7: Bay Trail+Android 4.4.4 (see attachment; autor kostyamat@4pda). About dt.img: I can't tell you how to do when porting, but if you are compiling TWRP this point is taken into consideration when editing BoardConfig.mk. What concrete advice I can't give, my recovery/TWRP hasn't dt.img.
For example: I to run on Onda TWRP 3.0.2.0 for Cube iWork8 Ultimate did (unpacked Carliv Imagetool):
1. Replaced all: recovery.img-base, recovery.img-cmdline, recovery.img-kernel, recovery.img-kernel_offset, recovery.img-pagesize, recovery.img-ramdisk-compress, recovery.img-ramdisk_offset, recovery.img-tags_offset.
2. In folder 'ramdisk':
- etc/recovery.fstab -> edited blocks like me;
- replaced: file_contexts, selinux_version, service_contexts, default.prop;
- file names init.recovery.***.rc, ueventd.***.rc changed like me, contents are not changed.
It was enough for a successful launch. But there is a little roughness in it work, so don't share.
Successful porting!
Click to expand...
Click to collapse
Thank you a lot for all of your help
I've got it working on my tablet. I am very grateful for your help.
Recovery just doesn't mount the partitions correctly, but I'll be modifying the recovery.fstab until I'll find a way. Intel does the mount points like /dev/block/platform/intel/by-label/boot on stock recovery. I'll need to find the true location of all of the partitions, but it is fixable.
Again, I am very grateful :laugh:
Lol the original recovery.fstab from the port, has the same guid name on the partition blocks. That fixed it. Everything is mounting! Thanks.
Anybody with an Linx 7 or a Cube iWork 7 I'd posted in the linx forums and there is a tool that should do everything for you soon

[Recovery] TWRP 3.0.2-0 for phicomm energy 2 e670 msm8909

Team Win Recovery Project 3.x, or twrp3 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.
CHANGELOGS :
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: 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.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
TWRP 3.0.2.0
E670 Recovery
How to install ? :
1. Extract The Zip File
2. Open Extracted folder and hold shift and right click and select "Open command window here"
3. Then connect your device to the System and make sure you have USB debugging enabled.
4. Type "adb devices" to check if the device is connected.
5. You will get a prompt in your device asking permission to allow USB debugging just click OK and allow.
6. Type "adb devices" again to see if ur device is connected or not and if its connected it will show something like this:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0123456789ABCDEF device
6. Make sure recovery.img is in the same adb and fastboot folder
7. Type "adb reboot bootloader" to boot into fastboot mode.
8. Use this command to flash the recovery:
Code:
fastboot flash recovery recovery.img
You will get something like this:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12060 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 0.656s
9. Boot into the system by using this command:
"fastboot reboot"
10. To boot into TWRP using adb use this command:
"adb reboot recovery"
11. If you wanna use hardware button combination :
a. Power Off your device
b. Press and hold volume UP + Power button till you see the PHICOMM Bootlogo and leave power button while keep holding the volume UP button till you boot into TWRP.
12. Download SuperSU.zip and flash it on TWRP to root your device
Sources
- android_device_phicomm_e670-android-5.1
Bugs ?
- No Bug

Bro you have twrp for phicomm energy 653

nawazmomin said:
Bro you have twrp for phicomm energy 653
Click to expand...
Click to collapse
No

Bro help us
Plss build twrp for Phicomm Energy 653 (Energy ).
We hardly need this ...plss help us ..

Help to built recovery
Hello sid,
I am trying to port custom recovery for phicomm e653, stuck on very 1st step.
I need stock recovery for that, but unable to find it in system, guide me please.
Sent from my PHICOMM E653 using XDA Free mobile app

All files of Phicomm energy 653
navid.ans1988 said:
Hello sid,
I am trying to port custom recovery for phicomm e653, stuck on very 1st step.
I need stock recovery for that, but unable to find it in system, guide me please.
Sent from my PHICOMM E653 using XDA Free mobile app
Click to expand...
Click to collapse
here is all necessary files for porting Phicomm e653 recovery, files include boot.img recovery.img partitions info etc.
link 4shared.com/zip/1G7DwXnTba/Phicomm_Energy_E653_Files.html

Thankyou brother, I will have a look and report to you.
Sent from my PHICOMM E653 using XDA Free mobile app

sameerchapai said:
here is all necessary files for porting Phicomm e653 recovery, files include boot.img recovery.img partitions info etc.
link 4shared.com/zip/1G7DwXnTba/Phicomm_Energy_E653_Files.html
Click to expand...
Click to collapse
With your help ported custom recovery for e653, unfortunately unable to boot into fastboot. If i try from recovery there is an option "reboot to bootloader" after i select that device reboots and stuck to phicomm logo. secondly when i directly give commands from adb as " adb reboot bootloader" same thing happens, device stucks on phicomm logo. can you guide me how to see partitions. i want to learn this things.

Plss check 4shared link ..partitions files is there on zip ..jst extract zip.
Thnx
---------- Post added at 08:30 PM ---------- Previous post was at 08:26 PM ----------
navid.ans1988 said:
With your help ported custom recovery for e653, unfortunately unable to boot into fastboot. If i try from recovery there is an option "reboot to bootloader" after i select that device reboots and stuck to phicomm logo. secondly when i directly give commands from adb as " adb reboot bootloader" same thing happens, device stucks on phicomm logo. can you guide me how to see partitions. i want to learn this things.
Click to expand...
Click to collapse
If u have ported then plss provide me

I just tried , pulled out recovery.img from system, it was of 30mb. Have you figured out why I am not able to boot into bootloader or fastboot. Do you operate same handset ? .
Sent from my PHICOMM E653 using XDA Free mobile app

navid.ans1988 said:
I just tried , pulled out recovery.img from system, it was of 30mb. Have you figured out why I am not able to boot into bootloader or fastboot. Do you operate same handset ? .
Sent from my PHICOMM E653 using XDA Free mobile app
Click to expand...
Click to collapse
Yea i having same handset but unfortunately while updating xposed installer software got bricked and completely dead for many days. After searching lot finally found fastboot rom but it was Deutsche version ..flashed with qpst tools all working fine but network not working.
bro plss be careful ok ..dnt repeat anything wrong like me coz no official roms available and vry bad software support from phicomm service

sameerchapai said:
Yea i having same handset but unfortunately while updating xposed installer software got bricked and completely dead for many days. After searching lot finally found fastboot rom but it was Deutsche version ..flashed with qpst tools all working fine but network not working.
bro plss be careful ok ..dnt repeat anything wrong like me coz no official roms available and vry bad software support from phicomm service
Click to expand...
Click to collapse
Thankyou for advice , that means there are fastboot problems in this device.
Sent from my PHICOMM E653 using Tapatalk

navid.ans1988 said:
Thankyou for advice , that means there are fastboot problems in this device.
Sent from my PHICOMM E653 using Tapatalk
Click to expand...
Click to collapse
Plss can u send me ur stock boot and recovery files?

Do you want full stock rom, I have uploaded to drive, provide your email id
Sent from my PHICOMM E653 using Tapatalk

navid.ans1988 said:
Do you want full stock rom, I have uploaded to drive, provide your email id
Sent from my PHICOMM E653 using Tapatalk
Click to expand...
Click to collapse
My email [email protected] wr u got full stock rom?

I had some issues , so phicomm India page on Facebook shared it with me, I will add you to download it and will share a link to you.
Sent from my PHICOMM E653 using Tapatalk

Ohh i already tried with that rom update file ..not updating with my recovery yar ..plss provide me boot and recovery files from ur phone plss
---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------
Is this same update file which is available on phicomm.in service center ?

Yes, I downloaded it from there, flash it via adb , I did it too it worked for me
Sent from my PHICOMM E653 using Tapatalk

Ok guide me how did u flashed?

sameerchapai said:
Ok guide me how did u flashed?
Click to expand...
Click to collapse
Download fastboot folder I just shared to you, put ROM package in fastboot folder, run adb.bat and fastboot.bat once. Then hold shift + right click anywhere in that folder(shift + right click on empty space), then click open command window here. After that cmd will open. Type adb devices, it will show device attached. Now put your device in recovery mode. Go to install via adb sideload. Then type adb sideload TF Update.zip in cmd window opened earlier .
Flashing will start, after you get succeeded, reboot device.
Sent from my PHICOMM E653 using Tapatalk

[TWRP] TWRP 3.4-0-0 For Blu G90 G0310WW [MT6765][Android 10]

First released twrp for BLU G90 phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
**Solved with new tree file**--data decryption is not working, so not able to read or backup internal storage.--
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device Tree :
New
GitHub - mrmazakblu/device_PBRP_BLU_G90_G0310WW at TWRP
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Download :
Releases · mrmazakblu/device_PBRP_BLU_G90_G0310WW
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Old
https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW
Download : https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW/releases

ADB Sideload is also broken.

Shananiganeer said:
ADB Sideload is also broken.
Click to expand...
Click to collapse
Most likely due to no able to read/ write to /data there is no place to temp store the zip.
Working on alternative options at the moment, as I am having trouble getting build correct to make decrypt.
Alternative is a modified /vendor.img, so device is not encrypted. But this of course is less secure.

I reformatted /data so it was unencrypted, but still couldn't use adb sideload. I was able to use adb push to put files onto the phone, but that didn't end up mattering as without rw to /system I can't install gapps XD. I'll have some time this weekend to take a look at things and try and help debug the decryption.

Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.

mrmazak said:
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
Click to expand...
Click to collapse
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.

Ivisibl3 said:
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Click to expand...
Click to collapse
To modify it "live" yes maybe.
You can modify the extracted system, as I did , using linux mount, and flash the system back modified, just like a gsi rom.
But for root, can't say.

On the latest build, was able to mount /system r/w. And successfully change the contents of it.
The patches in twrp source is not finished yet, so normal zip installs are not coded. But using adb shell (or TWRP terminal ) seem to be working.
This New build to be uploaded on github device source, as release "test build 9"

I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Well, the first thing I'm concerned with here is , I'm not sure if THIS TWRP will work on the g90 pro.
But it might be possible. I was able to mount system as r/w on my g90 in TWRP.
You would need to fastboot flash --disable-verity vbmeta and vbmeta_system to prevent red state bootloader lockout.

Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.

Shananiganeer said:
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Click to expand...
Click to collapse
The stock /product partition is not needed in non stock roms. Google gsi flashing guide tells show to delete logical partition product.
Code:
fastboot delete-logical-partition product
This is probably what is needed.
Don't know about your plan to increase stock super.img. no idea about why you mention boardconfig.mk

This TWRP is before the patch for TWRP fastbootd, so it is not included. I have resynced source, and will see if new build works, or not. If it does will post new release.

I mentioned BoardConfig.mk because the size of the super partition is listed there, but you were totally right about the product partition and I was able to flash LOSQ+gapps after deleting it. Thanks for the assist, and your work on porting TWRP to this awesome device! Will continue to keep an eye on your work as TWRP finalizes their support for Android 10.

Will this work for the G90 Pro? My guess is not but figured I'd ask

KryptekKnight said:
Will this work for the G90 Pro? My guess is not but figured I'd ask
Click to expand...
Click to collapse
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.

mrmazak said:
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
Click to expand...
Click to collapse
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide

KryptekKnight said:
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
Click to expand...
Click to collapse
I have no idea about gcam

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Sorry OP.....
I need to get 01 post of your topic to report on custom recoveries on the G90 Pro.
For new users, you should know about the Android 10 permission structure.
In TWRP or PBRP, through the File Manager, it is not possible to copy files to the superpartition. But you can copy files from the superpartition to the internal SD card.
Therefore, to modify files from the super partition, it will be necessary to extract the super partition and extract system-product-vendor to then carry out the modifications and repackage.
Using Havocv3.11 the volume issue dissapears...........

Well all, thanks to @lopestom , we may soon have a new device tree to build recovery from , and data decryption is working on first test img. New recovery would be pbrp instead of twrp.

Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP for Poco X3 Pro Global/Indian (vayu/bhima)
touch and adb work
SD card and USB OTG are working
Decryption is working
Send me a beer: Crypto(Preferred) | PayPal
Tree: https://github.com/TeamWin/android_device_xiaomi_vayu
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocox3pro.html
Unofficial 12 builds: https://www.pling.com/p/1833617/

Nebrassy said:
Hello, this is an alpha build of TWRP, for Redmi note 10 Pro Global/Indian/Indian Pro Max (sweet/sweetin)
Click to expand...
Click to collapse
Are you sure you posted in the right subforum?

kamild_ said:
Are you sure you posted in the right subforum?
Click to expand...
Click to collapse
Yeah, I just copied it from my other thread and forgot to edit a part of it

Wow finally Decryption twrp for x3 pro..

anyone try in Poco X3 PRO ?
Thanks.

Can it be installed from the current Recovery on a Poco X3 PRO? Or is it not permanent?

can I flash this if I have arrow recovery?

Nice, thanks to the dev. Is there a site/tutorial which explains the differences of the current recovery systems including why for example Arrow OS has its own?
I guess device memory setup,encryption and OTG plays a big role but since I used TWRP the first time years ago I did not keep up with Android/Recovery development much.

Well, I guess that escalated quickly
This is awesome news when it comes to custom recovery.

Can flash this recovery if im on orangefox with xiaomi.eu?
No problem when boot after flash new recovery? Thanks

Can't wait for version with adb sideload working

finally internal storage working.. great job

Can I install it like a image through my present Orangefox recovery ?

Luko69 said:
Can I install it like a image through my present Orangefox recovery ?
Click to expand...
Click to collapse
yep, just done that, decryption works so I can finally access the DATA partition.

Installed via previous Orangefox, working OK, decryption OK.

Using TWRP to install OTA Updates

I have tested it flashing Arrow vanilla version.
1) Able to read and write from Pc to internal storage and sd card.
2) Able to flash rom and Gapp separately.
3) Able to backup and restore.
It is almost like a perfect twrp to me. Thank you.

Bug report :
Following guides on xiaomi.eu and xda here, before flashing ROMs, "format data".
Data is gone.
"Put the ROM into internal storage."
Connect to PC, internal storage inaccessible from PC !!!
Internal storage was accessible before data wipe.
I tried to boot into system, MIUI loaded, initialization setup done. Reboot to fastboot, flash recovery and boot twrp img, then internal storage accessible again.
So, before flashing a rom, format data.
Done, oh no, internal storage inaccessible by PC AGAIN !!!
Now I'm forced to install rom with microSD, if formatting data is required "before flashing".
I got 3 of this phone, 2 of the are having same issue.
The third is waiting to unlock bl.
Arrow's guide ([ROM] guide, not [GUIDE] guide) had this "wipe data" step "after" zip flashing. So this works.
I'm just wondering if all guides about formatting before flashing rom zip is the must order.

pl1992aw said:
Bug report :
Following guides on xiaomi.eu and xda here, before flashing ROMs, "format data".
Data is gone.
"Put the ROM into internal storage."
Connect to PC, internal storage inaccessible from PC !!!
Internal storage was accessible before data wipe.
I tried to boot into system, MIUI loaded, initialization setup done. Reboot to fastboot, flash recovery and boot twrp img, then internal storage accessible again.
So, before flashing a rom, format data.
Done, oh no, internal storage inaccessible by PC AGAIN !!!
Now I'm forced to install rom with microSD, if formatting data is required "before flashing".
I got 3 of this phone, 2 of the are having same issue.
The third is waiting to unlock bl.
Arrow's guide ([ROM] guide, not [GUIDE] guide) had this "wipe data" step "after" zip flashing. So this works.
I'm just wondering if all guides about formatting before flashing rom zip is the must order.
Click to expand...
Click to collapse
After formatting data, you need to reboot twrp, I believe it tells you that while formatting

Nebrassy said:
After formatting data, you need to reboot twrp, I believe it tells you that while formatting
Click to expand...
Click to collapse
I did reboot again into twrp, even entering fastboot and boot twrp img, but same results if I never let the miui initialize once after formatting.