Database Develop

Simple Root for Unlocked Bootloaders (SGP311/312)

It was clear that rooting some Sony devices was not as easy as it should be. This is for unlocked bootloader users, who want to quickly root a stock ROM by flashing a rooted boot.img. It is for the POLLUX_WINDY (ie. the SGP311/312) devices ONLY.
Do not install this on the Pollux (tablet Z with LTE), or it will no longer boot - use flashtool to fix it
There may have been some in the past, but these tend to be full of other "tweaks", like hideous amateur boot logos, and stupid changes like setting ro.secure=0. That's a bad idea, it can break things, and frankly, I know from experience of myself and others that there is a need for a FAST way to root your unlocked device after flashing a new ROM, rather than messing around with downgrading and OTAs.
This will NOT work on locked bootloader, but this is not intended for them. This doesn't include 9001 different recoveries either, like some "kernels" do. This is the stock kernel, with root added, and nothing stupid added.
There is one security improvement made - ro.adb.secure has been set to 1. This is an important security feature, please don't complain about it. If you don't use ADB, you'll never see it, and it won't change anything. If you use adb, it will offer you greater security on 4.2+ stock Sony ROMs, which don't have this feature enabled. You will be prompted to accept the computer connection on the phone, just like in "AOSP" Android 4.2 and above.
The downloads are available above, in the "Downloads" tab. If you have a particular version you wish to request, simply post the kernel.sin. I have made this for only the SGP311/312 (Pollux_Windy) Tablet Z phone images right now, but will consider expanding it for other devices if there is demand and people who can test.
Enjoy simple root, without the nonsense. None of the "don't mirror my files" crap. None of the "please give me donations", none of the "omg credit me as the best person ever". Feel free to share, use, re-use, mirror, enjoy. And I think you'll find that these files are rather helpful for the unlocked bootloader root community I've been thinking about making them for months, but it seems that nobody has ever bothered to.
Click here to download
XDA:DevDB Information
Simple Root for Unlocked Bootloaders (SGP311/312), a Tool/Utility for the Sony Xperia Tablet Z
Contributors
pulser_g2, Chainfire
Version Information
Status: Stable
Current Stable Version: 3.1.C.0.136
Stable Release Date: 2013-09-14
Created 2013-09-14
Last Updated 2013-09-14

Hi, do you mean this root method doesn't work for the Tablet Z Lte model? Is there any way to get a method which can root the Lte version ? Thanks !

Omg @pulser_g2 you is best person ever... But seriously thanks man
Sent from my SGP312 using XDA Premium 4 mobile app

epcwong said:
Hi, do you mean this root method doesn't work for the Tablet Z Lte model? Is there any way to get a method which can root the Lte version ? Thanks !
Click to expand...
Click to collapse
Correct.
But, since I feel generous, if you upload me the kernel.sin file from your LTE model, I will make a rooted boot.img for it. You can attach them to a post here if you like - just the kernel.sin. Please name them per the stock ROM version, so I can label it correctly.

pulser_g2 said:
Correct.
But, since I feel generous, if you upload me the kernel.sin file from your LTE model, I will make a rooted boot.img for it. You can attach them to a post here if you like - just the kernel.sin. Please name them per the stock ROM version, so I can label it correctly.
Click to expand...
Click to collapse
Hi there, thanks for your reply. What do you mean by the kernel.sin file from my LTE model (mine is the HK version) ? I have taken a photo shot regarding my pad's rom and kernel version details for your reference as attached. If there is not the information that you need, please tell me how to get the "kernel.sin" file from my pad ! Thanks again for your kindness !
{
"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"
}

pulser_g2 said:
Correct.
But, since I feel generous, if you upload me the kernel.sin file from your LTE model, I will make a rooted boot.img for it. You can attach them to a post here if you like - just the kernel.sin. Please name them per the stock ROM version, so I can label it correctly.
Click to expand...
Click to collapse
i will upload the kernel.sin from the FTFs
is that okay for you?

Yes, thank you so much ! I'll appreciate that !

@pulser_g2
Here ya go
kernel.sin from 4.2.2 FTF
Google Drive

Thank you so much !!!

epcwong said:
Hi there, thanks for your reply. What do you mean by the kernel.sin file from my LTE model (mine is the HK version) ? I have taken a photo shot regarding my pad's rom and kernel version details for your reference as attached. If there is not the information that you need, please tell me how to get the "kernel.sin" file from my pad ! Thanks again for your kindness !
View attachment 2292738
Click to expand...
Click to collapse
Hi, here attached with the kernel.sin file for you. The Rom version is 10.3.1A.0.244. Thank you so much for your kindly attention for this matter !
---------- Post added at 01:10 PM ---------- Previous post was at 01:03 PM ----------
Sorry I can't upload the kernel.sin file becuase it was said " invalid file ", Sorry about this !
---------- Post added at 01:15 PM ---------- Previous post was at 01:10 PM ----------
Sorry I can't upload the kernel.sin file becuase it was said " invalid file ", Sorry about this !

Sgp311 4.2.2
Will this work on 16gb Wi-fi model SGP311 with android 4.2.2?

chiobesek said:
Will this work on 16gb Wi-fi model SGP311 with android 4.2.2?
Click to expand...
Click to collapse
If the file in the downloads list matches the version you are running (per about screen), then yes it will.

MightyBear007 said:
@pulser_g2
Here ya go
kernel.sin from 4.2.2 FTF
Google Drive
Click to expand...
Click to collapse
The attachment is rooted for this version. As you didn't give me the firmware version (ie. 10.A..whatever...), I won't add it to the list. Please test and let me know if it works. If this fails, just re-flash kernel using flashtool.

pulser_g2 said:
The attachment is rooted for this version. As you didn't give me the firmware version (ie. 10.A..whatever...), I won't add it to the list. Please test and let me know if it works. If this fails, just re-flash kernel using flashtool.
Click to expand...
Click to collapse
You just did a ro.secure in the ramdisk
Am I right?

