[RECOVERY][XGO] TWRP 2.7.0.0 touch recovery [2014-03-21] - Sony Xperia P, U, Sola, Go

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Introduction:
Team Win Recovery Project 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.
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
Decryption of /data
Easy selection of internal/external storage
Portal Link: http://www.xda-developers.com/android/twrp-recovery-now-available-for-the-xperia-u-p-go-and-sola/​
Click to expand...
Click to collapse
Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (may work on older version of android. I don't own Xperia Go so didn't test it. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
To ROM makers
if you include it in your ROM, please give proper credits cause I've spent almost a month trying to port this.Thanks.
Download
latest zip => recovery_install_20140321.zip - 6.39 MB
latest ramdisk => View attachment initrd.gz
Source
TWRP source -> https://github.com/omnirom/android_bootable_recovery
device tree -> https://github.com/Agontuk/android_device_sony_lotus
Credits
all teamwin members, especially @Dees_Troy for giving me constant advice
@munjeni for his support and answering all my questions

Changelog 15/03/2014
booting
full touch working
adb working
usb mass storage not working
fix path for battery percentage and charging status
Changelog 21/03/2014
reboot to recovery/bootloader from twrp fixed
reboot to recovery/bootloader from rom fixed
mount usb mass storage should work now
added battery led (not working)
Changelog 24/03/2014
all should work fine now except external storage mounting

F.A.Q
1) Are CWM backups compatible with TWRP ?
Ans: CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it.

Hi dude,
Would this override my current CWM v6.xx ( I'm using Munjeni's Cm11)?

Hukanawa said:
Hi dude,
Would this override my current CWM v6.xx ( I'm using Munjeni's Cm11)?
Click to expand...
Click to collapse
yes, it will override. @NoobCoder, would you like to share your source?

Are there any bugs in this recovery? I can test this recovery for the XGO if you'd like

NoobCoder said:
Changelog 15/03/2014
depends upon your testing. please provide feedback for
1) booting ?
2) adb working ?
3) usb mass storage working ?
4) touch working ?
5) reboot to recovery working ?
6) battery percentage and charging status show correctly ?
7) can you mount all partitions perfectly ?
Click to expand...
Click to collapse
1) booting ok
2) adb working nope
3) usb mass storage working nope
4) touch working ok
5) reboot to recovery working nope
6) battery percentage and charging status show correctly ok
7) can you mount all partitions perfectly ok

will it work for xperia sola too??
and this is my 1000th post :')

dwaipayanray95 said:
will it work for xperia sola too??
and this is my 1000th post :')
Click to expand...
Click to collapse
not yet, he update to xperia sola soon.

Hukanawa said:
Are there any bugs in this recovery? I can test this recovery for the XGO if you'd like
Click to expand...
Click to collapse
it'll be very much appreciated. I don't have XGO, so someone needs to test & report.
wan5xp said:
1) booting ok
2) adb working nope
3) usb mass storage working nope
4) touch working ok
5) reboot to recovery working nope
6) battery percentage and charging status show correctly ok
7) can you mount all partitions perfectly ok
Click to expand...
Click to collapse
are u using windows or linux ? If windows, is there any indication that the device is connected like "usb device not recognised"? Please check device manager and see if there's an device with yellow icon.

NoobCoder said:
it'll be very much appreciated. I don't have XGO, so someone needs to test & report.
are u using windows or linux ? If windows, is there any indication that the device is connected like "usb device not recognised"? Please check device manager and see if there's an device with yellow icon.
Click to expand...
Click to collapse
On testing, i use ubuntu. Adb only show ?????? No permission. Usb mass storage not detected. Mass storage does work in cwm.

wan5xp said:
On testing, i use ubuntu. Adb only show ?????? No permission. Usb mass storage not detected. Mass storage does work in cwm.
Click to expand...
Click to collapse
try this
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
NOTE: You may have to change the path to adb since you are using Superuser to start the server, it may not be in your .bashrc. It's not TWRP's problem, AFAIK.

NoobCoder said:
try this
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
NOTE: You may have to change the path to adb since you are using Superuser to start the server, it may not be in your .bashrc. It's not TWRP's problem, AFAIK.
Click to expand...
Click to collapse
okay, adb does work.

