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

[RECOVERY][XSOLA] TWRP 2.7.0.0 touch recovery [2014-04-27] - 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 (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..

Related

[RECOVERY][XGO] 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 (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

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

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.

FireTV 2 (sloane) Recovery [v6] - 3.0.0-5

It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
{
"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"
}
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Upgrade
You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you must use the Unbrick Image to unbrick.
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
This should prevent auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
This should fix the problems certain keyboard were having in recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
These are just changes related to the unbricking image. No other functional changes.
February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
This includes an updated script. You can now just run the zip instead of needing the zip and the script.
This includes TWRP 3.0.0-2.
Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
Fixed restoring backups.
This includes the same version of 2ndinit.
February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
This includes an automated script.
This has the same versions of 2ndinit and recovery as v1.
February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1

Awesome work!

Will try immediately! Thanks for posting this on weekend

Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks

deanr1977 said:
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
Click to expand...
Click to collapse
As long as you don't wipe data, updates remain blocked.

rbox said:
As long as you don't wipe data, updates remain blocked.
Click to expand...
Click to collapse
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?

deanr1977 said:
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
Click to expand...
Click to collapse
If you don't want to deal with adb, use the installer.

rbox said:
If you don't want to deal with adb, use the installer.
Click to expand...
Click to collapse
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance

deanr1977 said:
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
Click to expand...
Click to collapse
Installing recovery and roms does nothing to data.

rbox said:
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
Copy the contents of the zip to /sdcard on your FireTV.
Remount /system as read-write
Code:
mount -o remount,rw /system
Make the /system/recovery directory
Code:
mkdir /system/recovery
Copy 2ndinitstub
Code:
cp /sdcard/2ndinitstub /system/bin/ext4_resize
Copy 2ndinit
Code:
cp /sdcard/2ndinit /system/recovery/
Copy the recovery ramdisk
Code:
cp /sdcard/ramdisk-recovery.cpio /system/recovery/
Remount /system as read-only
Code:
mount -o remount,ro /system
Upgrade
You may repeat this to upgrade, but it is easier to just install a new pre-rooted rom. Every update for recovery I will make a new rom.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
Februrary 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Click to expand...
Click to collapse
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!

dk1keith said:
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
Click to expand...
Click to collapse
Yes adb shell. You can flash either version.

rbox said:
Yes adb shell. You can flash either version.
Click to expand...
Click to collapse
Awesome thanks rbox

Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.

aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.

dk1keith said:
Awesome thanks rbox
Click to expand...
Click to collapse
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied

aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
retyre said:
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
Click to expand...
Click to collapse
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
dk1keith said:
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
Click to expand...
Click to collapse
You need to be root...

rbox said:
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
You need to be root...
Click to expand...
Click to collapse
you mean by typing su?

dk1keith said:
you mean by typing su?
Click to expand...
Click to collapse
Yes, by typing su.

Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio

aboshi said:
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
Click to expand...
Click to collapse
Hrm... can you run
Code:
ls -l /system/bin/ext4_resize /system/recovery
also?

[ROM][Official] Kali NetHunter for the Huawei Nexus 6P LOS17.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I present to you: Kali NetHunter for the Huawei Nexus 6P LOS17.1
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
~ Prerequisites ~
- TWRP - https://drive.google.com/open?id=1axm3GVbTKypUdQAuYubNknJX4wKRFIec
- Stock components - vendor, radio, & bootloader img's from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image - https://androidfilehost.com/?w=files&flid=286833
- Magisk – https://forum.xda-developers.com/apps/magisk
~~ Downloads ~~
- NetHunter installer (find the latest release for Nexus 6P): https://www.kali.org/get-kali/#kali-mobile
- fstab with disabled forceencrpyt - https://www.androidfilehost.com/?fid=4349826312261764572
- vendor image with patched fw for nexmon - https://www.androidfilehost.com/?fid=8889791610682949885
EDIT: Use the following if there's no mirror on the link above: https://github.com/yesimxev/nethunter_files/raw/main/angler/vendor.squashfs.zip
- nexmon zip with nexutil and libs - https://www.androidfilehost.com/?fid=8889791610682951480
- Bootanimation TWRP flasher - https://www.androidfilehost.com/?fid=10763459528675571003
~~ How to Install ~~
- Assuming you have flashed stock radio, vendor, bootloader, TWRP, and Lineage 17.1 (using the steps from https://forum.xda-developers.com/ne...t/rom-lineageos-17-0-nexus-6p-angler-t4012099)
- Plug in to PC if you haven't done that yet
- Reboot into TWRP
- Format data
- Copy Magisk, NetHunter image, and fstab to USB-C drive or adb push to /sdcard
- Reboot into bootloader and flash vendor which was unzipped from zip
Code:
fastboot flash vendor vendor.squashfs
- Reboot into TWRP
- Copy fstab to /system_root/
Code:
adb push fstab.angler /sdcard/
adb shell "twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/fstab.angler /system_root/"
- Format data
- Reboot to system & do Android setup
- Reboot into TWRP
- Install Nexmon files through adb, from the zip above
Code:
twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/libnexmonkali.so /system_root/system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system_root/system/lib64/ && cp /sdcard/nexutil /system_root/system/xbin/ && chmod a+x /system_root/system/xbin/nexutil
- Flash NetHunter image
- Flash Magisk
- Reboot
- Run NetHunter app, update from NH Store
- Reboot
~~~ Notes & Updates ~~~
Nexmon is finally working with injection in Kali Chroot , although EAPOL data is still not (or malformed) in the captures.
- copy Nexmon libs over to /system/lib64/ from the nexmon.zip (not in TWRP):
Code:
adb push libnexmon* /sdcard/ && adb push nexutil /sdcard/
- and copy using androidsu terminal:
Code:
mount -o rw,remount / && cp /sdcard/libnexmonkali.so /system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system/lib64/ && cp /sdcard/nexutil /system/xbin/ && chmod a+x /system/xbin/nexutil
For devices which have no space left on system: you need to copy those files before flashing NetHunter. I didn't have this problem, maybe due to GApps pico. Then use the following commands in TWRP:
Code:
twrp mount /system_root && twrp remountrw /system_root && cp /sdcard/libnexmonkali.so /system_root/system/lib64/kalilibnexmon.so && cp /sdcard/libnexmon.so /system_root/system/lib64/ && cp /sdcard/nexutil /system_root/system/xbin/ && chmod a+x /system_root/system/xbin/nexutil
Thanks @JaK3sT for discovering this!
You have to make sure that wifi is on but you're not connected to an AP.
Enable in AndroidSU terminal, I created a custom command with
Code:
nexutil -m2
Export LD_PRELOAD for faking ioctl in every Kali Chroot terminal window you open
Code:
export LD_PRELOAD=/system/lib64/kalilibnexmon.so
Hijacker is not fully supported as I've built one with aarch64 tools, but it randomly stops airodump although it's working. Will give it a shot in the future.
- Mana is being replaced, for the time being you can downgrade iptables in chroot with the following :
Code:
wget http://old.kali.org/kali/pool/main/i/iptables/iptables_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libip4tc0_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libip6tc0_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libiptc0_1.6.2-1.1_arm64.deb
wget http://old.kali.org/kali/pool/main/i/iptables/libxtables12_1.6.2-1.1_arm64.deb
dpkg -i *.deb
apt-mark hold iptables
apt-mark hold libip4tc0
apt-mark hold libip6tc0
apt-mark hold libiptc0
apt-mark hold libxtables12
Credits: The Offensive Security Team and the NetHunter community, huge thanks to Re4son & kimocoder for patching the wlan1 insert reboot issue! Long time mystery.
Another extremely big thanks for @draco42 for patching libnexmon and kalilibnexmon!
Android Version: 10.0
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the Huawei Nexus 6P
Contributors
@Re4son, @kimocoder, @yesimxev, @draco42
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/Re4son/android_kernel_huawei_angler

**RESERVED**

Omg ...?????

**RESERVED**

Thank you!
Before your post went up, I had been trying for DAYS to install Nethunter on PE10.
Everytime I lost root (Magisk) on reboot and the Nethunter app never showed up.
I KNEW I was missing some important steps (which were not documented).
Now that official instructions are available I'm going to try and install it the proper way.

@Re4son @kimocoder
@yesimxev
Wow, you guys are on fire.
Congratulations to this great updates and foremost the long outstanding release for the Angler!
Which under Oreo flawlessly works now.
No nasty reboots while attempting to set your nic into monitor mode for sure. :good:
Kimocoder did an amazing job with the port of the new driver.
I could basically use every adapter. Especially the ac ones.
You accidentally mixed up some of the links.
This is the Angler (Huawei Nexus 6P) sub-forum and you posted a link for the installer to the Shamu (Motorola Nexus 6).
Also did I try to look over the source and compiled it for myself, but after everything was set up, my kernel and chroot & everything else, the usb adapter plug in/out bug occurred again.
Re4son worked on flair's source 16days ago.
Where can I find the one you used in the new release?
Here is the link to the correct one - >
https://build.nethunter.com/contrib...er-2020.2-pre3-angler-los-ten-kalifs-full.zip
For the user who aren't comfortable to use Android ten for other reasons, here the recommended stable release for Android Oreo stock - >
https://build.nethunter.com/contrib...unter-2020.2-pre3-angler-oreo-kalifs-full.zip
I had no time the last week(s), but I did see a couple of issues who need to be addressed.
One of the main problems with the new Oreo kernel neither Nexmon or the new QUALCOMM patch from kimocoder and Co. are working.
I will come back to this when I have the time..
Firstly great work to the entire team and big thanks for this great contribution

wow:laugh:awosome!

Could you explain to less experienced user how someone are going to be modify the last twrp version for the Angler wit fstab accordingly?

Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
Code:
mount -o rw,remount /vendor
cp /sdcard/fstab.angler /vendor/etc/

yesimxev said:
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
Click to expand...
Click to collapse
Thanks a bunch, @yesimxev!
As you saw in both threads for LOS 17 and PE, do they come with specific TWRP versions.*
Are they some what of relevant, or is the official release by twrp.me sufficient?
*LOS 17.1
https://forum.xda-developers.com/showpost.php?p=81059545&postcount=3
*Pixel Experience 10.0
https://forum.xda-developers.com/showpost.php?p=80290619&postcount=3

Thanks for this it works perfect but my Question is how to survive a System update?
For example a new Version of los 17 Comes out, i Flash it, so the nethunter kernel is gone.
When i Flash the whole nethunter Image then all works fine but the chroot Environment will be wiped and replaced with the one from the Image. Thats not so good because all of the Manual Things are wiped also, like compiled Software and post updated and installed Software.
So whats the best way to Keep the chroot Environment after an Android System update?

Create a backup of your rootfs via the Chroot Manager is probably the best option. You could just reflash the kernel too

Thanks for your fast reply.
How to Flash the kernel only? I looked into the Archive but there are too many scripts for all the Little nice Things during the installation and there isnt a single zip file for the kernel or i missed something. Sorry i m not that great developer…
I thought i could comment out the chroot extraction in the installer script, its the last step. Is this a possibility?
---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------
And the possibility to backup the chroot in the chroot Manager i never saw, thats great and probably the best Option yes. Thanks for that hint!

yesimxev said:
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
Code:
mount -o rw,remount /vendor
cp /sdcard/fstab.angler /vendor/etc/
Click to expand...
Click to collapse
When I tried copy fstab.anger from my /usb_otg to /vendor/etc/ via file manager in TWRP, a received error ERROR status code 1.
So I tried mount command, which is mentioned above, via terminal in TWRP. /vendor was mounted succesfully but when I used cp command a received error again, that target is in read-only filesystem. And yes I definitely mount it with "-o rw" (read write).
What can I do wrong?

SalyczeQ said:
When I tried copy fstab.anger from my /usb_otg to /vendor/etc/ via file manager in TWRP, a received error ERROR status code 1.
So I tried mount command, which is mentioned above, via terminal in TWRP. /vendor was mounted succesfully but when I used cp command a received error again, that target is in read-only filesystem. And yes I definitely mount it with "-o rw" (read write).
What can I do wrong?
Click to expand...
Click to collapse
Forgot to mention that vendor has to be mounted first. Use
Code:
mount /vendor

Nick_Speed said:
How to Flash the kernel only? I looked into the Archive but there are too many scripts for all the Little nice Things during the installation and there isnt a single zip file for the kernel or i missed something. Sorry i m not that great developer…
Click to expand...
Click to collapse
Probably because they were just released and for now as complete installer by Offensive being offered. ;/
I build both of the newly released kernel for LOS 17.1 and 8.1 Stock Oreo with the python installer.
Ten
https://mega.nz/file/hUBHxSyT#HJRVnp_uH1hosPfsDClSiG9hzO54eQkM24ONG48b3Fc
Oreo
https://mega.nz/file/AVZxFIDC#SQG_X6yfmwb3cjmO8bzYqo5RhTJ7hjmWEOrk-c97f2o
Best regards
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
SalyczeQ said:
Thanks for mentioning the link, replaced with the correct one. To do fstab:
Copy fstab to eg. Internal storage
Boot into TWRP
In terminal, type
When I tried copy fstab.anger from my /usb_otg to /vendor/etc/ via file manager in TWRP, a received error ERROR status code 1.
So I tried mount command, which is mentioned above, via terminal in TWRP. /vendor was mounted succesfully but when I used cp command a received error again, that target is in read-only filesystem. And yes I definitely mount it with "-o rw" (read write).
What can I do wrong?
Click to expand...
Click to collapse
Did you use the official version, or the ones supported by the the according rom developer?

yesimxev said:
Forgot to mention that vendor has to be mounted first. Use
Code:
mount /vendor
Click to expand...
Click to collapse
View attachment 4996285
as you can see I tried, but the same error still occurs

UsPdSr said:
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
[/COLOR]
Did you use the official version or the ones supported by the according to rom developer?
Click to expand...
Click to collapse
I used TWRP provided beside according rom, not the official version. View attachment 4996289
But If you will check the screenshot which I attached, I notice something weird, that in mount TWRP page I see vendor partition twice. Can It be a problem?
Is there any big difference between TWRP provided for LOS17.1 and PE10? Because the last thing I can think of is that I may swap it and use PE10 TWRP for install LOS17.1 rom.

SalyczeQ said:
I used TWRP provided beside according rom, not the official version.
But If you will check the screenshot which I attached, I notice something weird, that in mount TWRP page I see vendor partition twice. Can It be a problem?
Is there any big difference between TWRP provided for LOS17.1 and PE10? Because the last thing I can think of is that I may swap it and use PE10 TWRP for install LOS17.1 rom.
Click to expand...
Click to collapse
I tried the installation with LOS.
I had countless error messages primarily because of the vendor, too.
I have seen this weird entry before, after another user botched his installation as well.
I would definitely erase the recovery with fastboot, or try to flash the official one over.
Since the Nexus 6p received support for Pie am I very sceptical of the usage as daily driver.
I have no desire to flash these funny FBEwhatever recoveries and and see my device commit suicide. - _-
So.
I am definitely going to try it again, especially Pixel Experience is interesting, but I would like to ask the Nethunter team ( @yesimxev, @Re4son), if it would be possible to write a more detailed instructions on how to get this work, or perhaps assemble something to flash without modification by the user..
Many heaps

UsPdSr said:
I tried the installation with LOS.
I had countless error messages primarily because of the vendor, too.
I have seen this weird entry before, after another user botched his installation as well.
I would definitely erase the recovery with fastboot, or try to flash the official one over.
Since the Nexus 6p received support for Pie am I very sceptical of the usage as daily driver.
I have no desire to flash these funny FBEwhatever recoveries amd and see me device commit suicide.
So.
I am definitely going to try it again, especially Pixel Experience is interesting, but I would like to ask the Nethunter team ( @yesimxev, @Re4son), if it would be possible to write a more detailed instructions on how to get this work, or perhaps assemble something to flash without modification by the user..
Many heaps
Click to expand...
Click to collapse
Hey there,
So for ten i installed ExtendedUI OFFICIAL and PixelDust with the twrp fbe 10, reboot to recovery, rooted with magisk, set all up, install busybox within magisk, reboot to recovery, then installed the nethunter zip, rebooted to recovery,
rooted with magisk, reboot to System.
All is fine, the kernel etc. but no nethunter apps are showing. So i extracted the apps from the zip file, installed all and updated the nethunter app throught fdroid because the nethunter store app isnt working with extensions but fdroid did and the source for the nethunter repo you can copy from the store app.
Then fire up the nethunter up, set up chroot and tata, all is working great.
and btw thanks for the flashable kernel ;o)

Better Mobile App

welcome