MightyBear007 said:
You just did a ro.secure in the ramdisk
Am I right?
Click to expand...
Click to collapse
Nope. Setting ro.secure=0 is NOT the right way to root.
The ramdisk is modified, it will detect if you have root already, and if not, it will install SuperSU and the corresponding su binary on root. I also set ro.adb.secure=1, to add extra security for the device (now you need to approve ADB connections to unrecognised computers).
If you use ro.secure=0, this will break many apps with "root detection", as well as being a horrendously ugly hack, which introduces all sorts of vulnerabilities. ro.secure should always be set to 1
I strongly advise you don't use root methods that set ro.secure=0, as well as any kernels that do it. It's much safer to not have a rooted ADB shell lying available to anything that connects to your device... Including... you know... an app running on your device that initiated an adb connection to 127.0.0.1
So yes, this gives you root without adding stupid extra security holes like many kernels and "root methods" do

pulser_g2 said:
Nope. Setting ro.secure=0 is NOT the right way to root.
The ramdisk is modified, it will detect if you have root already, and if not, it will install SuperSU and the corresponding su binary on root. I also set ro.adb.secure=1, to add extra security for the device (now you need to approve ADB connections to unrecognised computers).
If you use ro.secure=0, this will break many apps with "root detection", as well as being a horrendously ugly hack, which introduces all sorts of vulnerabilities. ro.secure should always be set to 1
I strongly advise you don't use root methods that set ro.secure=0, as well as any kernels that do it. It's much safer to not have a rooted ADB shell lying available to anything that connects to your device... Including... you know... an app running on your device that initiated an adb connection to 127.0.0.1
So yes, this gives you root without adding stupid extra security holes like many kernels and "root methods" do
Click to expand...
Click to collapse
Nice Information
Thank you So much for replying!
I have to change all my kernels ram disk to 1
Sent from my C6902 using XDA Premium 4 mobile app

so i am right ?
Download the file rooted-SGP311_10.3.1.C.0.136-boot.img, unlock the bootloader of my tablet Z with android 4.2 (16gb wifi only running 10.3.1.C.0.136) at the moment, go for fastboot, do fastboot flash boot filename.img and i will be rooted with nothing else changed ?
just want to the root for ad free android, but stay with the stock system
thank u

Havoc2k said:
so i am right ?
Download the file rooted-SGP311_10.3.1.C.0.136-boot.img, unlock the bootloader of my tablet Z with android 4.2 (16gb wifi only running 10.3.1.C.0.136) at the moment, go for fastboot, do fastboot flash boot filename.img and i will be rooted with nothing else changed ?
just want to the root for ad free android, but stay with the stock system
thank u
Click to expand...
Click to collapse
Instead of going through all the trouble of unlocking the boot loader and flashing an image, use the Vroot tool instead; it works fast and and does not require unlocking the boot loader. Search this forum for information about the Vroot tool.

LENOVO A7000-a DEVELOPMENT

{
"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"
}
STOCK FIRMWARE RELEASED VERSION (A7000-a_S136_150519_ROW) ( ORIGINAL POST)
Download here
CWM RECOVERY BY ME ( WORKING BACKUP RESTORE)
Download here
TWRP RECOVERY BY @linerty (ORIGINAL POST)
Download here
SP FLASH TOOLS ( LATEST)
Download here
MT6752 SCATTER FILE
Download here
HOW TO ROOT:
1. Download CWM/ TWRP recovery
2. Flash via Sp flash tools( da with all checksums)
3. Download updatesu.zip form here
4. Put the zip in sd card.
5. Reboot to cwm/TWRP recovey
6. Select update from sd
7. Choose the zip and update
THANKS TO:
1. MY CHINESE FRIENDS FOR PROVIDING ME THE FIRMWARE.
2. @junedkh for telling me about the A7000-a_S136_150519_ROW FIRMWARE.
3. @maxritz ( Ritesh) FOR PORTING THE FIRST WORKING CWM.
4. @hafeeeeeeeez @atulmehla @Deep Pancholi FOR FULL SUPPORT & TESTING.
5. FRIENDS FOR SUPPORTING.
6. HOPE ..... FOR NOT GIVING UP ON US
WHATEVER YOU DO AT THIS AT YOUR OWN RISK. NEITHER ME NOR XDA WILL BE RESPONBILE IN CASE OF ANY HARDWARE/ SOFWARE DAMAGES CAUSED BY YOU TRYING THESE METHODS. YOU WILL BE SOLELY RESPONSIBLE.
RESPECT OUR WORK
PLEASE DON'T PM ME, IT'S A REQUEST , CAUSE I WON'T BE ABLE TO ANSWER ANY OF'EM
THANKS
CUSTOM ROMS PORTED BY ME:
PURE AOSP v 1.0
FEATURES:
** VERY SMOOTH UI, LIGHTWEIGHT .
** STABLE, READY FOR DAILY USE.
** SUPERB BATTERY, SUPERFAST CHARGING.
** 8MP FRONT/ 8 MP BACK
** GAPPS INCLUDED.
** NON ROOTED.
UPDATE AOSP V1.1:
Changelogs:
Added Dolby Atmos
Added ES File Explorer
Some Error Fixed.
When Connected to pc shows Lenovo A7000.
Add Owner Info.
Added Guest Mode.
Added Root.
Added extra wallaper
and Many more..
BUGS:
** LED ONLY SHOWS RED LIGHT. ( NO GREEN LIGHT)
HOW TO INSTALL:
1. DOWNLOAD ROM FORM HERE
2. REBOOT TO RECOVERY ( CWM) ( VOL UP + VOL DWN + PWR)
3. GO TO WIPE MENU
4. SELECT OPTION, WIPE PRE-FLASH.
5. GO TO INSTALL MENU, SELECT FROM SD CARD.
4. IT WILL TAKE A WHILE... DONE...
REMEMBER THIS WILL VOID YOU WARRANTY.
ENJOY..
SCREENS:
DEAR FRIENDS,
I do not own this device ( Lenovo A7000) anymore.. Matter of fact I do not own any mediatek devices now ( may be never will) K3 note was my last mediatek device...
So further support regarding development or bug fixes of ROMS ( my ports) is not possible from my end.
Thank you guys so much for your Kind support..