lock bootloader
can you make this work for xgo lock bootloader

guys any feedback will be appreciated to fix the bugs.

guys any feedback will be appreciated to fix the bugs.
Click to expand...
Click to collapse
Adb does work. Do you need me to get anything from adb?

wan5xp said:
Adb does work. Do you need me to get anything from adb?
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=51138429&postcount=9 to provide log. Also recovery.log too

NoobCoder said:
Check this http://forum.xda-developers.com/showpost.php?p=51138429&postcount=9 to provide log. Also recovery.log too
Click to expand...
Click to collapse
cat /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file - this give no output
cat /proc/cmdline
In booted system
Code:
startup=0x4 warmboot=0x77665501 ta_info=9,4,256 androidboot.bootloader=s1 androidboot.serialno=CB5A1L0FSB cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019 audit=1 semcandroidboot.babe1324=43423541314c30465342
In recovery
Code:
startup=0x4 warmboot=0x0 ta_info=9,4,256 androidboot.bootloader=s1 androidboot.serialno=CB5A1L0FSB cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019 audit=1 semcandroidboot.babe1324=43423541314c30465342

wan5xp said:
cat /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file - this give no output
Click to expand...
Click to collapse
just to be sure, you took the recovery log after trying to mount usb storage, right ?

NoobCoder said:
just to be sure, you took the recovery log after trying to mount usb storage, right ?
Click to expand...
Click to collapse
yeah, i tried it twice

Related

