Database Develop

Unofficial TWRP Mako 3.0.2.0 EXT4/F2FS/NTFS

Unofficial TWRP Touch Recovery for Google Nexus 4 codename MAKO with ext4 f2fs and NTFS support
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Screenshots:
Flashing Instructions:
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go in fastboot mode (hold down Power + Vol down for a ew seconds.
2. Open terminal window/command prompt to execute following commands
Code:
fastboot flash recovery TWRP_Mako-3.0.0-ext4-f2fs.img
3. With volume up and down select recovery mode e click power
4. Enjoy you reboot in TWRP 3.0.0
Download Links:
TWRP-3.0.2.0
XDA:DevDB Information
Unofficial TWRP Mako 3.0.2.0 EXT4/F2FS/NTFS, Tool/Utility for the Google Nexus 4
Contributors
vocoderism, Dees_Troy
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2016-04-08
Created 2016-02-06
Last Updated 2016-04-08

Thank you!

great job!
usb otg with "magic" zip works nice

It'd be nice to have native USB-OTG support without replacing the kernel. While mounting, backup to, restore from and install from all work as expected, I'm unsure of how installing ROM's (LP and MM ROM's specifically) using this method might be affected.

[/COLOR]
dimaka1256 said:
great job!
usb otg with "magic" zip works nice
Click to expand...
Click to collapse
What is the "magic" zip? A kernel to support usb OTG? Does it still need a external power source?

I'm assuming he's referring to the zip file contained in the following thread...
http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689
And yes, it needs to be a powered OTG cable, either a premade y-cable or as I did, bought a cheap normal OTG cable and splice an old 5v charger into it.

bfoos said:
I'm assuming he's referring to the zip file contained in the following thread...
http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689
And yes, it needs to be a powered OTG cable, either a premade y-cable or as I did, bought a cheap normal OTG cable and splice an old 5v charger into it.
Click to expand...
Click to collapse
yes, you're right in both cases
backupping and restoring to usb work ok, both with twrp2831 and this one and kernel replacing
installing 5.1.1 rom works ok with 2831 and kernel replacing
seems like M should also have no problems
external power will be needed until some crazy man dismantles the board and solders 5v bus power
ps congrats on becoming senior!

well, i've got a first problem
"magic" zip contains franco's 191 kernel which doesn't support f2fs so f2fs partitions are unaccessible by a recovery modded this way
i've tried to find the solution by exxtracting boot.img from quanta kernel but (my bad) i don't remember how to compile boot.img from zImage or extract it froom working device
upd: will try flashify or some other app to backup a boot.img from working device