+1
+1

+1
---------- Post added at 02:10 PM ---------- Previous post was at 01:27 PM ----------
comeon dev's show us the power of xda

I can't see any development related questions here. You need to tell us where you are stuck if you want help. (I assume you've read the forum subtitle and the tutorials)

+1

_that said:
I can't see any development related questions here. You need to tell us where you are stuck if you want help. (I assume you've read the forum subtitle and the tutorials)
Click to expand...
Click to collapse
We need cwm or twrp for our device and rooting also needed

Custom Recovery
_that said:
I can't see any development related questions here. You need to tell us where you are stuck if you want help. (I assume you've read the forum subtitle and the tutorials)
Click to expand...
Click to collapse
Yes, the post has been edited... firstly we are in a great need of Custom recovery and we will be grateful if someone does that for us.
if the recovery ( CWM/ TWRP) is made the rooting issue will be solved. Then we will move on to the Custom Rom section. But, for now we need a working custom recovery.

hafeeeeeeeez said:
We need cwm or twrp for our device and rooting also needed
Click to expand...
Click to collapse
puchupechu said:
Yes, the post has been edited... firstly we are in a great need of Custom recovery and we will be grateful if someone does that for us.
if the recovery ( CWM/ TWRP) is made the rooting issue will be solved. Then we will move on to the Custom Rom section. But, for now we need a working custom recovery.
Click to expand...
Click to collapse
I suggest you start reading here:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro

_that said:
I suggest you start reading here:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Click to expand...
Click to collapse
Basically we are noob on this thing thats y asking help from expert dev's we are trying hard since last 1 month no success we are unable to figure out we build cwm too but when we flash its getting flashed but when we go to recovery again its showing stock recovery

to try
http://www.phonehorn.com/2015/04/how-to-root-lenovo-a7000-and-install-cwm-recovery/
I don't know this work I think help this

estate100 said:
http://www.phonehorn.com/2015/04/how-to-root-lenovo-a7000-and-install-cwm-recovery/
I don't know this work I think help this
Click to expand...
Click to collapse
Already tried its showing successfully installed but when we go to recovery it showing stock recovery only

estate100 said:
http://www.phonehorn.com/2015/04/how-to-root-lenovo-a7000-and-install-cwm-recovery/
I don't know this work I think help this
Click to expand...
Click to collapse
These are of no help as they confuse Lenovo Note K3 with our Phone...... infact, our phone is different from K3 note in many aspects.
None of these methods floating around are actually working, including all the PC rooting softwares.
Matter of fact, people giving these tutorials don't even own a real Lenovo A7000a IRL. We are the users and we are well acquainted with the Dilemma.
A custom Recovery ported by a altruistic developer can only put us out of our miseries.