[RECOVERY][XSOLA] TWRP 2.7.0.0 touch recovery [2014-04-27]

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Introduction:
Team Win Recovery Project 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.
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
Decryption of /data
Easy selection of internal/external storage
Portal Link: http://www.xda-developers.com/android/twrp-recovery-now-available-for-the-xperia-u-p-go-and-sola/​
Click to expand...
Click to collapse
Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I don't own Xperia Sola so didn't test it. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
To ROM makers
if you include it in your ROM, please give proper credits cause I've spent almost a month trying to port this.Thanks.
Download
recovery_install_20140319.zip - 6.44 MB
latest ramdisk => http://forum.xda-developers.com/showpost.php?p=51282072&postcount=58
recovery_install_20140425.zip - 6.42 MB
Final Version => recovery_install_20140427.zip - 6.42 MB
Source
TWRP source -> https://github.com/omnirom/android_bootable_recovery
device tree -> https://github.com/Agontuk/android_device_sony_pepper
Credits
all teamwin members, especially @Dees_Troy for giving me constant advice
@munjeni for his support and answering all my questions
@cpkunki for making this thread featured in the portal
Changelog 16/03/2014
booted
full touch working
adb working
usb mass storage not working
fixed show battery capacity & charging status (+ icon next to percentage)
reboot to bootloader working (from twrp menu)
Changelog 19/03/2014
added battery led to indicate battery status
usb mass storage still not working
reboot to recovery working now
reboot to bootloader working now
Changelog 22/03/2014
internal storage is mounting
battery led works properly
added brightness slider
changed to default sony logo
Changelog 27/04/2014
Everything works fine
F.A.Q
1) Are CWM backups compatible with TWRP ?
Ans: CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it.
NoobCoder said:
depends on your feedback.
booted ?
full touch working ?
adb working ?
usb mass storage working ?
fixed show battery capacity & charging status (+ icon next to percentage) ?
reboot to bootloader working (from twrp menu) ?
Click to expand...
Click to collapse
1. YES
2. yes
3. not yet tested
4. i dont use xternal sd card but when i select mount usb storage, i cant see my sdcard on my computer
5. yes
6. when i select reboot to bootloader (from twrp menu) my phone just shutdown
and when i reboot to recovery (from phone) it takes time . . . reaallyy reaally long time (that's when i decided to force my phone to reboot)
thnx for ur work
i will include it in my next update of omni and slimkat and provide feedback ..
pingu_c660 said:
1. YES
2. yes
3. not yet tested
4. i dont use xternal sd card but when i select mount usb storage, i cant see my sdcard on my computer
5. yes
6. when i select reboot to bootloader (from twrp menu) my phone just shutdown
and when i reboot to recovery (from phone) it takes time . . . reaallyy reaally long time (that's when i decided to force my phone to reboot)
Click to expand...
Click to collapse
3,4)check first if adb is working or not. If not, check your driver from device manager. ADB & usb mass storage mount should work.
6)When you pressed reboot to bootloader, did your phone was connected to PC? If not, pls check again with phone connected and see if it enters fastboot.
reboot to recovery options is not yet fixed, I think. Can you pls provide me the output of the command cat /proc/cmdline before and after you pressed reboot to recovery ?
XperiaMT27 said:
thnx for ur work
i will include it in my next update of omni and slimkat and provide feedback ..
Click to expand...
Click to collapse
Just a suggestion bro, Please add it as optional so that we (the users of Omni and Slimkat) can select whether to use it or stick to CWM....
NoobCoder said:
3,4)check first if adb is working or not. If not, check your driver from device manager. ADB & usb mass storage mount should work.
6)When you pressed reboot to bootloader, did your phone was connected to PC? If not, pls check again with phone connected and see if it enters fastboot.
reboot to recovery options is not yet fixed, I think. Can you pls provide me the output of the command cat /proc/cmdline before and after you pressed reboot to recovery ?
Click to expand...
Click to collapse
3 -4: ADB is working and also i have my driver installed. and what is this ADB sideload do??? about the USB mount same result
6. it works and enter to fastboot mode
reboot to recover:
Before
Code:
startup=0x1 warmboot=0x0 ta_info=9,4,256 androidboot.bootloader=s1 androidboot.serialno=BX9030XM7U cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end audit=1 semcandroidboot.babe1324=425839303330584d3755
after (after i pressed the reboot to recovery button and the phone is in "rebooting stage"
Code:
startup=0x1 warmboot=0x0 ta_info=9,4,256 androidboot.bootloader=s1 androidboot.serialno=BX9030XM7U cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end audit=1 semcandroidboot.babe1324=425839303330584d3755
pingu_c660 said:
3 -4: ADB is working and also i have my driver installed. and what is this ADB sideload do??? about the USB mount same result
6. it works and enter to fastboot mode
reboot to recover:
Before
Code:
startup=0x1 warmboot=0x0 ta_info=9,4,256 androidboot.bootloader=s1 androidboot.serialno=BX9030XM7U cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end audit=1 semcandroidboot.babe1324=425839303330584d3755
after (after i pressed the reboot to recovery button and the phone is in "rebooting stage"
Code:
startup=0x1 warmboot=0x0 ta_info=9,4,256 androidboot.bootloader=s1 androidboot.serialno=BX9030XM7U cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end audit=1 semcandroidboot.babe1324=425839303330584d3755
Click to expand...
Click to collapse
usb mount should have worked. Please boot into recovery again and mount the usb storage. Then give me the output of this command
cat /sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file
This doesn't seem right, both cmdline is same. If you can reboot to recovery with CWM, then flash the boot.img with CWM again and follow this
1) while your device is on, run cat /proc/cmdline and post it here.
2) now reboot to recovery from power menu or from other software (romtoolbox)
3) while in recovery, run again cat /proc/cmdline and post it here.
Just TNX !
Bro @NoobCoder, Your work is really excellent !
This is exactly what I need...I looked for this many times before but I didn't find any helpful post...but now you DID IT!
I love TWRP Recovery.
Again TNX for your work. I appreciate it.
guys any feedback on what's working or not ?
@NoobCoder, does ur kernel use fota kernel partition method for twrp?
i build twrp as default for omni and slimkat but cant enter recovery the way cwm does.
i think only fota method is working for our devices??
XperiaMT27 said:
@NoobCoder, does ur kernel use fota kernel partition method for twrp?
i build twrp as default for omni and slimkat but cant enter recovery the way cwm does.
i think only fota method is working for our devices??
Click to expand...
Click to collapse
no. I'll use fota partition after fixing the bugs. If your tried it can you tell me what's working?
Check http://forum.xda-developers.com/showpost.php?p=51138429&postcount=9 to provide log. Also recovery.log too.
ok.. will test tomorrow
I can't boot to system, why? anyone experiences a same problem too?
Is this working someone on 4.1?
Sent from my MT27i using XDA Premium 4 mobile app
ccxex29 said:
I can't boot to system, why? anyone experiences a same problem too?
Click to expand...
Click to collapse
works well for me, Carbon + Carbon kernel.
edit : attached pic
@NoobCoder bro, I really want to give it a try but my problem is that I am not able to setup ADB currently. :/
So can I use Terminal emulator or similar app to make a new boot.img?
Sent from my MT27i using XDA Premium 4 mobile app
cpkunki said:
@NoobCoder bro, I really want to give it a try but my problem is that I am not able to setup ADB currently. :/
So can I use Terminal emulator or similar app to make a new boot.img?
Sent from my MT27i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you can, but it'll be complicated. I think you should setup ADB, cause you have to check later if adb is working in recovery and also usb mass storage.
1) move binaries from image_tools to system/bin and chmod them to 755
2) move new_recovery.sh to /data/local and chmod to 755
3) move my initrd.gz and your boot.img to /data/local/tmp
4) now in terminal, cd to /data/local then type ./new_recovery.sh
your new boot.img will be in /data/local/tmp/boot folder named boot.img
NoobCoder said:
you can, but it'll be complicated. I think you should setup ADB, cause you have to check later if adb is working in recovery and also usb mass storage.
1) move binaries from image_tools to system/bin and chmod them to 755
2) move new_recovery.sh to /data/local and chmod to 755
3) move my initrd.gz and your boot.img to /data/local/tmp
4) now in terminal, cd to /data/local then type ./new_recovery.sh
your new boot.img will be in /data/local/tmp/boot folder named boot.img
Click to expand...
Click to collapse
Thanks for your super quick response bro!
I was trying the linux commands that you mentioned.in OP.
Yes I followed the steps correctly and got my boot.img successfully. Flashed it and finally got TWRP for my Sola!
Thanks to you!
My Feedback-Everything seems to be working perfectly except for 1 or 2 issues that I'm experiencing.
First is-
As soon as I enter the recovery, it keeps locking automatically and I have to keep unlocking it.
Secondly-
The touch sensitivity is quite high. Sola has got its floating touch working here.
It experiences touch even when hovered over the screen which is quiet uncomfortable.
Any more feedback or any logs you need, tell me.
Celebrating first anniversary of my beautiful Sola..

