Related
Update to binary 3.0.2 from within SU.
Update SU to 3.0.6 via market. or download
http://downloads.androidsu.com/superuser/Superuser-3.0.6-efgh-signed.zip and flash
clear the data from SU if your still getting FC's
Credits go to HomerSP for coming up with the fix!!
Edited post #1 because 3.0.6 SU update
I searched for it. Thank's.
Sent from my IDEOS S7 Slim using XDA App
Yeah....it's WAY better to release an add-on fix and make everyone try to figure out how to fix the dev's **** up than it is for the dev to just release a WORKING VERSION!!!!
hp420 said:
Yeah....it's WAY better to release an add-on fix and make everyone try to figure out how to fix the dev's **** up than it is for the dev to just release a WORKING VERSION!!!!
Click to expand...
Click to collapse
Chainsdd is a busy person, and the su issues don't affect everyone. I haven't had a problem with it since 3.0.2. You should be happy that he even works on this at all instead of acting like an ungrateful twit.
Drunk texted from my CM7 Bolt
hp420 said:
Yeah....it's WAY better to release an add-on fix and make everyone try to figure out how to fix the dev's **** up than it is for the dev to just release a WORKING VERSION!!!!
Click to expand...
Click to collapse
Read this:
http://androidsu.com/2011/10/status-update/
ChainsDD is not a team. don't flame him
theraver said:
Read this:
http://androidsu.com/2011/10/status-update/
ChainsDD is not a team. don't flame him
Click to expand...
Click to collapse
Exactly, don't flame a developer for creating an awesome application that contains 1 bug in an update.
I also had the bug, I updated to 3.0.1, but the update failed, and I lost my root access. But c'mon, just download the su-update zip file, flash it, reboot and you're done.
As the developer said, it's impossible to test about 700 devices every single update. SuperUser is the most important application for rooted users if you think about it, don't flame the developer for making 1 fault.
thanks for the fix, glad to get rid of the SU binary outdated msg.
Yesterday i saw CyanogenMod Installer app for android...
It is quite helpful for those who are flashing roms first time on their device after rooting...
This app also tells them whether a Cyanogen rom is available for their device or not...
I m currently working on paranoid if this feature is added to PA source itself then it will cause pain for other roms...
This will be a arsenal for paranoidsss...
Have a look at CM installer
https://play.google.com/store/apps/details?id=org.cyanogenmod.oneclick
I m not promoting CM but giving u all idea atleast...
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Installer will be great for newbies...
theroadrunner said:
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Click to expand...
Click to collapse
if a rom offers an installer app then it will attract new users who havent flashed custom roms yet...this what i meant..
Custom ROM Installer
I think that an Automatic Installer for the first flashers would be indeed "comforting" Because I've started to flash custom roms recently and my first one was a pain, not because of the steps....The steps for installing the recovery tool and all are pretty easy and all. But we have the feeling we are going to brick the device at the first flash! hehe Maybe an automatic installer that detects your device model would be kinda safe for unexperienced users...
But nowadays I find it nice to manually flash roms, keep backups, etc...
Oh well...not a bad idea at all in my opinion ;}
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
moneyolo said:
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
Click to expand...
Click to collapse
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
stephendt0 said:
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Click to expand...
Click to collapse
Yeah, that was my fault aswell.
Now it will help..
Entropy512 said:
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
Click to expand...
Click to collapse
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
anurag.dev1512 said:
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
Click to expand...
Click to collapse
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
wait i will check ...
Mazda said:
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
Click to expand...
Click to collapse
thnxxx for notifying me... i havent checked the source but i will check now...
nice!
I cam across this thread while searching for the same and wondered if that could be possible in our yureka devices or not.
I even came to know that to do so you need the debug-able kernel that has already been provided for our devices by Cyanogen, and the su binaries from the CM11. Since the version of CM on our devices is not pre-rooted, can anyone please port the actual su binaries from a rooted CM11 and make it a flashable zip ??
I know this is just too much to ask, but I am not a developer and I have no idea how you guys port a feature from one device onto another. But it could be something worth working for. If anyone's taking it do let me know, you have my support and I am pretty sure there will be others like me who will be curious enough to enable and use that in-built Koush's superuser.
hkm93 said:
I cam across this thread while searching for the same and wondered if that could be possible in our yureka devices or not.
I even came to know that to do so you need the debug-able kernel that has already been provided for our devices by Cyanogen, and the su binaries from the CM11. Since the version of CM on our devices is not pre-rooted, can anyone please port the actual su binaries from a rooted CM11 and make it a flashable zip ??
I know this is just too much to ask, but I am not a developer and I have no idea how you guys port a feature from one device onto another. But it could be something worth working for. If anyone's taking it do let me know, you have my support and I am pretty sure there will be others like me who will be curious enough to enable and use that in-built Koush's superuser.
Click to expand...
Click to collapse
The main issue is that cm no longer uses that super user and Koush and CM have parted ways on less the good terms. Cm has even started using a completely different SU setup.
zelendel said:
The main issue is that cm no longer uses that super user and Koush and CM have parted ways on less the good terms. Cm has even started using a completely different SU setup.
Click to expand...
Click to collapse
Sorry, I beg to differ slightly.
It is true that the Superuser made by Koush is now deprecated & no longer be used in current builds of CM. But this thread contains the updated su binary which is currently used in CM. CM 11S (which isn't community driven but commercial) contains regular settings for Superuser policies but lacks of the compatible su binary which can be inserted and be used easily.
:cyclops:
zelendel said:
The main issue is that cm no longer uses that super user and Koush and CM have parted ways on less the good terms. Cm has even started using a completely different SU setup.
Click to expand...
Click to collapse
It's sad to herar that, I always like the sleek and simple inteface plus functionality that it provided, anyways thanks for the update.
Titokhan said:
Sorry, I beg to differ slightly.
It is true that the Superuser made by Koush is now deprecated & no longer be used in current builds of CM. But this thread contains the updated su binary which is currently used in CM. CM 11S (which isn't community driven but commercial) contains regular settings for Superuser policies but lacks of the compatible su binary which can be inserted and be used easily.
:cyclops:
Click to expand...
Click to collapse
So can I use that to flash the binaries to enable the default su in my settings menu ?? I posted it here coz I know there can be compatibility issues, just wanted to make sure that whether I can use it (the su.zip in that thread) to update my binaries in my yureka ?
Titokhan said:
Sorry, I beg to differ slightly.
It is true that the Superuser made by Koush is now deprecated & no longer be used in current builds of CM. But this thread contains the updated su binary which is currently used in CM. CM 11S (which isn't community driven but commercial) contains regular settings for Superuser policies but lacks of the compatible su binary which can be inserted and be used easily.
:cyclops:
Click to expand...
Click to collapse
Yes but cm11s has SU already built into it with that version of the OS. I would look at the source code diff between the 2 before you jump the gun. cm11 and cm11s are very different in the base coding.
zelendel said:
Yes but cm11s has SU already built into it with that version of the OS. I would look at the source code diff between the 2 before you jump the gun. cm11 and cm11s are very different in the base coding.
Click to expand...
Click to collapse
Well, I have already tested my hypothesis on YU Yureka before posting :good:
@hkm93
As you can see, it can be used. But I prefer @Chainfire's SuperSU for multiple extra facilities.
Titokhan said:
Well, I have already tested my hypothesis on YU Yureka before posting :good:
@hkm93
As you can see, it can be used. But I prefer @Chainfire's SuperSU for multiple extra facilities.
Click to expand...
Click to collapse
Awesome I just love the way it is, gave SuperSU a try when I updated it's binaries to root the device, it is good, and has more features, but you know, personal preferences
Anyways thanks a lot buddy :good:
Man where is the process to enable inbuilt superuser. And afterwards wt I need to do
hkm93 said:
I cam across this thread while searching for the same and wondered if that could be possible in our yureka devices or not.
I even came to know that to do so you need the debug-able kernel that has already been provided for our devices by Cyanogen, and the su binaries from the CM11. Since the version of CM on our devices is not pre-rooted, can anyone please port the actual su binaries from a rooted CM11 and make it a flashable zip ??
I know this is just too much to ask, but I am not a developer and I have no idea how you guys port a feature from one device onto another. But it could be something worth working for. If anyone's taking it do let me know, you have my support and I am pretty sure there will be others like me who will be curious enough to enable and use that in-built Koush's superuser.
Click to expand...
Click to collapse
No matter what.. Even if there is an option there are no SU binaries and therefore even if you enable it it won't work..
YOU WILL RECEIVE OTA UPDATES EVEN AFTER ROOTING IF YOU MANTAIN THE STOCK RECOVERY I.E. USE THE CUSTOM RECOVERY TEMPORARILY AND LOCK THE BOOTLOADER AGAIN
Don't , Just Don't !
arjunsingh1000 said:
No matter what.. Even if there is an option there are no SU binaries and therefore even if you enable it it won't work..
YOU WILL RECEIVE OTA UPDATES EVEN AFTER ROOTING IF YOU MANTAIN (maintain* not mantain) THE STOCK RECOVERY I.E. USE THE CUSTOM RECOVERY TEMPORARILY AND LOCK THE BOOTLOADER AGAIN
Click to expand...
Click to collapse
I have no idea why you even bothered to reply, it made no sense, because it's already confirmed that it works, I tried it months ago and it works flawlessly, n I don't feel the need to convince a kid for the same. And I never asked anything about OTA, didn't even mention Bootloader or custom recovery in my post, what was all that for ??
Seriously, did you even read the thread before replying ??
well , I have RRO layers working on stock android M for those who are interested.
you need to be rooted, with a custom kernel that enables write permissions in /system partition
like hells-core one or lean kernel.
The funny fact is that google apparently made a system image for M that is so big that fill up our nexus 6 /system partition almost full , leaving only 16 mb of free space there. Impressive.
Even if you have write access , apps that have to write something in /system fails for lack of drive space.
this includes for example adaway, betterbatterystats, busybox on rails and RRO Layers.
So the trick here is to delete some big gapps that you don't plan to use to make room for other stuff.
I used TiBU for that and worked perfectly , now I'm running with busybox and inversion UI for Layers
and all is fine
Hope this helps, cheers
thanks to @Amos91 for spotting the space issue in the lean kernel thread
mangusZen said:
well , I have RRO layers working on stock android M for those who are interested.
you need to be rooted, with a custom kernel that enables write permissions in /system partition
like hells-core one or lean kernel.
The funny fact is that google apparently made a system image for M that is so big that fill up our nexus 6 /system partition almost full , leaving only 16 mb of free space there. Impressive.
Even if you have write access , apps that have to write something in /system fails for lack of drive space.
this includes for example adaway, betterbatterystats, busybox on rails and RRO Layers.
So the trick here is to delete some big gapps that you don't plan to use to make room for other stuff.
I used TiBU for that and worked perfectly , now I'm running with busybox and inversion UI for Layers
and all is fine
Hope this helps, cheers
thanks to @Amos91 for spotting the space issue in the lean kernel thread
Click to expand...
Click to collapse
Or you can run the latest xtrasmooth custom base on latest ota M Rom which is debloated and have everything working.
yellowman82 said:
Or you can run the latest xtrasmooth custom base on latest ota M Rom which is debloated and have everything working.
Click to expand...
Click to collapse
so, ok to just flash xtra smooth, and then hells kernel?
havent tried xtra smooth yet, but I see its really debloated..
thanks man
yellowman82 said:
Or you can run the latest xtrasmooth custom base on latest ota M Rom which is debloated and have everything working.
Click to expand...
Click to collapse
Some people are reporting some things that need to be worked on over in the ROM thread. Plus, I don't want to dirtyflash my userdata over to that ROM. It wont work, lots of people tired and get errors to the moon and back.
It does look like a nice rom though.
yellowman82 said:
Or you can run the latest xtrasmooth custom base on latest ota M Rom which is debloated and have everything working.
Click to expand...
Click to collapse
Sure, but I just finished to setup this new stock, dont have time for now to clean flash again [emoji14]
dirtyflashing anything always opens you up to problems, so its rarely the roms fault, and more often, the users fault..
wase4711 said:
dirtyflashing anything always opens you up to problems, so its rarely the roms fault, and more often, the users fault..
Click to expand...
Click to collapse
Yeah I know, I wasn't blaming the ROM for dirty flashing errors. Just that it's something I don't want to deal with haha.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
mangusZen said:
well , I have RRO layers working on stock android M for those who are interested.
you need to be rooted, with a custom kernel that enables write permissions in /system partition
like hells-core one or lean kernel.
The funny fact is that google apparently made a system image for M that is so big that fill up our nexus 6 /system partition almost full , leaving only 16 mb of free space there. Impressive.
Even if you have write access , apps that have to write something in /system fails for lack of drive space.
this includes for example adaway, betterbatterystats, busybox on rails and RRO Layers.
So the trick here is to delete some big gapps that you don't plan to use to make room for other stuff.
I used TiBU for that and worked perfectly , now I'm running with busybox and inversion UI for Layers
and all is fine
Hope this helps, cheers
thanks to @Amos91 for spotting the space issue in the lean kernel thread
Click to expand...
Click to collapse
I figured this out about the same time you did. I knew it had to be something so trivial.
Alas though, I have my theme set up to match my Pipboy homescreen now so I'm happy.
Peylix said:
Some people are reporting some things that need to be worked on over in the ROM thread. Plus, I don't want to dirtyflash my userdata over to that ROM. It wont work, lots of people tired and get errors to the moon and back.
It does look like a nice rom though.
Click to expand...
Click to collapse
There is nothing wrong with the rom. The dirty flash is for users, like myself, who do not want to go through the process of rooting android M ourselves. I personally did not mind dirty flashing to gain root. Soon as I flashed, booted and made sure I had root, I went back to twrp and did a complete wipe and clean flash. Alternatively, you can wipe the system and flash the rom (it is a risk to take) OR backup, wipe and flash the rom....dirty flash is just to get root.
Now if you already gain root, just flash it like any rom you will There is no bug in the rom given it is basically stock, debloated and deodex. There is only so much that can go wrong with it...lol
P.S not saying this to convince you to flash, more so for those reading this thread. Would hate for them to gain false assumptions.
mgbotoe said:
There is nothing wrong with the rom. The dirty flash is for users, like myself, who do not want to go through the process of rooting android M ourselves. I personally did not mind dirty flashing to gain root. Soon as I flashed, booted and made sure I had root, I went back to twrp and did a complete wipe and clean flash. Alternatively, you can wipe the system and flash the rom (it is a risk to take) OR backup, wipe and flash the rom....dirty flash is just to get root.
Now if you already gain root, just flash it like any rom you will There is no bug in the rom given it is basically stock, debloated and deodex. There is only so much that can go wrong with it...lol
P.S not saying this to convince you to flash, more so for those reading this thread. Would hate for them to gain false assumptions.
Click to expand...
Click to collapse
I don't want to turn people away from it either. Like I said, it looks like a great ROM. I just remember seeing a few posts mentioning that there were a few bugs, can't remember what for. I don't know however if it was user created bugs or ROM, at the time though it looked more for the later.
As for dirty flashing. I've been guilty of doing it a lot over the years. Sometimes problem free, others not so. All I wanted was a one time install with no errors. I had already manually flashed to 6.0 through fastboot to keep my userdata. I didn't feel like flashing over another ROM ontop and then have the possibility of errors come up because of my dirty flash of userdata to go with it. (It's just personal I guess haha)
I should have rephrased my post better to regard it more of me being lazy.
Hey man thanks for pointing out the system size. I was -_- trying to figure out why my layers wouldnt apply... TiB removed sheets. because..... worked like a champ
wase4711 said:
dirtyflashing anything always opens you up to problems, so its rarely the roms fault, and more often, the users fault..
Click to expand...
Click to collapse
not true, your always. i always dirty flash, and im typically the one without problems, ever. now some do have issues, but its not usually frim the dirty flash, but it is usually user related(where i agree with you).
simms22 said:
not true, your always. i always dirty flash, and im typically the one without problems, ever. now some do have issues, but its not usually frim the dirty flash, but it is usually user related(where i agree with you).
Click to expand...
Click to collapse
I've had the same experience throughout the years as you.
Sorry, this thread is now closed.
I would suggest you to move this thread to the General Disucssion section
Moved.
well I think I found a bug so twrp thinks there is no os installed and the browser doesnt work and when you try to flash gapps for 7.1 it doesnt work how do we fix this
williambright80 said:
well I think I found a bug so twrp thinks there is no os installed and the browser doesnt work and when you try to flash gapps for 7.1 it doesnt work how do we fix this
Click to expand...
Click to collapse
For which ROM u talking about?? Aosp espressos'
Kunal Gautam said:
For which ROM u talking about?? Aosp espressos'
Click to expand...
Click to collapse
yes
TWRP :-OK it isn't that severe to be called a bug
GApps:- I know its a problem with the ROM that it doesn't deal with opengapps but still you can try PA GApps they are working fine with the ROM.
Thanks
Kunal Gautam said:
TWRP :-OK it isn't that severe to be called a bug
GApps:- I know its a problem with the ROM that it doesn't deal with opengapps but still you can try PA GApps they are working fine with the ROM.
Thanks
Click to expand...
Click to collapse
which gapps
link me to 7.1 ROM you promised, ty.
Boscep said:
link me to 7.1 ROM you promised, ty.
Click to expand...
Click to collapse
here is the link to 7.1 https://builds.unlegacy-android.org/aosp-7.1/espresso/ua_espresso-7.1.1-20170227.zip
Is this for pad 2 gt-p5100
JPSimon said:
Is this for pad 2 gt-p5100
Click to expand...
Click to collapse
Yes but to avoid confusion please call it by galaxy tab 2 10.1
hello @CCD
how are you?
comeback pls
tab 2 needs more dev, ty.
UPDATE 2.0
Builds are almost ready CM 14.1 once my exams are completed will start to test them.... Dont know why but still camera bug carry on almost no lags..... + CyanogenMod Features....
JPSimon said:
Is this for pad 2 gt-p5100
Click to expand...
Click to collapse
It could be but right now i haven't updated my device tree
For P3100's right now but i will do it soon but it could be faster if you could help me updating
williambright80 said:
which gapps
Click to expand...
Click to collapse
Sorry my mistake PA Gapps are now discontinued instead of them you could download dynamic gapps
Link-https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Kunal Gautam said:
Introduction
At the end of 2016 I started to seek nougats for Tab 2, found AOSP by Ziyan and Android - Andi
flashed it, examined it, Discontinued it......
Here we gonna discuss it.
What is the need?
Tab 2 was released in 2012 and in mid 2014 was discontinued by Samsung thus resulted to get this to be called OLD but in my eyes its still new with great potential and great reliability so I just want to keep this device alive till 2019. So that's the reason....
CURRENT STATE
Nougat development is doing well and with the help of you I can or all devs can make it better.....
So just because of this learned porting and started porting, successfully ported 4 out 5 ROMs will upload them all......
DEVELOPING CIRCLE
Roms that are being supported by me are :-
AOSP
Lineage OS
AICP
Resurrection Remix
Thanks To @[email protected]
SlimKat Roms
CyanogenMod
LineageOS
You
Me of course
Click to expand...
Click to collapse
So hey, i'm nee to this forum and rooting in general but i will glad if some of you could help me out of this, here's the deal: i saw that AOSP roms are the best for performance (right?) and i also want the lastet version of android so that rom fit perfectly my needs, where i can download it? And is compatibile with my tab 2 10.1 WiFi only? Also where the hell is the guide to root that Device, i saw it once and i never found it back... (yeah i'm probably stupid)
LordReaperIV said:
So hey, i'm nee to this forum and rooting in general but i will glad if some of you could help me out of this, here's the deal: i saw that AOSP roms are the best for performance (right?) and i also want the lastet version of android so that rom fit perfectly my needs, where i can download it? And is compatibile with my tab 2 10.1 WiFi only? Also where the hell is the guide to root that Device, i saw it once and i never found it back... (yeah i'm probably stupid)
Click to expand...
Click to collapse
No need for guide
Steps
1. Download KingRoot.
2. Install it.
3. Root your device with it.
4. Enjoy
TO INSTALL CUSTOM RECOVERY TO INSTALL CUSTOM ROMS
1. Download official TWRP app from the Play Store.
2. Install recovery using the information on the screen.
INSTALL THE MODDED RECOVERY PLZ IF YOU DONT WANT TO GET YOU DEVICE BRICKED
1. Go to google search andi github
2. Open it
3. Go to the recovery section and then in TWRP download the common recovery and install the downloaded recovery using the current TWRP recovery
And AOSP are good but actually for Tab 2 it is really unstable right now. But if you really want to install it
Just go in the Tab 2 Development section
The AOSP must on top there will be links to the website
Just go to directory when you visit downloading website
AOSP 7.1/espresso/Download the latest one
And just copy to you device
Then go to the recovery (Power + Volume Up)
Then go into wipe/anvanced
Select
1. DALVIK
2. CACHE
3. SYSTEM
4. DATA
Then wipe
Then install the Rom
TADA Done than just reboot.
Kunal Gautam said:
No need for guide
Steps
1. Download KingRoot.
2. Install it.
3. Root your device with it.
4. Enjoy
TO INSTALL CUSTOM RECOVERY TO INSTALL CUSTOM ROMS
1. Download official TWRP app from the Play Store.
2. Install recovery using the information on the screen.
INSTALL THE MODDED RECOVERY PLZ IF YOU DONT WANT TO GET YOU DEVICE BRICKED
1. Go to google search andi github
2. Open it
3. Go to the recovery section and then in TWRP download the common recovery and install the downloaded recovery using the current TWRP recovery
And AOSP are good but actually for Tab 2 it is really unstable right now. But if you really want to install it
Just go in the Tab 2 Development section
The AOSP must on top there will be links to the website
Just go to directory when you visit downloading website
AOSP 7.1/espresso/Download the latest one
And just copy to you device
Then go to the recovery (Power + Volume Up)
Then go into wipe/anvanced
Select
1. DALVIK
2. CACHE
3. SYSTEM
4. DATA
Then wipe
Then install the Rom
TADA Done than just reboot.
Click to expand...
Click to collapse
Awesome dude, thanks for the tips, i'll wait that my tabet charge will be over 80% (just for safety) and the i'll root it. I downloaded both ".tar.md5" and ".zip" file but when i go to choose the file with TWRP in the directory that i put them, the app explorer don't see them... -> update, the TWRP app let me see only the 2..8.5.0 version of recovery, while the site on github start from 3.x.x.x. also i tried to flash the img files extracted from the 3.x.x.x. recoveries and it told me "flash failed".
Also my Galaxy Tab 2 just crashed while rooting with Kingroot (it was trying the could method) -> EDIT: i reset it and when i open the kingroot app it start from where it left , it was a "crash" because the stock rom have not the reboot function?
BTW i thought, you said that galaxy tab 2 is unstable, but i remember that the first stock rom was very well optimized with no lag, then i updated it via samsung and then it come to lag and IT IS VERY SLOW. so you mean that installing a custom rom will not solve the problem?
[b]"need alpha testers for cm 14.1"[/b]
Alpha testers wanted for CM 14.1
1st Build releasing today.. Stay Tuned!!!