i've done it!
concluding previous post
I tried to convert my /data and /cache to f2fs and keep usb-otg functionality in recovery
i applied the zip from here http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689 and lost my f2fs partitions (the kernel contained there is franco's r191 and doesn't support f2fs
as a daily driver for my phone i use quanta #10 kernel http://forum.xda-developers.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561 that works with stickmount nicely
So my job was:
-extracting boot.img from alive system with quanta kernel (done with flashify)
-replace boot.img in "magic" zip with acquired in previous step
so i got usbotg-replace-recovery-kernel-q10.zip
additionally, quanta kernel does not allow USB OTG by default - we should enable it in companion app or by terminal command
Code:
echo "1" > /sys/module/msm_otg/parameters/otg_hack_enable
So i created another zip that does one job - makes it
so, howto:
1. flash twrp recovery provided in OP post
2. flash usbotg-replace-recovery-kernel-q10.zip once
3. flash usbotg-q10_enable.zip EVERY TIME you boot the recovery to use USB OTG in it
disclaimer:
i'm not responsable for any consequences with your devices, at least I've flashed factory image for several times until i realised the problem - it helps
maybe i've violated some copyrights sorry and feel free to contact me
the job done is quick and dirty - i'll be glad to see, if someone makes my ideas better
yes, and it works for me
Credits:
@zaclimon for creating marvellous kernel
@zman0900 for most of work on "magic" zip
@ziddey for messing with USB OTG stuff
@vocoderism for messing with this recovery
upd: installing MM omniROM 6.0.1 20160207 succeeded with all this stuff

For info only.
My Nexus 4 running Chroma ROM February revision (based on 6.0.1 MMB29Q) appeared to work ok with TWRP 3.0, but refused to back up because it saw zero space available. It also didn't keep settings between boots. I restored 2.8.7.0 and this works fine - it sees over 10GB free, performs the backup, and retains settings.
Occasional random reboots make me think that perhaps I have a hardware problem, so maybe it's just my N4?

dimaka1256 said:
i've done it!
concluding previous post
I tried to convert my /data and /cache to f2fs and keep usb-otg functionality in recovery
i applied the zip from here http://forum.xda-developers.com/nexus-4/development/recovery-mod-twrp-2-6-3-0-externally-t2412689 and lost my f2fs partitions (the kernel contained there is franco's r191 and doesn't support f2fs
as a daily driver for my phone i use quanta #10 kernel http://forum.xda-developers.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561 that works with stickmount nicely
So my job was:
-extracting boot.img from alive system with quanta kernel (done with flashify)
-replace boot.img in "magic" zip with acquired in previous step
so i got usbotg-replace-recovery-kernel-q10.zip
additionally, quanta kernel does not allow USB OTG by default - we should enable it in companion app or by terminal command
Code:
echo "1" > /sys/module/msm_otg/parameters/otg_hack_enable
So i created another zip that does one job - makes it
so, howto:
1. flash twrp recovery provided in OP post
2. flash usbotg-replace-recovery-kernel-q10.zip once
3. flash usbotg-q10_enable.zip EVERY TIME you boot the recovery to use USB OTG in it
disclaimer:
i'm not responsable for any consequences with your devices, at least I've flashed factory image for several times until i realised the problem - it helps
maybe i've violated some copyrights sorry and feel free to contact me
the job done is quick and dirty - i'll be glad to see, if someone makes my ideas better
yes, and it works for me
Credits:
@zaclimon for creating marvellous kernel
@zman0900 for most of work on "magic" zip
@ziddey for messing with USB OTG stuff
@vocoderism for messing with this recovery
upd: installing MM omniROM 6.0.1 20160207 succeeded with all this stuff
Click to expand...
Click to collapse
Awesome! I was doing this exact thing last night but had to go to bed. All I was missing was the terminal command. Here's a little tip though, use Android Image Kitchen to unpack and repack your boot.img. This will gzip the image and vastly reduce its size. And yup installing MM roms works just fine.

Awesome work! Thanks

Since TWRP will obviously happily boot and function to varying degrees with just about any old kernel, I think this merits more testing. Since Quanta is an AnyKernel, it just modifies the RAM Disk of whatever base kernel you install it on. Perhaps there exists a full kernel that has OTG hard coded and enabled, thus negating the need for using a script to enable it every time. F2FS isn't really that important to me, but it is obviously for others. I think I'm going to play around with some LP/MM kernels and see what I can come up with. I'll happily share my findings with you fine folks.

bfoos said:
Since TWRP will obviously happily boot and function to varying degrees with just about any old kernel, I think this merits more testing. Since Quanta is an AnyKernel, it just modifies the RAM Disk of whatever base kernel you install it on. Perhaps there exists a full kernel that has OTG hard coded and enabled, thus negating the need for using a script to enable it every time. F2FS isn't really that important to me, but it is obviously for others. I think I'm going to play around with some LP/MM kernels and see what I can come up with. I'll happily share my findings with you fine folks.
Click to expand...
Click to collapse
Why don't you guys simply don't change TWRP's init script to add an entry to enable the OTG switch at boot? I'm pretty sure it can be done without any additional external script because it was self-compiled beforehand.

Hah, I was just about to unpack the 3.0.0-0 image and poke around.

bfoos said:
Hah, I was just about to unpack the 3.0.0-0 image and poke around.
Click to expand...
Click to collapse
Lool true there is still this option. You could do something like:
write /sys/module/msm_otg/parameters/otg_hack_enable 1
inside the init.rc of the recovery.

Yeah, I was gonna go that route, but instead I just copied the enable.sh script from @dimaka1256's zip file, dumped it in sbin and called it as a service from within init.rc. Repacked the image and flashed it... SUCCESS!!! USB-OTG enabled on boot!
***EDIT***
Here's some technical information (including the steps used to create it) about the attached zip file.
I first flashed the boot.img contained in the latest PureNexus release, then Quanta v10. Rebooted into system and used flashify to do a kernel backup. I then replaced the ziddey-boot.img image in the "magic" zip file referenced earlier in this thread, rebooted into recovery and flashed it. Rebooted recovery and flashed @dimaka1256's usbotg-q10_enable.zip and tested to see if OTG and F2FS were working... SUCCESS!!! I then rebooted back into system and used flashify to do a recovery backup. I unpacked the image with Android Image Kitchen, took the enable.sh from usbotg-q10_enable.zip and dumped it into the ramdisk's sbin directory and edited the init.rc file to call the enable script as a service. Repacked the image and flashed it, tested OTG and F2FS once more and it passed. Zipped the image as it was just over the 8MB attachment limit for .img files here. So, extract and flash away and enjoy something we should have natively... OTG!!!

bfoos said:
Yeah, I was gonna go that route, but instead I just copied the enable.sh script from @dimaka1256's zip file, dumped it in sbin and called it as a service from within init.rc. Repacked the image and flashed it... SUCCESS!!! USB-OTG enabled on boot!
Click to expand...
Click to collapse
seriously you can remove most of lines of the script that are related to checking board name (no need to it, since recovery is ok and launched) and leave just setting permissions and echo'ing the parameter
nice work!

Yup, a little teamwork by some like-minded individuals and we now have in my opinion, the best of everything TWRP has to offer our beloved N4's. 3.0.0-0, OTG, F2FS, etc.

Amazing, big up for the port. I was thinking that we will have official support, but as this thread has shown up, I realised that we'll not.
A dumb question: is this recovery capable of restoring backups made by twrp-2.8.7.0 ?

Kali NetHunter-hammerhead

I have recently had a few people asking me to post my NetHunter package but as I build from others sources I will instead direct you to the original thread by member jcadduono HERE
The link to the nightly NetHunter installer- https://idlekernel.com/nethunter/nightly/
Choose the package for the ROM you are using, I have installed and can confirm the hammerheadcm-marshmallow.zip package to be working on ResurrectionRemix it should work for most CM based ROMs.
If you are using factory 6.0.1 then you would use the hammerhead-marshmallow.zip file.
I have not had a problem dirty flashing the zip over my current ROM however this is the suggested method of installing.
BEFORE INSTALLING
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist in CyanogenMod by itself.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
If you are already rooted or know you have systemless SuperSU installed, you will need to go into the SuperSU app and do a full unroot then reflash CyanogenMod (for the unmodified boot partition) and Gapps. The NetHunter installer does not play well with systemless SuperSU at this time.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
FULL FRESH INSTALL STEPS
Flash CyanogenMod/SlimRom/ResurrectionRemix installer zip
Flash Gapps if you want them (preferably OpenGapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Kali NetHunter installer zip from this thread
Boot into device
Open the NetHunter app
Use the Kali Chroot Manager to install Kali on your phone
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
Upgrading from NetHunter 2.0 is not recommended, and may break the NetHunter app in some cases.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the ~60 MB update-nethunter-* zip again.
KNOWN ISSUES
F2FS - You need to have an ext4 data partition. I'm not sure why, but having a Kali chroot on your data partition totally breaks booting f2fs /data.
There is currently no fstab modifications in NetHunter, but I do plan on making a zip to automatically modify the fstab for f2fs later.
USB Keyboard - The keyboard is unusable on some devices (ex. the Note 3) due to a depth bug that causes your key presses to go right through the keyboard into the swipe pad.
Terminal App - Full screen programs like nano or vi are unusable because they can't be rendered properly. Learn sed for text file editing. Just kidding that's cruel.
Install OpenSSH server in Kali and use the JuiceSSH app as an alternative to NetHunter Terminal. (it's wayyyy better sorry jmingov)
DEVELOPMENT
jcadduono's branch of the installer development is here: https://github.com/jcadduono/kali-nethunter
The original branch of development is located here: https://github.com/offensive-security/kali-nethunter
The NetHunter team has been doing a really great job bringing Kali to Android.

Do NOT install SuperSU 2.67 systemless! for some reason it causes random reboots. Updating to 2.65 through the Play Store is fine.

Does it work on Hammerhead CAF?

This is a very cool project and definitely worth checking out. Thanks for the info. [emoji106]
Sent from my Nexus 5 using Tapatalk

ASHURiCAN said:
Does it work on Hammerhead CAF?
Click to expand...
Click to collapse
i don't think it works on CAF. i haven't tried it as i don't use CAF builds.

Dumb question

ASHURiCAN said:
Does it work on Hammerhead CAF?
Click to expand...
Click to collapse
No, it's not working with CM13 CAF

HighRidas said:
DEVELOPMENT
jcadduono's branch of the installer development is here: https://github.com/jcadduono/kali-nethunter
The original branch of development is located here: https://github.com/offensive-security/kali-nethunter
The NetHunter team has been doing a really great job bringing Kali to Android.
Click to expand...
Click to collapse
Hi, can u help me to request hammerheadcaf support please?
Can i multirom a caf based with a noncaf rom? thanks afterwards

[Kernel][Exynos][BROKEN] Kali NetHunter for the Galaxy S7 Edge

OKAY SO
Currently, I am unable to get even stock kernel sources to boot. I'm not sure what to do to at this point. Waiting on someone else that actually has the device to get this figured out - DO NOT FLASH!
WARNING: This is completely untested, highly theoretical, and possibly dangerous. Flash at your own risk.
Back up your original boot image in TWRP before attempting to flash this! If it doesn't boot, you can simply restore your previous boot image.
This is Kali NetHunter 3.0.5 for the Galaxy S7 Edge.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The updater zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
DOWNLOAD
Current version: 3.0.5 (beta, 2016-03-11)
Please be careful to download the right version based on this table:
SM-G935F, SM-G935FD, SM-G935X, SM-G935W8: hero2lte
SM-G930F, SM-G930FD, SM-G930X, SM-G930W8: See proper forum.
All others be sad.
Download is available at: https://idlekernel.com/nethunter/hero2lte/
Grab the 700 MB+ zip.
Kernel-only zip is for upgrading your kernel, or just using the NetHunter kernel by itself. (yes, you can do that!)
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
Flash this zip in TWRP to allow system modifications and unencrypted data: https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
Once that is flashed, go to the wipe page and use the [Format Data] button.
This will wipe all your data, including internal storage!
Boot up your system and set up Android.
Now you can go back into TWRP and flash Kali NetHunter.
Currently, Samsung encryption is not supported by TWRP, so we have to disable it.
Sorry security freaks! There's a lot of irony here, isn't there?
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU (2.68) in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
Also included is an extra Busybox that gives you full large file support and some extra applets.
FULL FRESH INSTALL STEPS
Install Team Win Recovery Project to your recovery partition.
{
"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"
}
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
Download Kali NetHunter.
Without exiting TWRP, transfer the NetHunter installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the ~60 MB update-nethunter-* zip again.
THE KERNEL
The NetHunter kernel for the Galaxy S7 Edge is based on Samsung's OSRC G935FXXU1APAW kernel sources.
It has the following changes:
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted system, data, and cache partition support
UKSM Ultra Kernel Same-page Merging KSM support
Updated and enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
Simple IO (SIO) scheduler as default IO scheduler
USB HID Gadget keyboard support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption changed from forced to optional (disabled during installation)
Disables dm-verity and allows you to boot modified system partitions
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (it better not be something other than G935F, dangit!)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
NetHunter Terminal - It doesn't automatically set the columns/rows, so you need to type "resize" sometimes to fix the display.
DEVELOPMENT
You can see my branch of the installer development here: https://github.com/jcadduono/kali-nethunter
Alternatively, the main branch is also available on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Kernel source: https://github.com/jcadduono/nethunter_kernel_herolte
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7 Edge, Kernel for the Samsung Galaxy S7 Edge
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 3.0.5
Beta Release Date: 2016-03-11
Created 2016-03-11
Last Updated 2016-04-15

great, thanks for the first kernel any way to add synapse support?

Waiting eagerly to see people's results before I take a leap!
Sent from my SM-G900F using XDA Free mobile app

riso123 said:
Waiting eagerly to see people's results before I take a leap!
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Me too

Cowards!
Ahem, anyone tried this yet?
Sent from my SM-G935F using Tapatalk

Beefheart said:
Cowards!
Ahem, anyone tried this yet?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Haha, not sure everyone will get that British humour lol
Sent from my SM-G900F using XDA Free mobile app

Beefheart said:
Cowards!
Ahem, anyone tried this yet?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Someone tried the G930F version for me earlier. They said it worked but they had random reboots once in a while.
I'm hoping someone will show up and know how to grab /proc/last_kmsg or something.

jcadduono said:
Someone tried the G930F version for me earlier. They said it worked but they had random reboots once in a while.
I'm hoping someone will show up and know how to grab /proc/last_kmsg or something.
Click to expand...
Click to collapse
Any idea why the guy in the TWRP thread can't see any partitions from recovery?

Beefheart said:
Any idea why the guy in the TWRP thread can't see any partitions from recovery?
Click to expand...
Click to collapse
he needs to visit http://www.zennioptical.com/

jcadduono said:
he needs to visit http://www.zennioptical.com/
Click to expand...
Click to collapse
In this country it would be SpecSavers.
He's not posted since so hopefully he's fixed it and has managed to root.

i have radom reboot. hope it will work tomorrow.

Thiramisu said:
i have radom reboot. hope it will work tomorrow.
Click to expand...
Click to collapse
Just the one random reboot?
Ate you able to mount your partitions?
Sent from my SM-G900F using XDA Free mobile app

Thiramisu said:
i have random reboot. hope it will work tomorrow.
Click to expand...
Click to collapse
i got "failed to install from external sd fault :1"......someone can help me?
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
riso123 said:
Just the one random reboot?
Ate you able to mount your partitions? YES
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
But bootloop now

Thiramisu said:
i got "failed to install from external sd fault :1"......someone can help me?
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
But bootloop now
Click to expand...
Click to collapse
Are you flashing from twrp posted on the other thread? Another guy has said he can't mount pairings which makes me think this is a similar issue, however you appear to actually be able to flash the file, which means either your partitions have mounted or you are not using twrp?
However the error your getting sounds like mount issues after the kernel flash.
Sent from my SM-G900F using XDA Free mobile app

riso123 said:
Are you flashing from twrp posted on the other thread? Another guy has said he can't mount pairings which makes me think this is a similar issue, however you appear to actually be able to flash the file, which means either your partitions have mounted or you are not using twrp?
However the error your getting sounds like mount issues after the kernel flash.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
i flashed the TWRP, and my Phone boot correctly. after i tray to flash update-nethunter-hero2lte-marshmallow-kalifs-full-rolling-3.0.5-20160311-1404.zip my phone have bootloops. i format data before i flash.

Thiramisu said:
i flashed the TWRP, and my Phone boot correctly. after i tray to flash update-nethunter-hero2lte-marshmallow-kalifs-full-rolling-3.0.5-20160311-1404.zip my phone have bootloops. i format data before i flash.
Click to expand...
Click to collapse
Sounds like you followed the instructing correctly, however, could you bout to twrp and see if you can browse both your internal and external partitions. I still feels like a mount issue which is likely the recovery more than kernel.
Add you where able to boot after flashing recovery, are you able to now boot with the sd card removed?
Sent from my SM-G900F using XDA Free mobile app

riso123 said:
Sounds like you followed the instructing correctly, however, could you bout to twrp and see if you can browse both your internal and external partitions. I still feels like a mount issue which is likely the recovery more than kernel.
Add you where able to boot after flashing recovery, are you able to now boot with the sd card removed? Yes i am able to boot and see the SD Card, its not removed!
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
I try to install again update-nethunter-hero2lte-marshmallow-kalifs-full-rolling-3.0.5-20160311-1404.zip I get the Answer: Failed to install
Updater progress ended with Error: 1
i am able to see internal and external partitions
Error: Your data partitions appears to be empty

Thiramisu said:
I try to install again update-nethunter-hero2lte-marshmallow-kalifs-full-rolling-3.0.5-20160311-1404.zip I get the Answer: Failed to install
Updater progress ended with Error: 1
i am able to see internal and external partitions
Click to expand...
Click to collapse
the only useful info you can provide is recovery.log, after trying to flash, go to advanced -> copy log to sdcard, then copy it off mtp storage and post it here

jcadduono said:
the only useful info you can provide is recovery.log, after trying to flash, go to advanced -> copy log to sdcard, then copy it off mtp storage and post it here
Click to expand...
Click to collapse
Full Text of copy log is to long to paste here in. How can i upload, please?

Thiramisu said:
Full Text of copy log is to long to paste here in. How can i upload, please?
Click to expand...
Click to collapse
Paste the text in a .txt file and upload it

TWRP 3.2.0.0 Moto Z2 force [Nash]

{
"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"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10

Nice
Sent from my SM-N930F using XDA-Developers Legacy app

Woow, very nice present GREAT JOB!!!

Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!

In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.

Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.

jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.

Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:

jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.

joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it

Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good

joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)

How are you rooted

joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)

thread updated if any questions please pm me

Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!

Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk

Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?

Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly

[RECOVERY][EXPERIMENT/TEST] TWRP 3.2.1.x for TF701T

Hi, I don't post much on here but I wanted to share something with everyone since this is one of my fav tablets (before one of my drives crash and the data is lost, lol).
Disclaimer: I'm providing this AS-IS, I've been using this for about a few weeks now and while there may be bugs, it's been working for me and figure I'd share a newer version of TWRP for the TF701T. This will need some testing, I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base).
Hopefully this helps someone who loves this lil tegra transformer as much as I do!
I'll post links to source later on but to build this but if anyone wants to try;
-I used a slightly modded version of the zombi-x device tree
-tweaked the rm-wrapper (from the timduru katkiss device tree) so it references the correct includes (I was building under zombi-x 5.1 using omni twrp 8.x)
-Since the device tree was already using a prebuilt kerenel, I plugged the one from the TWRP 2.8.x kang/area51 by sdbags release
-The "rom base" folder I was building under was "zombi-x" 5.1/LP
-and the TWRP sources were from omnirom's oreo/8.x source
Here's a link to my dropbox tf701t folder, I keep a backup in the recovery folder.
I also built a 3.0.0.0 "area51" version, think I found that in the zombi-x repositories also. Both booted, roms I had installed, backups were made and restored under both however I've used the 3.2.1.x version more exetensively.
DROPBOX TF701T LINK!
Anyways, happy holidays everybody! I'll try and keep up with this post and update things when I get a chance, but for now rock on!
PS. Should be able to
Code:
fastboot boot <recoveryimagefile.img>
to test it before flashing permanently with
Code:
fastboot flash recovery <recoveryimagename.img>
PS2. Added images to post for 3.2.1.0 and the "Area51" 3.0.0.0 builds, Enjoy!
PS3. UPLOADED SOURCES! (finally, lol)
DEVICE TREE
-The device tree is still setup to use the prebuilt kernel (I compiled from source posted below this, with gcc 8.x toolchain). If using the kernel source below, use recovery_tf701t_defconfig - otherwise just make sure whatever config you run is setup to use LZMA for ramdisks here.
-Also this device tree is setup to use F2FS, I left the original ext4 fstab files included with a ext4_* prefix if anyone's curious. I'll fix that eventually and split them into 2 branches (ext4-only and f2fs).
KERNEL SOURCE
-This experimental kernel has some tweaks, F2FS support (no encryption), O/C @ ~2.5Ghz, bunch of extra governors (lionheart works nicely), but in it's base form works great for booting recovery.
Hopefully this stuff helps others bulding for this awesome lil tablet! Back to some more compilations while I got time.
UPDATE: F2FS Test (12/30/17)
-Added a recovery build that I have been running for a bit with F2FS support
-Use this with a ROM that supports F2FS, or repack a boot.img with a F2FS kernel and mod the ramdisk (edit fstab to mount /data /system and /cache with F2FS.).
-It supports the usual ext4 and other filesystems, but defaults to f2fs when using the format data and wipe commands (modded fstab on /system /cache /data).
-Also haven't had any issues formatting /cache, or touch not working with this kernel. I'll get around to a normal ext4 version and upload that as it seems to fix the /cache issues.

Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.

hitmancho said:
Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.
Click to expand...
Click to collapse
Glad it works for you too, I noticed the /cache issue also on the other TWRP 2.8.x version posted for this tablet too. One thing that I do (even on the other TWRP) is wipe the partition I want (or change its fs type) first, and if I need to touch another partition then I reboot the recovery and it works.
It's annoying, I'm currently testing building the kernel inline instead of using the 2.8.x kernel (from that other posted recovery) in the device tree. I'm using sources that I know boot, just playing with the configs to see how it plays with TWRP. I ported over the f2fs stuff from the katkiss kernel to mess around with, boots in the rom fine - so if I can get it to boot recovery then the f2fs formatting stuff should work and mount correctly.
Sidenote - one thing I notice with the 3.2.1-0 version is the screen seems to work better, I haven't had the touchscreen not responsive issue I had with the previous TWRP 2.8.x version.
Going for a coffee, I'll play around with it tonight (and remember to upload stuff to my github eventually to share). Long day of work, time to unwind

Small Update (Progress is good!)
So, took some time to dig around why it wasn't booting the recovery when I built from the same (working) kernel source I'm booting the normal android os with. Turns out, most likely due to space savings, the recovery is set to boot LZMA - turned that on in the config and that kernel now booted up recovery perfectly!
I'm rebuilding the kernel, since in my infinite wisdom, I compiled with my selinux disabled kernel - which also worked, but bombed out on any rom zips that ran anything to do with contexts/perms. Good news was F2FS worked mounting, formatting, etc.. Hopefully tomorrow I'll have a selinux friendly f2fs supporting kernel for recovery that'll work.
Random sidenote: I was eyeing the newer kernel drivers (from 4.x), If everything works as it's currently configured, I'll give try backporting the newer stuff and see how she runs. Just wanted to post a small update with some notes just in case anyone in wants to try building it themselves.

Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.

silverchairbg said:
Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.
Click to expand...
Click to collapse
I need to reformat /system and /cache only - most times. No need to reinstall apps.

You're lucky then, I always end up with errors on dirty flash and format /data also fails, so I resort to changing FS. Sometimes even this gives errors and I need to do it several times until errors are gone.

I just restart recovery and try formatting again.

AmauryRR great work! Please use the memory card of the docking station

Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).

I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base)
Click to expand...
Click to collapse
Can you, please, describe how it is working?
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Sasisco said:
Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).
Click to expand...
Click to collapse
Yes, please, more info on that!

Tf701t update
Hi AmauryRR,
Any chance you could break the process down step by step for none-IT people like me? i have tried everything but think i have to accept that this is above my pay grade .
i am especially having a difficult time with the boot loader. Indicates the following: "An unknown error occurs, which may be a network......try again later"
i can email you the screenshots as i can't seem to upload them here.
regards
rob

Can someone get me recovery work in android 4.2.2 ,
10.14.1.47 bootloader please?
"" I searched in google all recovery file can't be downloaded''

Any chance of a flashable version of this?