[RECOVERY][XP] TWRP 2.7.0.0 touch recovery [2014-03-21]

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Introduction:
Team Win Recovery Project 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.
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
Decryption of /data
Easy selection of internal/external storage
Portal Link: http://www.xda-developers.com/android/twrp-recovery-now-available-for-the-xperia-u-p-go-and-sola/​
Click to expand...
Click to collapse
Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I don't own XP. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
To ROM makers
if you include it in your ROM, please give proper credits cause I've spent almost a month trying to port this.Thanks.
Download
recovery_install_XP.zip - 6.43 MB
Source
TWRP source -> https://github.com/omnirom/android_bootable_recovery
Credits
all teamwin members, especially @Dees_Troy for giving me constant advice
@munjeni for his support and answering all my questions
@percy_g2 for providing gyroscope fix in touch
Changelog 21/03/2014
booted
full touch working
adb working
usb mass storage working
fixed show battery capacity & charging status (+ icon next to percentage)
reboot to bootloader/recovery working (from twrp menu)
reboot to bootloader/recovery working (from rom)
battery led to indicate battery status
brightness slider working (under settings=>screen in twrp)
F.A.Q
1) Are CWM backups compatible with TWRP ?
Ans: CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it.
edit: kernel not supported, stock rom, anyway thanks bro, good job!
miui
MIUI 5 (4.2.2) works +++
Confirmed working on SlimKat 4.4.2 by @DroidModderXtreme. Really good job man!
Sent from my Xperia P using XDA Premium 4 mobile app
kosmos-2011 said:
MIUI 5 (4.2.2) works +++
Click to expand...
Click to collapse
kopter36 said:
Confirmed working on SlimKat 4.4.2 by @DroidModderXtreme. Really good job man!
Sent from my Xperia P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Pls confirm if everything is working according to changelog. Thanks
Well, noob Coder Here's It
booted
full touch working
adb : I dont know how to check
usb mass storage: working super fine
battery percentage is showing... as it is showing in my phone 14%+(guess thatz it)
reboot to bootloader/recovery working (from twrp menu) = working well
reboot to bootloader/recovery working (from rom) =working
battery led to indicate battery status=working
brightness slider working well
Buddy, itz cool to see someone from my country helping here. Thnx for your effort.
MIUI 4.2.2
booted yes
full touch working yes
adb working ? yes
usb mass storage working ? yes
fixed show battery capacity & charging status (+ icon next to percentage) yes
reboot to bootloader/recovery working (from twrp menu) ? yes
reboot to bootloader/recovery working (from rom) ?
battery led to indicate battery status ? yes
brightness slider working (under settings=>screen in twrp) ? yes
Who can make zip for recovery for CM11?
Sent from my Xperia P using xda premium
Xperia_Fans said:
edit: kernel not supported, stock rom, anyway thanks bro, good job!
Click to expand...
Click to collapse
you're on locked BL ? If not, it should work. Did you try it?
kaziupal said:
Buddy, itz cool to see someone from my country helping here. Thnx for your effort.
Click to expand...
Click to collapse
anytime
after flashing this kernel root doesnt seem to be working on miui 4.2.2
work parfectly in stock rom based ( dark) with nemsis v6.3 as original karnel
i thinks that is better than cmw
thanks a lot
Using it on latest carbon but fix permission failed will provide logcat later
Sent from my Xperia P using Tapatalk
ibudanov said:
Who can make zip for recovery for CM11?
Sent from my Xperia P using xda premium
Click to expand...
Click to collapse
Not sure it's possible, since the boot.img is compiled a script that runs on the device.
I suppose it would be possible to do it by running the script on an XP with CM11 installed then using the compiled boot.img to create a flashable ZIP.
I'm going to try do this once I get to my computer.
Are you using Percy's CM11?
not working
i have an XP with the stock rom .100, the stock kernel and Unlocked Bootloader. I followed the instructions but it failed.
here's a screenshot of cmd and if you see something wrong in it tell me plz.
Thanks for your great work !!
big-A said:
i have an XP with the stock rom .100, the stock kernel and Unlocked Bootloader. I followed the instructions but it failed.
here's a screenshot of cmd and if you see something wrong in it tell me plz.
Thanks for your great work !!
Click to expand...
Click to collapse
check your folder, you must have a new file: "new_boot.img" and after fastboot it via flashtool
no
dastane said:
check your folder, you must have a new file: "new_boot.img" and after fastboot it via flashtool
Click to expand...
Click to collapse
there's no new_boot.img in the folder it's clear in the cmd screenshot that the process failed...
did you copied your curent karnel file in this folder and rename it into " boot.img" as its said in the OP??
djkk16 said:
after flashing this kernel root doesnt seem to be working on miui 4.2.2
Click to expand...
Click to collapse
+1
no root acces
now i'm using Liquid smooth based 4.4.2
the probleme is from the original karnel not from this recovry; waiting for karnel fix and i will re flash twrp