+1 ji..
This phone is pretty good. I think, it Comes with unlockable bootloader / unsafe boot image. Even the source + stock firmware is already available.
If experienced developers helps us by giving any custom recovery, we will be very thankful and grateful to them as this great phone is lacking in this area only.
[Sorry for bad English, as it's not my mother tongue]
Sent from my Lenovo A7000-a using Tapatalk

Here it is but. if you know chinese.
Well its final i think.
can someone test if the SDCard works.
the mounts work.
remember. you need to delete "recovery-from-boot.p" in /system
this can over write the recovery.
original recovery from
http://cellphonemic.com/lenovo-k3-note-recovery.html
i tried the original recovery image. Didn't work. so i ported. I replaced the core files and retained the ram disk and did a few edits.
Thanks to the guys who made that recovery. It seems that was originally for a K50
credits:
Kishore Dutta for the stock recovery.
The guy whoever made that original recovery
My patience, annoyance and my anger that made me do it.
Feel free to give me a thumbs up, lots of money, anything. Thank is welcome too.

how please
maxritz said:
Well its final i think.
can someone test if the SDCard works.
the mounts work.
remember. you need to delete "recovery-from-boot.p" in /system
this can over write the recovery.
original recovery from
i tried the original recovery image. Didn't work. so i ported. I replaced the core files and retained the ram disk and did a few edits.
Thanks to the guys who made that recovery. It seems that was originally for a K50
credits:
Kishore Dutta for the stock recovery.
The guy whoever made that original recovery
My patience, annoyance and my anger that made me do it.
Feel free to give me a thumbs up, lots of money, anything. Thank is welcome too.
Click to expand...
Click to collapse
How to do this a explanation is needed thnx

1. Download CWM recovery ( link given in group & xda)
2. Flash via Sp flash tools( da with all checksums)
3. Download updatesu.zip form https://download.chainfire.eu/396/supersu/
4. Put the zip in sd card.
5. Reboot to cwm recovey
6. Select update from sd
7. Choose the zip and update
Done ??
MOST IMPORTANTLY FLASH AT YOUR OWN RISK WE ARE NOT RESPONSIBLE IF ANY DAMAGE CAUSED TO YOUR PHONE. YOU WILL BE SOLELY RESPONSIBLE

puchupechu said:
1. Download CWM recovery ( link given in group & xda)
2. Flash via Sp flash tools( da with all checksums)
3. Download updatesu.zip form https://download.chainfire.eu/396/supersu/
4. Put the zip in sd card
[5/12, 8:10 AM] Kishore Datta: 5. Reboot to cwm recovey
6. Select update from sd
7. Choose the zip and update
Done ??
MOST IMPORTANTLY FLASH AT YOUR OWN RISK WE ARE NOT RESPONSIBLE IF ANY DAMAGE CAUSED TO YOUR PHONE. YOU WILL BE SOLELY RESPONSIBLE
Click to expand...
Click to collapse
Hi...!
did it worked for u.....?

Matrix and I were the 1st one to test it and get root. So ..yes, of course it worked for us

Can u please give me the scatter file u flashed the recovery(CWM)

writes the cmw recovery but the phone still shows not rooted
and also how to delete the recovery file in system
---------- Post added at 04:36 AM ---------- Previous post was at 04:31 AM ----------
Confirmed Got it
Lenovo A7000 Rooted
thnx
---------- Post added at 05:14 AM ---------- Previous post was at 04:36 AM ----------
darylzero said:
writes the cmw recovery but the phone still shows not rooted
and also how to delete the recovery file in system
---------- Post added at 04:36 AM ---------- Previous post was at 04:31 AM ----------
Confirmed Got it
Lenovo A7000 Rooted
thnx
Click to expand...
Click to collapse
Root not sticking after reboot need to check this
any idea how to make it stick after reboot

[RECOVERY] TWRP 3.1.0-1 - SM-T710/715/810/815 - update 13/3/2017

{
"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"
}
UPDATE 12/3/2017 - New version of TWRP has been released v3.1.0-0. See below:
https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html
I have updated versions T710/715/T810/T815 with new builds. TWRP is now v3.1.0-1
Features:
System image backup/restore
Factory image flashing.
F2FS support.
Supersu root option removed which would cause a bootloop on 5.1.1 and 6.0 devices.
MTP fix - MTP now finally working in recovery.
SEANDROID warning fix
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
I have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP 3.1.0-1 for Galaxy Tab S2 T710/T715/T810/T815 models - Lollipop 5.0.2/5.1.1 Marshmallow 6.0.1/Nougat 7.0
twrp_3.1.0-1_sm-t710_13317
twrp_3.1.0-1_sm-t715_13317
twrp_3.1.0-1_sm-t810_13317
twrp_3.1.0-1_sm-t815_13317
twrp_3.1.0-1_sm-t817r4_201117
TWRP 3.0.2-1 for Galaxy Tab S2 T710/810 models - Lollipop 5.0.2/5.1.1 Marshmallow 6.0.1
TWRP_3.0.2-1_sm-t710
TWRP_3.0.2-1_sm-t810
TWRP 3.0.0-1 for Galaxy Tab S2 T710/715/810/815 models - Lollipop 5.0.2/ 5.1.1/6.0.1
TWRP_3.0.0-1_sm-t710
TWRP_3.0.0-1_sm-t715
TWRP-3.0.0-1-sm-t810
TWRP_3.0.0-1_sm-t815
TWRP 2.8.7.1 for Galaxy Tab S2 T710/715/810/815 models - Lollipop 5.0.2 and 5.1.1
LOLLIPOP 5.0.2 ONLY:
twrp_2.8.7.1_LL_5.0.2_t710
twrp_2.8.7.1_LL_5.0.2_t715
twrp_2.8.6.3_LL_5.0.2_t810
twrp_2.8.6.3_LL_5.0.2_t815
LOLLIPOP 5.1.1:
twrp_2.8.7.1_LL_5.1.1_t710
twrp_2.8.7.1_LL_5.1.1_t810
Device tree on Github
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
Note: T717T/P, T817T/P users can flash T*10 or T*15 variant respectively.
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
TO ROOT:
Flash SuperSU below with TWRP.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Credits to Teamwin for their work. Suzook and my other testers.

You are the best
---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------
small issue : twrp_2.8.7.1_LL_5.1.1_t810.tar
access denied

whynottoday said:
You are the best
---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------
small issue : twrp_2.8.7.1_LL_5.1.1_t810.tar
access denied
Click to expand...
Click to collapse
Same here.

@ashyx incredible work.. does this mean root is achievable through SuperSU flash in TWRP? Or you need a custom kernel for that like on Galaxy S6?

it works thanks

itskapil said:
@ashyx incredible work.. does this mean root is achievable through SuperSU flash in TWRP? Or you need a custom kernel for that like on Galaxy S6?
Click to expand...
Click to collapse
You need my custom kernel.

I just want to confirm that t710_twrp_2.8.7.1_LL_5.0.2 also works on T715.
Vielen Dank!

Flashed the TWRP LL5.0.2 version for T810. Everthing´s ok. Thanks.

Deacon-Frost said:
Flashed the TWRP LL5.0.2 version for T810. Everthing´s ok. Thanks.
Click to expand...
Click to collapse
I flashed the 5.0.2 version on the 710 ok (even though Im on 5.1.1, the 5.1.1 tar would not work)

thedanks said:
I flashed the 5.0.2 version on the 710 ok (even though Im on 5.1.1, the 5.1.1 tar would not work)
Click to expand...
Click to collapse
Please give more details of what didn't work. I can't debug with such generic comments.

thedanks said:
I flashed the 5.0.2 version on the 710 ok (even though Im on 5.1.1, the 5.1.1 tar would not work)
Click to expand...
Click to collapse
Please give more details of what didn't work. I can't debug with such generic comments.

Hi ashyx ......I see,you took the 815 also to the list. Anyone test it? Thx a lot man. Will Try to get root with twrp. Anyone tested a supersu.zip ? Should work also too get root. ...
Gesendet von meinem SM-T815 mit Tapatalk
---------- Post added at 03:57 PM ---------- Previous post was at 03:46 PM ----------
So, maybe the first custom Roms will come soon. ....... ????
Gesendet von meinem SM-T815 mit Tapatalk
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
@ashyx ,what is the easiest way to deodex a firmware?
Gesendet von meinem SM-T815 mit Tapatalk

ashyx said:
Please give more details of what didn't work. I can't debug with such generic comments.
Click to expand...
Click to collapse
Sorry I grabbed a copy of the permissive kernel tar that was broke... once I got the new version all was fine.

Just root my SM-T815 ......great work, thx man.....
Gesendet von meinem SM-T815 mit Tapatalk

It work fine for my T710 with 5.0.2

Just noticed a minor issue with the T710 5.0.2 version. In the Reboot options pressing "Power Off" reboots back into recovery instead of turning off.

jabbado said:
Just noticed a minor issue with the T710 5.0.2 version. In the Reboot options pressing "Power Off" reboots back into recovery instead of turning off.
Click to expand...
Click to collapse
Remove your usb cable.

ashyx said:
TWRP 2.8.7.1 for Galaxy Tab S2 T710/715/810/815 models - Lollipop 5.0.2 and 5.1.1[/SIZE
Click to expand...
Click to collapse
Would you mind sharing your device tree?
edit: only reason I ask is it's been a loooong time since I've compiled a recovery for an unsupported device and I'd like to get back in the loop... only my attempts at doing so are failing lol. Thanks.

BigBot96 said:
Would you mind sharing your device tree?
edit: only reason I ask is it's been a loooong time since I've compiled a recovery for an unsupported device and I'd like to get back in the loop... only my attempts at doing so are failing lol. Thanks.
Click to expand...
Click to collapse
I don't have a fully working device tree yet.
The device tree I initially created to compile twrp always failed to boot even though the compile process always completed successfully.
I finally managed to build a bootable version by porting some of the binaries and libs from another device and using some of the files from the compile.
It seems when compiling from the latest 5.1 omni sources there is an issue, well for me anyway.
I contacted big biff on IRC about this and he seems to think it should compile OK and doesn't know what the issue is.
However I can't even get a bootable version from existing working trees.
I can't be bothered reverting everything to earlier sources so just used some of the working files from the build I compiled from source and the rest ported over.
I still haven't managed to nail the issue.
If you want I can get something up on github and maybe we can work on it to get it booting?
You will have to bear with me though as I deleted a load of stuff as I needed the space, so it may have gone.
What is the issue you are having?

ashyx said:
I don't have a fully working device tree yet.
The device tree I initially created to compile twrp always failed to boot even though the compile process always completed successfully.
I finally managed to build a bootable version by porting some of the binaries and libs from another device and using some of the files from the compile.
It seems when compiling from the latest 5.1 omni sources there is an issue, well for me anyway.
I contacted big biff on IRC about this and he seems to think it should compile OK and doesn't know what the issue is.
However I can't even get a bootable version from existing working trees.
I can't be bothered reverting everything to earlier sources so just used some of the working files from the build I compiled from source and the rest ported over.
I still haven't managed to nail the issue.
If you want I can get something up on github and maybe we can work on it to get it booting?
You will have to bear with me though as I deleted a load of stuff as I needed the space, so it may have gone.
What is the issue you are having?
Click to expand...
Click to collapse
I'm getting the same issue where it won't boot. Sits at the BL with the Recovery is SE Android warning. Can't get past that dagum screen. Here's my current tree: https://github.com/BigBot96/android_device_samsung_gts2wifi
Compiles without errors but no go. The last recovery I ported was for the Verizon Galaxy Tab 2 7.0 LTE and it was very simple to get up and running. Both CWM and TWRP.

[Kernel+][Exynos] Kali NetHunter for the Galaxy S7 edge

​
WARNING: When using custom kernels on the S7 edge, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
OKAY SO
This is Kali NetHunter 3.15.2 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 NetHunter installer 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/nhsystem, 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.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.2 (stable, 2016-11-04)
Please be careful to download the right version based on this table:
SM-G935F, SM-G935FD, SM-G935W8, SM-G935X: kernel-nethunter-hero2lte-*
SM-G935K, SM-G935L, SM-G935S: kernel-nethunter-hero2ltekor-*
S7 flat: You're in the wrong forum!
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
This means that if your data partition is encrypted, you will need to use the [Format Data] button in TWRP to remove encryption.
This will delete all your data, including internal storage.
You should back everything up first before installing Kali NetHunter.
Samsung Smart Switch Mobile can be useful for this, and allows you to back up your apps to a location on an external SDcard.
Unfortunately it doesn't back up most app data.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
It's become apparent that there may be issues with the stock ROM and this kernel, and that it might run best on a Note 7 port.
FULL INSTALLATION 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"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
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 the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer 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.
For new installations: Download the nethunter-generic-arm64-kalifs zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 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 OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
THE KERNEL
The NetHunter kernel for the Galaxy S7 edge is based on Samsung's OSRC N930SKSU2BPID Note 7 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.44 (with dirtycow vulnerability patched)
SELinux permissive
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted data partition support
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
USB HID Gadget keyboard & mouse support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption disabled (not supported by custom kernels at the moment)
Kernel module support, insert your own modules!
CIFS, NFS available through included kernel modules
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
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
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
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.
Reboot after 60 seconds - Sometimes when you boot your device it could reboot after 60 seconds because of a Samsung secure service not responding. Unresolved, but rare, and only happens within 60 seconds of a boot.
DEVELOPMENT
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Galaxy S7 edge NetHunter kernel source: https://github.com/jcadduono/android_kernel_samsung_universal8890/tree/nethunter-6.0
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: Stable
Current Stable Version: 3.15.2
Stable Release Date: 2016-11-04
Created 2016-10-06
Last Updated 2016-11-04

Good job bro,
I have the ohap one installed and working perfectly,
Wifite and all works but cannot crack even my wep wifi and most of the other like metasploit same case .
How is this different from the previous one.

Dude, i have download kernel nethunter hero2lte marahmallow....... for my s7 edge and whioe flashing in twrp it shows error device unsuppported.
I have no prev version of nethunter . This is fresh one
Rom : kingrom v11
Kernel : prometheus 1.7.2 (tried with stock kernel also)
Pls help me out i wanna get this awesome stuff onto my phone...

I think you have mentioned it wrong hero2ltekor is for g935f/fd/......
hero2lte is for the others. Because in my g935fd hero2ltekor works the other doesnt flash.
Pls correct it.
edit: im stuck in bootloop now(heroltekor) somehing's wrong....

Future support for S7 flat?
Delivered by my Silver S7.

Camera with washed out colors or with working modes?

Has anyone been fortunate enough to get this to work?
Experience?
Sent from my SM-G935F using XDA-Developers mobile app

mandroid717 said:
Future support for S7 flat?
Delivered by my Silver S7.
Click to expand...
Click to collapse
yes just download herolte (rest everything is same) instead of hero2lte may ur lucky to work it out.
---------- Post added at 03:09 PM ---------- Previous post was at 03:08 PM ----------
efx7n said:
Camera with washed out colors or with working modes?
Click to expand...
Click to collapse
how did u get it working pls tell the file u hv downloaded, ur rom name and version ,kernel name and version
Thank you,

ahamed.rafi135 said:
Dude, i have download kernel nethunter hero2lte marahmallow....... for my s7 edge and whioe flashing in twrp it shows error device unsuppported.
Click to expand...
Click to collapse
try todays build I missed the 2 in hero2lte model check script. really weird because it should have also caught hero2ltexx
are you using the latest official twrp?
also the table is correct, so don't flash other model builds on your device
efx7n said:
Camera with washed out colors or with working modes?
Click to expand...
Click to collapse
i've never heard of this issue, no clue, i'm running it on note 7 with a flawless camera.
mandroid717 said:
Future support for S7 flat?
Delivered by my Silver S7.
Click to expand...
Click to collapse
youre in the wrong forum -> http://forum.xda-developers.com/galaxy-s7/development/kernel-kali-nethunter-galaxy-s7-t3475407

jcadduono said:
try todays build I missed the 2 in hero2lte model check script. really weird because it should have also caught hero2ltexx
are you using the latest official twrp?
also the table is correct, so don't flash other model builds on your device
i've never heard of this issue, no clue, i'm running it on note 7 with a flawless camera.
youre in the wrong forum -> http://forum.xda-developers.com/galaxy-s7/development/kernel-kali-nethunter-galaxy-s7-t3475407
Click to expand...
Click to collapse
Thanks for the kernel, does this work with Superman rom does anyone know? Is this essentially stock kernel with some extras, do all cores work?
One last question, is it safe to use the Note7 Canadian kernel on the Canadian S7 edge? I ask because unlike the US, the processors are not the same, S7 Edge is Qualcomm and Note7 is Snapdragon bit in the usa on the otherhand both are Snpdragon, same cpu.
Cheers!

cantenna said:
Thanks for the kernel, does this work with Superman rom does anyone know? Is this essentially stock kernel with some extras, do all cores work?
One last question, is it safe to use the Note7 Canadian kernel on the Canadian S7 edge? I ask because unlike the US, the processors are not the same, S7 Edge is Qualcomm and Note7 is Snapdragon bit in the usa on the otherhand both are Snpdragon, same cpu.
Cheers!
Click to expand...
Click to collapse
It's impossible to use Snapdragon kernel on Exynos. We're only supporting the Exynos devices, as the Canadian Snapdragon is locked.
The Canadian S7 edge should run the International S7 edge kernel without any issues.
I would assume it should work fine with any of the ROMs out right now, unless their boot image is unable to fit the new kernel. Most if not all ROMs are probably using the stock boot image with a few text edits here and there, so they should be fine.
As for the all cores working issue, I ran into one where 2 of the main cores were unable to start up when I had KALLSYMS disabled. I had to enable it anyways since I'm using module support, so at least that's not an issue in this kernel that exists, I think...

I'm running stock everything.. will this still work? I have twrp running as previously rooted but the app I rooted for requires permissive but mine is enforcing..

Will it work with super-man rom and Will everything work fine
Sent from my SM-N930F using XDA-Developers mobile app

All good running Decent UltraLite 3.5 on my W8 S7E with full Kali latest build and kernel. Can't wait to play...

BugsDroid said:
All good running Decent UltraLite 3.5 on my W8 S7E with full Kali latest build and kernel. Can't wait to play...
Click to expand...
Click to collapse
Links of the files? [emoji106] I meant which nethunter files did you install on this Rom?

Handeman707 said:
Links of the files? [emoji106] I meant which nethunter files did you install on this Rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/s7-...ent-debloated-dd1-addons-mods-t3435516/page58
https://build.nethunter.com/nightly/
I used the files from the 24th of this month.

Downloadlink is Dead

Eugenic said:
Downloadlink is Dead
Click to expand...
Click to collapse
Only works using Firefox for me.

BugsDroid said:
http://forum.xda-developers.com/s7-...ent-debloated-dd1-addons-mods-t3435516/page58
https://build.nethunter.com/nightly/
I used the files from the 24th of this month.
Click to expand...
Click to collapse
Indeed works for me also, Thanks!!, Installed Rom (Decent UltraLite 3.5), Installed Kali Nethunter files (nethunter-generic-arm64-kalifs-full-rolling-3.15.2-20161024-2241) and latest Nethunter Kernel (kernel-nethunter-hero2lte-marshmallow-3.15.2-20161024-2241), Running now Nethunter Kali linux on a Touch Wiz Samsung 7 Edge!
B.T.W.: Do I need a "External Mini Wifi Adapter" with "WiFite v2" to scan the network and which one is the best?? Or do i also to activate some linux code? Thanks Anyway!

Handeman707 said:
B.T.W.: Do I need a "External Mini Wifi Adapter" with "WiFite v2" to scan the network and which one is the best?? Or do i also to activate some linux code? Thanks Anyway!
Click to expand...
Click to collapse
The adapter is required to use monitor mode. You can still do MITMF and similar tools without it.
So far from my testing, this doesn't work with any S7 roms. Only the N7 ports, has anyone else experienced this?

[OMS7][NOUGAT][7.1.2][obake]XPerience-11.1.2_r29 [NIGHTLY]

{
"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"
}
XPerience 11.X.X for the Motorola Moto DROID Ultra
Maded by Klozz Jesus AKA TeamMEX
XPerience is a free, community built distribution of Android 7.1.1 (Nougat) which greatly extends the capabilities of your phone.
This project are based on AOSP CAF
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.
*/
NOTE: READ this PLS
All required device configs, blobs and kernel source are on my github u know the url
Please don ask for etas
Please don't report same bugs all time
Report with logcat and dmesg
Screenshots representative only
Click to expand...
Click to collapse
Features:
Substratum support
XPerience Updater
NetworkTrafficMetter
Ambient Display with customizations
OMS-N7
Force expanded notifications
Disable inmersive messages
Inmersive recents
Alessa app for kernel tweaking.
XPerience Active Display
Pocket Judge
* Judge if device is in pocket.
* Notify clients callbacks when pocked state changes.
* Start listening when device becomes not interactive.
* Stop listening when device becomes interactive and is NOT in pocket.
policy: introduce pocket lock
fingerprint: disable when device is in pocket
One Hand mode (slide your finger across the navigation bat to switch between the standard and mini screen views(from the center))
App sidebar
WORKING:
Working
Rild
LTE/3G/2G
Bluetooth
MTP
Sensors
Led
Wi-Fi
MUSIC
sounds
Videos
[*] Camera
[*] camcoder
SELinux Enforced
New audio HAL fully working
Mic working.
Not working/ Bugs:
camera
posibility maybe random mic bug like ghost
How to install:
Download zip from Downloads:
Put zip into Internal Storage
Reboot into Recovery like TWRP
Flash zip file XPerience-11.x.x-xxxxxxx-obake.zip
Flash Gaaps
Wipe dalvick-cache and cache
Reboot and config
Reboot Again and enjoy!
Screenshots:
https://lh3.googleusercontent.com/****Wbf15v8tBRMttby0pViCXsGn22HuE5oJ3g9OXbcus2ybc3wnLGVggSXayByZOaShwr9kihLRmpHRvKXsaSwXxACOnkRt=w1366-h768-rw-no
Basketbuild NIGHTLY's
Sourceforge mirror 1
xperience web
MD5:
Google APPS
http://opengapps.org
​
Changelog in second Post:
Thank you for Donate: (if u want to post ur nick instead of your name send PM)
If you like my work, you can buy me a coffee with your donatives. All donations are appreciated. and this can help me to pay some bills about internet
​
XDA:DevDB Information
The XPerience Project for Motorola Moto DROID Ultra, ROM for the Motorola Droid Ultra
Contributors
TeamMex
Source Code: https://github.com/XPerience-AOSP-Lollipop/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: unlocked bootloader
Based On: AOSP,CAF
Version Information
Status: Testing
Created 2017-10-01
Last Updated 2017-09-30
Click to expand...
Click to collapse

Reserved

Reserved

Untested some guy asked me if I can port my build N from ghost so here u go
maybe we have the same bugs here like ghost.
please test and report.

What bugs should I expect ? Planning to test it over the weekend.

i wana try it but stuck on kitkat 4.4 su-6-7.7 firmware, any way to root in and unlock its bootloader

First you have to unlock the bootloader, but I think on the latest 4.4.su 6-7.7 isn't possible ...

Still got my droid mini around. Will do some testing for y'all.
Edit: Can't get this to boot. It's stuck on the BL screen and doesn't even reach the rom's boot screen. Using TWRP 2.8.4.0. Is there an updated one for obake?

SnipeR_TT said:
Still got my droid mini around. Will do some testing for y'all.
Edit: Can't get this to boot. It's stuck on the BL screen and doesn't even reach the rom's boot screen. Using TWRP 2.8.4.0. Is there an updated one for obake?
Click to expand...
Click to collapse
Same here with Droid Maxx.

This is awesome.
Do you have chance to fix the non working bits?

s_u_n said:
This is awesome.
Do you have chance to fix the non working bits?
Click to expand...
Click to collapse
Hi, Were you able to get the rom to boot?

s_u_n said:
This is awesome.
Do you have chance to fix the non working bits?
Click to expand...
Click to collapse
it is working for you?
since i dont have the device is hard to me know if it is really working, and yea maybe the camera can't be fixed easy.
cheers.

SnipeR_TT said:
Hi, Were you able to get the rom to boot?
Click to expand...
Click to collapse
I have not tried.
I was hoping I could try once the non working features are working.

Droid mini XT1030, stuck on the bootloader screen.
Can your team fix this?

from following the moto x (ghost) forums (my maxx is currently a ghost in droid clothing running aokp) twrp 3.1.1 is required iirc, due to some new wrinkle that needs support baked in for N. someone would have to port the unofficial one over in the other forum over to us. i can say though, that running ghost firmware, 3.1.1 works great on our devices.
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
SnipeR_TT said:
Still got my droid mini around. Will do some testing for y'all.
Edit: Can't get this to boot. It's stuck on the BL screen and doesn't even reach the rom's boot screen. Using TWRP 2.8.4.0. Is there an updated one for obake?
Click to expand...
Click to collapse
westhaking said:
Same here with Droid Maxx.
Click to expand...
Click to collapse
TeamMex said:
it is working for you?
since i dont have the device is hard to me know if it is really working, and yea maybe the camera can't be fixed easy.
cheers.
Click to expand...
Click to collapse
don't we need TWRP >2.8.x to boot N? i ran into this issue a few months ago trying to use the ghost version of this rom. if you can come up with a 3.1.1ish build of twrp for my xt1080m, i'll be happy to test both out.
edit: in fact very interested. i've yet to be able to use my jawbone era earpiece via bluetooth without the connection dropping and phone doing a hard reset. probably highlights one of the few differences in the ultra vs x, if i had to wager a guess. if you have more targeted drivers, in fact i will beg you to let me.
edit 2: i'm good at capturing logcats for devs so they don't have to hear me ramble all the time to figure out wtf i am talking about.

Please don't let this thread die. We have now @tom.etc as a capable tester.

Twrp 3.1.1 for GHOST works on Mini, Maxx, and ULtra
s_u_n said:
Please don't let this thread die. We have now @tom.etc as a capable tester.
Click to expand...
Click to collapse
I got a droid mini for free. It was on an old software version, hadn't been touched in years. I unlocked the bootloader with sunshine and then let it take like 7 system updates until it was up to date, then flashed twrp 2.8.4
I had issues flashing the lineage os 13 unofficial for obake https://forum.xda-developers.com/droid-ultra/development/rom-cyanogenmod-13-obake-t3319958, it was stuck on the lineage boot screen. I was trying to use twrp 2.8.4 because that was the latest version I could find for this device.
As mentioned above, it seems that GHOST (Moto X 2013) software does work on the droid Maxx, Ultra, and Mini Family. I flashed 3.1.1 twrp_ghost from https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449 on my droid mini and it works.
When I tried to flash Lineage os 13 though, it would fail to flash, saying the firmware file wasn't made for ghost_verizon since I was using the 3.1.1 twrp from ghost, TWRP is under the impression that I am using a different device.
If you open the rom zip using WinRAR, and you can copy the updater-script located at META-INF/com/google/android/updater-script to your desktop, open the file, change 2 instances of "obakem" to "ghost_verizon", save the file, then with WinRAR still open copy the updater-script back into the zip. I flashed the zip in twrp 3.1.1 after doing this and successfully booted into lineage os 13.
I flashed lineage os 14.1 for ghost from here: https://forum.xda-developers.com/moto-x/development/rom-unofficial-lineageos-14-1-t3667515 on my droid mini using the 3.1.1 ghost twrp and lineage os boots! It has on screen buttons for back, home, and recent apps though, the hardware buttons aren't working. Also, as mentioned over there, the camera does not work.
Anyways, sorry for the long explanation. I tried getting this rom to boot in twrp 3.1.1 by updating the updater-script the same way but it didn't work. So there's some other issue causing this rom not to work. If you want nougat just flash twrp 3.1.1 ghost, and lineage os 14.1 for ghost, that worked for me.

smilesinlife said:
i wana try it but stuck on kitkat 4.4 su-6-7.7 firmware, any way to root in and unlock its bootloader
Click to expand...
Click to collapse
try to unlock bootloader in official way https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a if you get bootloader unlock then install custom recovery https://forum.xda-developers.com/droid-ultra/development/twrp-2-8-4-0-droid-mini-ultra-maxx-t3012851 and then flash su zip http://www.supersu.com/download
---------- Post added at 10:53 AM ---------- Previous post was at 10:49 AM ----------
is led notification works on droid mini?

soaking in florida sun for next 2 weeks, but when i get back home to the snow of NJ, i'll give all of this a go and let you know how it all turns out.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
steven_computer_guy said:
I got a droid mini for free. It was on an old software version, hadn't been touched in years. I unlocked the bootloader with sunshine and then let it take like 7 system updates until it was up to date, then flashed twrp 2.8.4
I had issues flashing the lineage os 13 unofficial for obake https://forum.xda-developers.com/droid-ultra/development/rom-cyanogenmod-13-obake-t3319958, it was stuck on the lineage boot screen. I was trying to use twrp 2.8.4 because that was the latest version I could find for this device.
As mentioned above, it seems that GHOST (Moto X 2013) software does work on the droid Maxx, Ultra, and Mini Family. I flashed 3.1.1 twrp_ghost from https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449 on my droid mini and it works.
When I tried to flash Lineage os 13 though, it would fail to flash, saying the firmware file wasn't made for ghost_verizon since I was using the 3.1.1 twrp from ghost, TWRP is under the impression that I am using a different device.
If you open the rom zip using WinRAR, and you can copy the updater-script located at META-INF/com/google/android/updater-script to your desktop, open the file, change 2 instances of "obakem" to "ghost_verizon", save the file, then with WinRAR still open copy the updater-script back into the zip. I flashed the zip in twrp 3.1.1 after doing this and successfully booted into lineage os 13.
I flashed lineage os 14.1 for ghost from here: https://forum.xda-developers.com/moto-x/development/rom-unofficial-lineageos-14-1-t3667515 on my droid mini using the 3.1.1 ghost twrp and lineage os boots! It has on screen buttons for back, home, and recent apps though, the hardware buttons aren't working. Also, as mentioned over there, the camera does not work.
Anyways, sorry for the long explanation. I tried getting this rom to boot in twrp 3.1.1 by updating the updater-script the same way but it didn't work. So there's some other issue causing this rom not to work. If you want nougat just flash twrp 3.1.1 ghost, and lineage os 14.1 for ghost, that worked for me.
Click to expand...
Click to collapse
since i have my device already reporting itself as ghost and not obake, i should not have to edit anything then. the recovery and rom should just work, no?
fyi, up through MM, the patch offered in this forum for lollipop has worked swimmingly for activating the capacitve buttons on any ghost rom i've tried. then its usually just a matter of disabling the navbar.

tom.etc said:
soaking in florida sun for next 2 weeks, but when i get back home to the snow of NJ, i'll give all of this a go and let you know how it all turns out.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
since i have my device already reporting itself as ghost and not obake, i should not have to edit anything then. the recovery and rom should just work, no?
fyi, up through MM, the patch offered in this forum for lollipop has worked swimmingly for activating the capacitve buttons on any ghost rom i've tried. then its usually just a matter of disabling the navbar.
Click to expand...
Click to collapse
Yes. If you have the twrp 3.1.1 for ghost already installed on a Droid Maxx/ultra/mini, you should be able to flash ghost roms without needing to modify them, then flashing the patch you mentioned which does enable the capacitive buttons.