[RECOVERY][XU] CWM 6.0.4.8 Swipe Recovery [2014-05-21]

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Introduction
Hey guys, welcome to my new project. I've been working to port swipe gestured cwm recovery for the past week. It's working good now so I've thought of sharing it
How to Use
swipe up/down to change selection
swipe left to go back
swipe right to execute selected menu
For users having touch issue
Those who have touch problems can use the soft key button.
back button is UP
menu button is DOWN
home button is SELECT
for going back, you can use camera focus button
Installation:
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I only tested with AOSX. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
To ROM makers
if you include it in your ROM, please give proper credits.Thanks.
Download
recovery_install_20140521.zip - 6.36 MB
Changelog V1: 21/05/2014
working swipe recovery
adb working
usb mass storage working
custom background, menu text color
added vibration for soft key press
F.A.Q
If you encounter error like "cmdline out of range" in the terminal, then after executing run_me; type this in the terminal
Code:
adb shell
su
cd /data/local/tmp/boot/
kernel_make zImage initrd.gz cmdline boot.img
then copy the boot.img to your desktop and flash it.
works very well on paranoid android by Abhinav2
Good job! :good:
This CWM Recovery seems truly nice…
Thanks!
works on Sola too! wow...
boot to recovery - works
boot to system - works
swipe function - works
will try more and report it
anyone tested on cm11???
siddheshvartak said:
anyone tested on cm11???
Click to expand...
Click to collapse
it'll work on all 4.4 roms. Just try and report.
works very well in cm11 build 6.....
AGONTUK said:
F.A.Q
If you encounter error like "cmdline out of range" in the terminal, then after executing run_me; type this in the terminal
Code:
adb shell
su
cd /data/local/tmp/boot/
kernel_make zImage initrd.gz cmdline boot.img
then copy the boot.img to your desktop and flash it.
Click to expand...
Click to collapse
ok.. stupid question mayde.. i get the "cmdline out of range" error and after executing run_me I type the commands and finally I get tha message "target file boot.img is patched succesfully, enjoy new kernel" but where is this boot.img stored so I can grab it and flash it? I am searching my androd folders and can not locate it.. probably I have not understand it or what..?
EDIT: ok. the problem was that folders were not mounted as writable and were not visible.
anyway. thank you!
aggourodolmas said:
ok.. stupid question mayde.. i get the "cmdline out of range" error and after executing run_me I type the commands and finally I get tha message "target file boot.img is patched succesfully, enjoy new kernel" but where is this boot.img stored so I can grab it and flash it? I am searching my androd folders and can not locate it.. probably I have not understand it or what..?
Click to expand...
Click to collapse
It's in the /data/local/tmp/boot folder.
AGONTUK said:
It's in the /data/local/tmp/boot folder.
Click to expand...
Click to collapse
damn.. after and that it doesn't boot in recovery. I keep pressing volume up to enter recovery it loads for a second and then restarts just to boot normally.
aggourodolmas said:
damn.. after and that it doesn't boot in recovery. I keep pressing volume up to enter recovery it loads for a second and then restarts just to boot normally.
Click to expand...
Click to collapse
we use volume down to enter recovery !!!!
AGONTUK said:
we use volume down to enter recovery !!!!
Click to expand...
Click to collapse
not even with volume down works.
here is what I do. after extracting boot.img, I flash it via flashtool and fastboot mode and it gives me the "OK' sign. I power on device and on SONY logo I keep pressing volume down, enters for a second in recovery and restarts again to boot normally cause it can not enter recovery.
I think I am gonna give it up..
aggourodolmas said:
not even with volume down works.
here is what I do. after extracting boot.img, I flash it via flashtool and fastboot mode and it gives me the "OK' sign. I power on device and on SONY logo I keep pressing volume down, enters for a second in recovery and restarts again to boot normally cause it can not enter recovery.
I think I am gonna give it up..
Click to expand...
Click to collapse
After sony logo, led bar will light up with red, yellow, green light. Then it'll vibrate and pressing volume button will trigger recovery. If not, then you have done something wrong. Follow instruction properly, use command line not flashtool. Also this is mainly for kitkat roms, I don't know if it'll work properly on previous android versions.
can someone upload thee new recovery cuz i dunno how to do that adb thing im using experimental v12
thx!
wrong recovery
i flashed this recovery and i got twrp and now unable to go back to differnt recovery.
I tried to root my swipe elite plus but it ends with bricked.please help
arnab roy said:
I tried to root my swipe elite plus but it ends with bricked.please help
Click to expand...
Click to collapse
Did u even read the post bro? This is for xperia u, and the swipe in the name is for recovery with swipe gestures.

[Recovery][L3 II][Single/Dual] Custom Recoverys

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Unlocking Bootloader (Required)
* Because unlocking the bootloader? *
Bootloader bootloader is present on any Linux (Android) and Windows system.
Every manufacturer makes its locked bootloader to "not let any user device end his".
The LG , besides the bootloader lock, removes the command to unlock and still does not tell how to unlock the bootloader, then the only way is to burn an edited bootloader, that being the case.
Via App - thanks @ElDainosor and @vuminhduc_1998
Follow instructions in topic.
Support: All LG Optimus L3 II Variants
How to get into recovery via buttons:
Turn off your cell phone and do so, press the "Volume -" + "Power", after a second tight press "Home" and when vibrate loose and everyone quickly and repeatedly press the "Home". Will need a few tries until you get the delicacy, because that's the base.​
Next Update:
TWRP with support to sd-ext (by @Cobmaster)
TWRP 2.8.6.0 -> TWRP 2.8.7.0​
The CWMA and TWRP when I choose install zip from sdcard it displays the folder "/sdcard/0/" instead of "/sdcard/"
Sorry for my english I hope you understand what I mean xd
This is not bug
This folder is the default location, the CWMA you can change the location in recovery settings
thanks... It works on E425g????
now im trying to build something like that, im just learning so its hard even so i know about linux and building but it a little difernt...
Has not yet been tested, but I suppose that works.
It's hard but if you insist you can
TWRP works, but i cant install some packages like cyclone kernel, there is a problem in updater-script.
obrigado!!!
ensarman said:
TWRP works, but i cant install some packages like cyclone kernel, there is a problem in updater-script.
obrigado!!!
Click to expand...
Click to collapse
But you only tested the TWRP?
Test the CWM Advanced
Caio99BR said:
But you only tested the TWRP?
Test the CWM Advanced
Click to expand...
Click to collapse
lol, ok i will, but later, when i go home
Caio99BR said:
But you only tested the TWRP?
Test the CWM Advanced
Click to expand...
Click to collapse
olá
I have tested the CWM touch and it works perfectly until now I do not test everything buy it works well..
besides I have written a tutorial en spanish at my blog, if you want to check it: I will leave the link:
http://supranet.org/sistemas-operativos/twrp-y-cwm-touch-recovery-y-para-lg-optimus-l3-ii/
thanks
E430 Test
Caio99BR said:
Hello people, today I came to bring the main Recovery's ported and tested by me
TWRP - TeamWinRecoveryProject (by TeamWin) - Touch
CWM - ClockworkMod (by Koush) - Non-Touch
CWM Advanced Edition - 6 PhilZ Touch Recovery (by Phil3759) - Touch
Unlocking Bootloader (Required)
* Because unlocking the bootloader? *
Bootloader bootloader is present on any Linux (Android) and Windows system.
Scheme android bootloader.
{
"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"
}
Every manufacturer makes its locked bootloader to "not let any user device end his" meaningless thing to say.
The LG miserable, besides the bootloader lock, removes the command to unlock and still does not tell how to unlock the bootloader (already tried to communicate how to unlock), then the only way is to burn an edited bootloader, that being the case.
Unlocking the bootloader
Unzip emmc_appsboot.rar and place the file on the SD card
Code:
adb pull emmc_appsboot.bin /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5
Commands to install the CWM:
Put the file on the sdcard
Code:
adb push cwm.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Commands to install the TWRP:
Put the file on the sdcard
Code:
adb push twrp.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Commands to install CWM Advanced Edition:
Put the file on the sdcard
Code:
adb push cwma.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/cwma.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Note:
Tested only on E435 - Lg Optimus L3 Dual II
If someone on the other testing L3 II, leave feedback
How to get into recovery via buttons:
Turn off your cell phone and do so, press the "Volume -" + "Power", after a second tight press "Home" and when vibrate loose and everyone quickly and repeatedly press the "Home". Will need a few tries until you get the delicacy, because that's the base.
Downloads:
ADB - AndroidFileHost - (For PC)
Terminal Emulator - Play - (For Mobile)
Bootloader - AndroidFileHost - (Unlock the Bootloader)
TWRP (01/10/2014) - AndroidFileHost - (twrp.img)
CWM (10/01/2014) - AndroidFileHost - (cwm.img)
PhilZ CWM (01/10/2014) - AndroidFileHost- (cwma.img)
Credits:
IGGYVIP - For unlocked BootLoader :good:
hugo.gabriel999 - For Inspiration
TeamWin - For TWRP
Koush - For CWM
Phil3759 - For A Best And Advanced CWM
Click to expand...
Click to collapse
Hi, I tested PhilZ Touch and TWRP on LG E430 they work very well
Mikk123 said:
Hi, I tested PhilZ Touch and TWRP on LG E430 they work very well
Click to expand...
Click to collapse
Thanks!
Cayo what is the cwms???
ensarman said:
Cayo what is the cwms???
Click to expand...
Click to collapse
It is the CWM however you can use the touch to do the movements, it's good because you stop using the physical buttons.
Besides being easier.
Ok i will tr it, it works with the. New edify syntax like set metadata instead of set permission?
ensarman said:
Ok i will tr it, it works with the. New edify syntax like set metadata instead of set permission?
Click to expand...
Click to collapse
Yes, I have implemented SELinux support that adds support to new syntax.
All these recoverys made by me already have this support. There were already implemented in the second build, because in the first gave installation error (CM 11 test builds) due to lack of SELinux support.
Caio99BR said:
Yes, I have implemented SELinux support that adds support to new syntax.
All these recoverys made by me already have this support. There were already implemented in the second build, because in the first gave installation error (CM 11 test builds) due to lack of SELinux support.
Click to expand...
Click to collapse
great!!! thanks man
These recoverys are ready for CM11!
And who knows
I will delete the CWM and leave only the CWMS because it is better and simpler
Status
Updated CWM and CWM PhilZ Edition, now they are compatible with the CyanogenMod 11 (which will be released soon), for those who want to test will be necessary to update the recovery to the latest version.
I did not update the TWRP because it gave an error in which I could not solve.

[OFFICIAL][RECOVERY][SM-G313HZ]TWRP 3.0.X-0 For Samsung Galaxy V

​
Helloo.. what's up guys...
I'm so sorry. Long time no post.. hehe
Today i'm gonna share custom recovery (again) for Samsung Galaxy V SM-G313HZ aka vivalto3gnvdx. This custom recovery called TWRP 3.0.
Quoted from official website :
Screenshots :
{
"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"
}
What’s new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
Link : Since our device officially supported by teamwin, then all updates can be downloaded directly to the official website TWRP on the vivalto section here
Old build :
What’s new in 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
Link :
Odin version
Flashable version
Changelog :
Fix MTP
Thanks to Allah SWT
Credits :
Team win
Cleverior
corphish (for his clue to fix MTP)
And you...
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
PLEASE PUT THIS POST AS SOURCE. THANKS
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
doesntexits said:
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
Click to expand...
Click to collapse
Ok.. thanks for correction.
MTP is detected but can not mount. In adb, device is in recovery status. not in device status. is this same with you ?
screenshot of adb is attached.
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
doesntexits said:
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
Click to expand...
Click to collapse
There is no custom lun in my boardconfig. Maybe i can try to add it later. And the correct lun file location is in /sys/devices/virtual/android_usb/android0/f_mass_storage/lun .
I'm using TWRP source from omni source.
adb shell is working bro. Now your problem is MTP only.
doesntexits said:
adb shell is working bro. Now your problem is MTP only.
Click to expand...
Click to collapse
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
cleverior.ipul said:
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
Click to expand...
Click to collapse
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
doesntexits said:
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
Click to expand...
Click to collapse
Ya, even using custom lun but still not working.
Update with fix MTP
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
which version of firmware do u use ? have u try to install twrp using odin ?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
If you install TWRP from Odin, make sure you've choose .tar file as PDA, if not the recovery won't be installed
There's no way to install it through stock recovery, since it always gives "E: Signature verification failed".......
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Kazryu said:
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Click to expand...
Click to collapse
When install custom recovery using Odin, don't tick auto reboot. After install successfully, pull your battery out, seriously!
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
doesntexits said:
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
Click to expand...
Click to collapse
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
cleverior.ipul said:
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
Click to expand...
Click to collapse
It adds f2fs support for TWRP recovery, so we can flash other ROMs with f2fs partition support
I cannot use `adb shell`, can you use it?
---------- Post added at 14:33 ---------- Previous post was at 13:57 ----------
In TWRP 2, I remove all adbd control scripts in init.rc, just leave adbd service def, then in init.recovery.scx15.rc:
Code:
on init
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct D002
write /sys/class/android_usb/android0/functions [B]mtp,mass_storage,adb[/B]
# adb won't work in OSX without this
write /sys/class/android_usb/android0/bDeviceClass EF
write /sys/class/android_usb/android0/bDeviceSubClass 02
write /sys/class/android_usb/android0/bDeviceProtocol 01
[B] export PATH /sbin:/system/bin
export LD_LIBRARY_PATH .:/sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /external_sd
write /sys/class/android_usb/android0/enable 1
start adbd[/B]
So now I can use adb shell and MTP in TWRP 2.
Dude, on the TWRP Official Site I see it is in version 3.0.2-0, so it is safe to install that version and you will update this thread to the new version ?

Categories

Resources