Kyocera -C6745 Help - Android General

After viewing many threads on this phone I've come to realize that it is almost unrootable..
---------------------------------------------------------------------
I myself am unable to root the Kyocera Hydro Air
(At&t go phone)
But I do know how to enter recovery, and many do not.
While my method is stupidly weird, it is very easy.
What you will need is kingroot and Busybox by jrummy
Kingroot: Online, Has to be 4.9.6 I believe it should be there if you search kingroot apk
Busybox: Google Play store
Ok, I'm sure you know what kingroot is and know it will not work, ik it does not root the phone, its not for that technically.
First enable Dev mode, then enable USB debugging and disable Verify apps over USB.
Then Run kingroot once or twice, (it is supposed to fail both times)
However, this gives you a broken root,
Go ahead and install Busybox by jrummy
And run the Recovery script not as root (If it even gives you the options) If its done right, it will boot into recovery. you can hard reset and maybe even boot from a zip. I am a noob at this and found it by mistake xD, I hope it helps in some way, and I hope it works for you.
(If this does not work, run kingroot again, or try resetting your phone and trying again)

Additional stuff
If this did not work for you and you need help, pm me or reply asking for help!

I got my son a Hydra and the battery life is horrible. He pretty much gave up on using it. Any advice?
Sent from my SM-G900T using Tapatalk

I have not had to much trouble with the battery myself, the hydro air seems to have a decent one for me, all I can suggest is making sure all the apps are closed, and maybe resetting it and reinstalling apps one by one to see if maybe some of the apps are draining the battery to fast. Maybe even consider disabling the stock apps that you don't need.

I installed greenify to close all apps but battery drain is severe. Phone can be left at 100% at 11pm and be dead by 7am.
Sent from my SM-G900T using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 08:36 AM ----------
Hydra wave
Sent from my SM-G900T using Tapatalk

passport619 said:
I installed greenify to close all apps but battery drain is severe. Phone can be left at 100% at 11pm and be dead by 7am.
Sent from my SM-G900T using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 08:36 AM ----------
Hydra wave
Click to expand...
Click to collapse
I'll look into the Hydro wave, I might just buy one and mess with it myself, hopefully I can find something to help out

I'm going to download an app called Juice Defender to test if it makes a difference, if it does I'll let ya know, maybe it will help you

Also, settings like brightness and turning off rotation and location will help, you probably already know that, but turning off location helps a lot, it would also be nice to know what Android version is on it

I did a Google search and found an article from 2013 stating that juice defender was a recommended app for the Hydro back then.
Sent from my SM-G900T using Tapatalk

Yea same here

Ok, there is no real good solution to that problem sorry.. best I can do is recommend not to get a Samsung galaxy s7, explodes every time

Is there a way to hard reset my hydro air without getting into the phone? It is password protected and will not let me back into it. and plugging it into the computer is set to charge only, so i cant see any of the files from my pc.

KyoceraHelp said:
After viewing many threads on this phone I've come to realize that it is almost unrootable..
---------------------------------------------------------------------
I myself am unable to root the Kyocera Hydro Air
(At&t go phone)
But I do know how to enter recovery, and many do not.
While my method is stupidly weird, it is very easy.
What you will need is kingroot and Busybox by jrummy
Kingroot: Online, Has to be 4.9.6 I believe it should be there if you search kingroot apk
Busybox: Google Play store
Ok, I'm sure you know what kingroot is and know it will not work, ik it does not root the phone, its not for that technically.
First enable Dev mode, then enable USB debugging and disable Verify apps over USB.
Then Run kingroot once or twice, (it is supposed to fail both times)
However, this gives you a broken root,
Go ahead and install Busybox by jrummy
And run the Recovery script not as root (If it even gives you the options) If its done right, it will boot into recovery. you can hard reset and maybe even boot from a zip. I am a noob at this and found it by mistake xD, I hope it helps in some way, and I hope it works for you.
(If this does not work, run kingroot again, or try resetting your phone and trying again)
Click to expand...
Click to collapse
Hello, please I have a kyocera hydro air I got from ebay but the phone is screen lock, with a password, I can't access the phone, can't get to the menu. Any one with useful information on how to unlock or bypass the lock screen.

Related

Rooting problem - Solved!

I used the Moboboro and SuperOneClick method. Everything went smoothly, SOC went through its routine and told me my device was now rooted. The superuser app appeared in my drawer and updated itself. I figured everything was good. Wrong. Rootchecker and busybox are both telling me the device (UG802) is not actually rooted. Any ideas what I can do?
Thanks
Unfortunately I have exactly the same problem when I attempt to root ug 802. Will appreciate any help!
I'm going thru the same thing. I guess there is a Chinese tool that works but I'm not up for trying.
http://forum.xda-developers.com/showthread.php?t=2139454
I read the ug802 comes prerooted ?? I have been able to load apks thru astro without issue but also got non rooted message using busybox.
Root doesn't appear to matter as there isn't a ROM based off the JB firmware it comes with AFAIK
---------- Post added at 03:50 AM ---------- Previous post was at 03:45 AM ----------
I just stumbled across this and might give it a try tonite
You may have to register to get links
http://www.arctablet.com/blog/forum...mini-pc-rooted-firmware-from-20121112-update/
koii said:
Unfortunately I have exactly the same problem when I attempt to root ug 802. Will appreciate any help!
Click to expand...
Click to collapse
Meaby this is something for yah: freaktab.com/showthread.php?2632-UG802-2dark4u-Finless-custom-ROM-version-1-7-true-1080-and-overclock-AND-best-performance-ever
pulsaris said:
Meaby this is something for yah: freaktab.com/showthread.php?2632-UG802-2dark4u-Finless-custom-ROM-version-1-7-true-1080-and-overclock-AND-best-performance-ever
Click to expand...
Click to collapse
Depends on which UG802 version you have. On that forum there's a warning that the ROM is not for use on the latest version of the UG802, it kills the wi-fi.
Getting my ug802 into recovery is about impossible. Mine has no reset button and I'm not up for opening the case. Somebody has to have a way to do this easy.
pwrshft99 said:
Getting my ug802 into recovery is about impossible. Mine has no reset button and I'm not up for opening the case. Somebody has to have a way to do this easy.
Click to expand...
Click to collapse
FWIW, opening the case is a piece of cake. It's just held on with tabs. Slide a flat head screwdriver above the HDMI port and gently work it back and forth. It will crack open and then you can just work your way around. Why do you need to open the case?
According to what I've read you can run a jumper wire across to pin terminals and force the ug802 into recovery mode. This seems to be what those that have tried and failed to root have resorted to to get their device out of boot loop.
I've modded a few androids but this one is tough
pwrshft99 said:
According to what I've read you can run a jumper wire across to pin terminals and force the ug802 into recovery mode. This seems to be what those that have tried and failed to root have resorted to to get their device out of boot loop.
I've modded a few androids but this one is tough
Click to expand...
Click to collapse
Ok, finally found a method that worked for me. Have to wait for next post to post a link....
http://www.armtvtech.com/armtvtechforum/viewtopic.php?t=28
It is for the MK808, but it worked for me. You need an account to see the download link for the file, but you can just google the file name and find the download link that way.
Thanks for the update... I'm going to give this a shot tonite. I'm thinking I don't have the right drivers or something
---------- Post added at 06:53 AM ---------- Previous post was at 06:01 AM ----------
OK this worked for as well!! Big thank you!!
I'd like to add that I got stuck until I realized that after each reboot I had to back into settings and under ubs click connect to PC. Once I did that it rooted right away. Now we just need some new ROMs to try!!
Hi, im using this rom and just need to install. Already came with SU. No need to root
Since I use that one I never root again
Install an uninstaller root apk, and desinstall all apk you dont need it

SM-P905V Root. US Verizon

Updated to provide those things I have used to get to where I am. Original post is below the break.
I suppose I need to also add the normal blah, blah, blah. Do not attempt these things unless you are willing to brick your expensive tablet. Your choice to follow my recommendations or anyone else from this point forwards, are all on you.
I have a Verizon Samsung Galaxy Note 12.2 SM-P905V. Here is a screen shot showing my build info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have returned to stock per http://http://www.mediafire.com/download/dx...MULTI_CERT.zip Posted on kest874 thread http://forum.xda-developers.com/showthread.php?t=2795630. I have always taken the available carriers updates before rooting.
Next use Towelroot to allow root.
Towelroot is easily found if you search for it with any search engine. Towelroot is no longer supported by the dev who created it as he has moved on to bigger and better things.
I have never had to enter any code when using towelroot. I read where people need to input various character strings but not I. I can't explain any reasons why that is so.
Towelroot works great to root but! Capitalize the BUT! Do not allow KNOX to be disabled when Towelroot roots you and pops up a message about KNOX. That is what caused my hotbooting issue.
Download SuperSU from the play store and install.
Bingo, bango, bongo. Your rooted.
Now, if only I could get TWRP to ODIN without fail. Current version being attempted is 2.8.0.0.
------------------------------------------------------ Break ------------------------------------------------------------
I would like the tablet setup to be stable with root and a recovery. I am rooted now, towelroot, but there isn't a recovery available yet. I can wait for the recovery to become available but getting a stable root working is my number one issue.
Yes I am rooted but it isn't stable. My tablet reboots on a whim. Well actually I can continually duplicate the reboot. The reboot occurs exactly after I pull down the notification window after resuming the tablet from a timeout. I can tinker with anything I want on the tablet for as long as I want but if I let the screen timeout, poof. The tablet will suicide reboot exactly after screen wake and a notification window pull down.
With all that said, I odin'd back to new state last weekend. I let the tablet take all updates and I reinstalled all nonroot requiring apps from the store. I got a solid 5-6 days without any root on the tablet and not one single reboot.
Today I installed root through towelroot and I installed supersu. I specifically set my screen timeout to 30 seconds and waited 30 seconds to test the situation. Yuppers, after I pulled the notification window down it rebooted. I should add the tablet will suicide reboot also after opening a program and selecting something else, all after powering back up after a screen timeout. I continue to use the notification pull down as the example because it's stock and very, very easy to duplicate.
And it's not a normal reboot. It's like a partial reboot. What I witness the screen show, during a suicide reboot, is the Samsung logo with the spinning colors CCW and then the red Verizon splash screen. The boot completely bypasses the beginning boot screen that is individualized for the model and has the powered by android quip.
Does anyone have any ideas how to troubleshoot this further? TWRP doesn't have a recovery yet for this Verizon variant so any of that stuff is out of the question for now. I did install an ADB package on my Win7 machine and I'm able to list the device.
Best Regards
Shon
Sounds similar to the bug with notification shade while using chromecast when the volume and brightness sliders are on in the notification panel. If yours are enabled try turning them off. Probably won't help but worth a shot.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
Sounds similar to the bug with notification shade while using chromecast when the volume and brightness sliders are on in the notification panel. If yours are enabled try turning them off. Probably won't help but worth a shot.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Heck it's worth investigating. I investigated. No change. Oh well, thanks for the suggestion though. One never knows how simple the issue might be.
Rename?
Are my difficulties possibly due to both TWRP and CF auto-root files named as viennaltexx vs viennaltevzw? Android system info program shows my device as viennaltevzw.
BTW I wiped again to try CF auto-root through odin with a fresh install. All still fails in odin during the nand write start. Same as TWRP.
Just wondering if the problem could be as simple as renaming the files.
Hello? *tap, *tap, *tap.
*blows into microphone.
Testing, testing, one. Two. Three.
Is this thing on?
LOL.
Didn't want to just do a simple bump.
Based on the lack of response I assume you're the only 905v user experiencing this so it leads me to suspect a certain software installed that is causing it, perhaps one that pushes a persistent notification. I don't know. The other thought is to go into developer options and tinker with turning off animations or forcing gpu rendering or disabling hardware overlays.
Sent from my SM-P900 using Tapatalk
Perfect. Thank you muzz. I will report back.
I have a 905V, rooted and tons of Xposed applets installed, don't have the issue.
Yea I have to have something strange going on. Also the fact that I can't load TWRP or CF-auto root because I fail at the nand write start. I know my nand isn't corrupt because I can odin the base image, but one problem at a time.
td - yes, Xposed. That is what I want to get to, but I need to get through this rebooting issue first.
Thanks guys
Someone has twrp?
I have P905v (verizon) and only root via towel root method, which worked fine. I too have a bunch of xposed modules and they work fine.
If anyone had twrp with the p905v, can you tell me where you got it from?
Sent from my SM-P905V using XDA Free mobile app
Gonkulor said:
I have a Verizon Samsung Galaxy Note 12.2 SM-P905V. Here is a screen shot showing my build info.
View attachment 2890423
I would like the tablet setup to be stable with root and a recovery. I am rooted now, towelroot, but there isn't a recovery available yet. I can wait for the recovery to become available but getting a stable root working is my number one issue.
Yes I am rooted but it isn't stable. My tablet reboots on a whim. Well actually I can continually duplicate the reboot. The reboot occurs exactly after I pull down the notification window after resuming the tablet from a timeout. I can tinker with anything I want on the tablet for as long as I want but if I let the screen timeout, poof. The tablet will suicide reboot exactly after screen wake and a notification window pull down.
With all that said, I odin'd back to new state last weekend. I let the tablet take all updates and I reinstalled all nonroot requiring apps from the store. I got a solid 5-6 days without any root on the tablet and not one single reboot.
Today I installed root through towelroot and I installed supersu. I specifically set my screen timeout to 30 seconds and waited 30 seconds to test the situation. Yuppers, after I pulled the notification window down it rebooted. I should add the tablet will suicide reboot also after opening a program and selecting something else, all after powering back up after a screen timeout. I continue to use the notification pull down as the example because it's stock and very, very easy to duplicate.
And it's not a normal reboot. It's like a partial reboot. What I witness the screen show, during a suicide reboot, is the Samsung logo with the spinning colors CCW and then the red Verizon splash screen. The boot completely bypasses the beginning boot screen that is individualized for the model and has the powered by android quip.
Does anyone have any ideas how to troubleshoot this further? TWRP doesn't have a recovery yet for this Verizon variant so any of that stuff is out of the question for now. I did install an ADB package on my Win7 machine and I'm able to list the device.
Best Regards
Shon
Click to expand...
Click to collapse
OK so I posted the following message in another forum because I couldn't find this one again. Someone kindly provided me with the link back here so I wanted to post this again, but here. Please advise if any others have this issue or have a shot at a solution.
"I rooted with a towel root and downloaded from the link provided in the first post. I clicked the "make it ra1n" button and received a message stating you are now rooted, please enjoy. I Installed SU (pro version) by chainsfire from playstore, updated binary using "normal" method and used root checker. It confirmed root access and then it was on to Titanium Backup Pro.
Here is my main issue though. Almost immediately after rooting with this method via the provided link, my P905V started Hot Rebooting itself almost every time i attempt to wake it. Flashed back to stock and started all over. Same thing, clicked "make it ra1n" once and received confirmation of root, installed SU again, did root checker and it confirmed root. It again started hot rebooting upon wake up. It did not do it once on the original firmware, nor when i reflashed before rooting with towel root. I noticed someone else had this issue in another thread but received minimal feedback and nobody else with this issue.
My question, is anyone else having this issue? Anyone know where i should start to determine the cause here? I do not have enough posts to post in the development forums even though i have been a member for some time. I am very familiar with root and the Galaxy Note product line, but I am stumped. I have solved all other issues by reading through posts and finding solutions. This is the first time I am totally lost. All help or suggestions welcome. Thanks."
aburns7487 said:
Someone has twrp?
I have P905v (verizon) and only root via towel root method, which worked fine. I too have a bunch of xposed modules and they work fine.
If anyone had twrp with the p905v, can you tell me where you got it from?
Sent from my SM-P905V using XDA Free mobile app
Click to expand...
Click to collapse
Well I also get those reboots in my p907a att model.
torreon901 said:
Well I also get those reboots in my p907a att model.
Click to expand...
Click to collapse
After rooting with towelroot?
bbro84 said:
After rooting with towelroot?
Click to expand...
Click to collapse
Had same issue after towel root on AT&T p907a resolved it by factory resetting it then re rooting and leaving Knox active.
cnote74 said:
Had same issue after towel root on AT&T p907a resolved it by factory resetting it then re rooting and leaving Knox active.
Click to expand...
Click to collapse
I did reflash once, i wil give factory reset and not freezing Knox. thanks for the suggestion and I will let you know if it works.
bbro84 said:
I did reflash once, i wil give factory reset and not freezing Knox. thanks for the suggestion and I will let you know if it works.
Click to expand...
Click to collapse
Thanks I will do same thing....
---------- Post added at 05:43 AM ---------- Previous post was at 05:42 AM ----------
bbro84 said:
After rooting with towelroot?
Click to expand...
Click to collapse
Yes... after towelroot
aburns7487 said:
Someone has twrp?
I have P905v (verizon) and only root via towel root method, which worked fine. I too have a bunch of xposed modules and they work fine.
If anyone had twrp with the p905v, can you tell me where you got it from?
Sent from my SM-P905V using XDA Free mobile app
Click to expand...
Click to collapse
Here is the TWRP suggested for the P905V http://forum.xda-developers.com/showpost.php?p=54299636&postcount=280
I'm not having luck getting it to stick via odin. maybe you could have better results.
bbro84 said:
OK so I posted the following message in another forum because I couldn't find this one again. Someone kindly provided me with the link back here so I wanted to post this again, but here. Please advise if any others have this issue or have a shot at a solution.
"I rooted with a towel root and downloaded from the link provided in the first post. I clicked the "make it ra1n" button and received a message stating you are now rooted, please enjoy. I Installed SU (pro version) by chainsfire from playstore, updated binary using "normal" method and used root checker. It confirmed root access and then it was on to Titanium Backup Pro.
Here is my main issue though. Almost immediately after rooting with this method via the provided link, my P905V started Hot Rebooting itself almost every time i attempt to wake it. Flashed back to stock and started all over. Same thing, clicked "make it ra1n" once and received confirmation of root, installed SU again, did root checker and it confirmed root. It again started hot rebooting upon wake up. It did not do it once on the original firmware, nor when i reflashed before rooting with towel root. I noticed someone else had this issue in another thread but received minimal feedback and nobody else with this issue.
My question, is anyone else having this issue? Anyone know where i should start to determine the cause here? I do not have enough posts to post in the development forums even though i have been a member for some time. I am very familiar with root and the Galaxy Note product line, but I am stumped. I have solved all other issues by reading through posts and finding solutions. This is the first time I am totally lost. All help or suggestions welcome. Thanks."
Click to expand...
Click to collapse
That Sir. is exactly my problem too. Not that I am glad to find someone else with the same problem, but maybe we can figure this out.
I just did another wipe. I still haven't installed towelroot yet.
cnote74 said:
Had same issue after towel root on AT&T p907a resolved it by factory resetting it then re rooting and leaving Knox active.
Click to expand...
Click to collapse
I swear I tried this but I have wiped so many times I don't know. I might as well try it too.
Gonkulor said:
I swear I tried this but I have wiped so many times I don't know. I might as well try it too.
Click to expand...
Click to collapse
Can anyone who is having this issue verify if they have knox frozen or uninstalled? Here is why; I opened Titanium Backup, searched for "knox" and found only two of four frozen knox items. I froze the other two knox related items and have not had the hot reboot issue occur sinve. Granted it has only been about 12 hours and I was not using the tablet for several of those hours.
I am hoping others who are having this issue can step in and confirm if they too only froze some of the knox items or if this has nothing to do with knox. If my issue is fixed and not because of the knox stuff, then a solution is useless since I still don't know what caused the issue. Thanks to all for the input.
---------- Post added at 10:10 AM ---------- Previous post was at 10:03 AM ----------
bbro84 said:
Can anyone who is having this issue verify if they have knox frozen or uninstalled? Here is why; I opened Titanium Backup, searched for "knox" and found only two of four frozen knox items. I froze the other two knox related items and have not had the hot reboot issue occur sinve. Granted it has only been about 12 hours and I was not using the tablet for several of those hours.
I am hoping others who are having this issue can step in and confirm if they too only froze some of the knox items or if this has nothing to do with knox. If my issue is fixed and not because of the knox stuff, then a solution is useless since I still don't know what caused the issue. Thanks to all for the input.
Click to expand...
Click to collapse
EDIT: It just hot rebooted so scratch the above idea...back to drawing board.

Galaxy 4 7.0 SM-T230NU Root (vRoot)

After spending 2 days to figure out how I can get root on my newly purchased Galaxy Tab 4 7.0,
I finally got it to work through vRoot.
Here's a detailed instruction from ShinySide.
http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
Now, where I had the problem wasn't what I did. Rather, it was the auto update that Samsung rolled out in August.
I tried doing through vRoot like, 50 times, and got the same result over and over.
Then I read ShinySide's post saying the August update interferes with vRoot so I had to flash my tablet with older firmware.
Lucky for me, ShinySide also has this available on this forum:
http://forum.xda-developers.com/showthread.php?t=2778374
I did it with NE2, and BOOM. VRoot rooted my phone like a charm.
So, those of you who are having trouble with vRoot (probably seeing X mark instead of a check mark at the end)
check your firmware under About Phone.
If it says August, then you have to flash the device back to the older firmware.
That little detail made me go crazy for the past 2 days, so I thought I'd share that.
So, just remember two things:
1) Check your firmware!
2) DISCONNECT Internet as soon as you install vRoot and run it while you are NOT connected to avoid auto update.
And make sure to THANK ShinySide 'cause he made this possible!
Thank you for posting. I've been looking for root options for my T230NU and was skeptical about VRoot. I don't trust random apps that aren't even in English, you know?
Your post looks good so I may attempt to root as well. Please update if it turns out that VRoot is a bs virus.
babb1er said:
After spending 2 days to figure out how I can get root on my newly purchased Galaxy Tab 4 7.0,
I finally got it to work through vRoot.
Here's a detailed instruction from ShinySide.
http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
Now, where I had the problem wasn't what I did. Rather, it was the auto update that Samsung rolled out in August.
I tried doing through vRoot like, 50 times, and got the same result over and over.
Then I read ShinySide's post saying the August update interferes with vRoot so I had to flash my tablet with older firmware.
Lucky for me, ShinySide also has this available on this forum:
http://forum.xda-developers.com/showthread.php?t=2778374
I did it with NE2, and BOOM. VRoot rooted my phone like a charm.
So, those of you who are having trouble with vRoot (probably seeing X mark instead of a check mark at the end)
check your firmware under About Phone.
If it says August, then you have to flash the device back to the older firmware.
That little detail made me go crazy for the past 2 days, so I thought I'd share that.
So, just remember two things:
1) Check your firmware!
2) DISCONNECT Internet as soon as you install vRoot and run it while you are NOT connected to avoid auto update.
And make sure to THANK ShinySide 'cause he made this possible!
Click to expand...
Click to collapse
Thank you! Been a bit$h to root this thing lol. I'll try and report back what worked etc. +1
Fas
I just tried the vroot method and should've known it was trouble when I had to uninstall my antimalware software to download and install it. Damn thing installed five other programs, including trojans, and changed my browsers to go through a proxy. Best of all, it did NOT work. Beware!
Just went old-school and used Odin. See how here:
http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
So I'm now scrubbing my laptop...
reaper000 said:
I just tried the vroot method and should've known it was trouble when I had to uninstall my antimalware software to download and install it. Damn thing installed five other programs, including trojans, and changed my browsers to go through a proxy. Best of all, it did NOT work. Beware!
Just went old-school and used Odin. See how here:
http://forum.xda-developers.com/tab-4/general/root-galaxy-tab-4-7-t230-t2835264
So I'm now scrubbing my laptop...
Click to expand...
Click to collapse
Yeah I never did the vroot crap. Sounded fishy to me
faslane said:
Yeah I never did the vroot crap. Sounded fishy to me
Click to expand...
Click to collapse
I tried it on a few devices. What it does is install a bunch of root apps/exploits and keeps trying till it finds one. I think some installs a chinese app store or somesort Which is kinda weird.
faslane said:
Thank you! Been a bit$h to root this thing lol. I'll try and report back what worked etc. +1
Fas
Click to expand...
Click to collapse
Fails during Odin process....ugh. This is killing me, I'm by no means new to any of this and this damn thing simply won't take a custom recovery image or root....ANY help at all would be much appreciated.
Fas
---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------
Fails during Odin process....ugh. This is killing me, I'm by no means new to any of this and this damn thing simply won't take a custom recovery image or root....ANY help at all would be much appreciated.
Fas
DUHAsianSKILLZ said:
I tried it on a few devices. What it does is install a bunch of root apps/exploits and keeps trying till it finds one. I think some installs a chinese app store or somesort Which is kinda weird.
Click to expand...
Click to collapse
vRoot installs chinese superuser but it can be replaced
OK, so my Tab is a SM-T230NU
This is the one I cant root or flash a custom recovery too....freaking me out LOL
Anyone have ideas? there's got to be a way to root this think and install CM or TWRP....haven't even found and Android device that couldn't be...RF2F50K2LPL is serial fyi is that helps.
Fas
faslane said:
OK, so my Tab is a SM-T230NU
This is the one I cant root or flash a custom recovery too....freaking me out LOL
Anyone have ideas? there's got to be a way to root this think and install CM or TWRP....haven't even found and Android device that couldn't be...RF2F50K2LPL is serial fyi is that helps.
Fas
Click to expand...
Click to collapse
Try TWRP or wait tilm CWM is avaible and flash root
Another guide
Here's a link to another guide for the SM-T230NU.
http://forum.xda-developers.com/tab-4/development/root-tab-4-sm-t230-t2984670
I'm fairly new to rooting and I haven't tried this.
Thanks all....I haven't tried it yet. My Note 4 is sufficing and working on a few PC builds so just haven't had the need for it lol. I'll try one tomorrow and see what works. +1
HELP!
I think I may have bricked my SM-T230NU
I googled how to root SM-T30NU and didn't realize google was showing me instructions for SM-T530NU when I actually was trying to root SM-T230NU
I followed this guide
(can't share links but if you google root SM-T30NU you should find it)
I get message I am in Odin Mode and my current Binary is custom system status official
It says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I tried both versions of Kies I found and it doesn't show up in recovery mode.
I am a total noob, please help if possible.
Have you gotten it fixed yet? If not go to the opening post and find the link to the NE2 firmware. Follow instructions there to flash to NE2. You should be fine.
blaisedinsd said:
HELP!
I think I may have bricked my SM-T230NU
I googled how to root SM-T30NU and didn't realize google was showing me instructions for SM-T530NU when I actually was trying to root SM-T230NU
I followed this guide
(can't share links but if you google root SM-T30NU you should find it)
I get message I am in Odin Mode and my current Binary is custom system status official
It says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I tried both versions of Kies I found and it doesn't show up in recovery mode.
I am a total noob, please help if possible.
Click to expand...
Click to collapse

Android Pay

Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!
For me, it just has Google Play Services crashing whenever I try to add a card. This was after disabling SuperSU.
walkwithdeath said:
Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!
Click to expand...
Click to collapse
did you try stock rooted thats my next attempt after I charge phone up a little. I been reading up and it seems stock rooted with supersu removing stock or xposed rootcloak work. Just nandroid and try it out nobody says you have to use it but if that works it may give us an insight on what to target for getting it to work
Yes, so far I believe thats what I read. At this point I have read a lot. The two methods involve unchecking enable superuser in supersu and then the root cloak method via xposed. Neither have worked in every custom ROM so far. I may try CM nightlies tho.
just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!
walkwithdeath said:
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!
Click to expand...
Click to collapse
basicaly what I was saying it works on stock ONEPlus roms only it seems and you just have to deny root when adding cards. I tried to use lil while ago but it said my cards were not available yet to use with Android Pay
Just wanted to chime in with my post from another thread to consolidate threads:
I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
just as an update i re-flashed stock rom and realized using xposed and make any additional changes to the system folder causes it not to work whether I have supersu checked off or not. Now with that said i have it working fine with stock and having supersu loaded from twrp and play store nothing else. I also set up a tasker command to uncheck supersu prior to me using Android Pay. 1 click I guess I waas being lazy
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
playya said:
just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work
Click to expand...
Click to collapse
I have tried disabling root and root cloak. I am on Exodus rom and it has "morph mode" where I tried both methods in Exodus mode and AOSP mode. If this helps narrow down the problem.
For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.
Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Digil said:
For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.
Click to expand...
Click to collapse
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week
Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
playya said:
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week
Click to expand...
Click to collapse
What Rom are you Using ?!?
Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need for a locked bootloader on 1+ it works fine but strictly with stock
Skitts said:
Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
What Rom are you Using ?!?
Click to expand...
Click to collapse
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure
playya said:
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure
Click to expand...
Click to collapse
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.
Skitts said:
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.
Click to expand...
Click to collapse
So was I and I left them for crdroid which has a lot less issues. But I flashed stock to try out Android Pay and I have been surprisingly pleased. It will work just don't flash SuperSU but use built in version or update via TWRP option if asked after flashing rom
Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.
rbrugman said:
Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.
Click to expand...
Click to collapse
android authority has it and if you do a google search for it you will find it. also know that you have to un-tick auto updates in Google Play. I wiped data in Google play, Google Play Services prior to installing the now outdated version. I had to do this so that when I loaded the older version it will try and update the moment you try and set it up.

Nandroid backup needed

Woudl anyone kindly give me a copy of your nandroid backup please? I have a corrupted file system. My /system/app and my /system/priv-app have both been combined together in /data/data. There are some other unique changes too. I don't even know how the phone can operate like this, but it works flawlessly. Unfortunately, I have been hacked and nothing works to get rid of it. If anyone has good adb command skills and can guide me, I'd be happy with that. My adb commands are not extended, and not of them work thus far. I want my phone back in good shape. As of now, there is a bootloader script that erases any changes upon boot.. I need help here. I keep asking, and I see dozens of you reading... but not one reply. Help would be nice. Lol
Why do you just use Odin and reflash the tar
Sent from my SM-N920P using XDA-Developers mobile app
Yes, odin flash will wack the bootloader partitions as well.
rayraycarter4 said:
Why do you just use Odin and reflash the tar
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
If it was that simple I wouldn't be here asking for help. I've been flashing for 4 years. Hundreds of times. More than 20 devices. There is a modified bootloader that wipes any updates and keeps the script alive. It takes over my whole OS. I know because I have two Note 5's. One I just got from my friend. It has never been rooted. So when I compare the two, I see lots of major differences. Some of my settings are completely gone. Like the ability to use fingerprints to open websites and verify Samsung account. Then, on the unrooted phone, when I swipe left to briefing, it says "Briefing" wants permission. On my previously rooted, but currently unrooted phone, it says "Touchwiz Home" wants permission. On top of that, I'm not getting the prompts for permissions when I open a app. They are already granted. when I first flash BPC3 and immediately flash TWRP I can see my system files in place. When I boot and look again form ROM Toolbox, the /system folder is empty and I found everything loaded in /data/data. I see several locations with recovery scripts, and one with a fstab.storage in the cache folder. If I delete the cache, the phone will not boot. If I take any of the /data/data apps out, the phone will not boot. I have successfully got it to boot one time and everything seemed fine. However, over the course of a day, little by little, everything reinstalls itself. I'm assuming from a masked backup location. This is a real hack job, and I need some help. I'm not a complete idiot, however, this kind of thing is WAAAAAY over my head. I could start snapping screenshots and posting them here if any of you want to learn more about this and help me get it fixed. I can't use this phone like this. Somebody has complete control of my device.
tdunham said:
Yes, odin flash will wack the bootloader partitions as well.
Click to expand...
Click to collapse
Help me bro. This isn't something normal. Please. I'll provide you with whatever information you need. Read the above post.
Oh yeah, one other thing. When I use ODIN I am getting a message that says... "receiving message from bootloader. Please wait two minutes." Then it go the next file and says the same thing, On the third file it fails.
Okay, so I found some logs in the dropbox folder and found a bunch of code linked to a GitHub account owned by this guy. http://forum.xda-developers.com/member.php?u=1897326 I'm not saying that he is responsible, but I am saying that someone is using his code maliciously. I have it on my phone, I have system logs to verify it, and I have tons of problems with all my accounts being hacked. My phone will not reinitialize on Smart Switch. Nothing works. Sombebody please help me update my bootloader. I don't know how to do this myself and I can not find any information anywhere. Flashing a new sboot.tar with ODIN does not work. Upon reboot, it gets erased and the same old crap comes back.
Sleepycloud said:
Okay, so I found some logs in the dropbox folder and found a bunch of code linked to a GitHub account owned by this guy. http://forum.xda-developers.com/member.php?u=1897326 I'm not saying that he is responsible, but I am saying that someone is using his code maliciously. I have it on my phone, I have system logs to verify it, and I have tons of problems with all my accounts being hacked. My phone will not reinitialize on Smart Switch. Nothing works. Sombebody please help me update my bootloader. I don't know how to do this myself and I can not find any information anywhere. Flashing a new sboot.tar with ODIN does not work. Upon reboot, it gets erased and the same old crap comes back.
Click to expand...
Click to collapse
So what happened ? Did you get it fixed ?
Sent from my SM-N920P using Tapatalk
djxn40 said:
So what happened ? Did you get it fixed ?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I'm still working on it. This has some incredibly complicated scripts designed to stop any fixes. I haven't figured it out yet. I have been working non-stop for a week now. I think I'm close to figuring it out, but I'm not as good or even close to his skill set. A lot of this stuff is like looking at Chinese. I'm working on a new initramfs to get everything in order again. I hope to be finished soon. I'll post a detailed fix when I am finished. I'm not going anywhere, I'm here to help others as much as possible. I'll be posting a fix soon.
Somebody share their 100% stock nandroid with me. If you are worried about your data, restore the backup, do a factory reset then back up that nandroid and send me a link in a pm. I need it badly. This crap that i have isnt going away with anything. In four years, this is the ONLY device that I have not been able to fix. I know somebody was smart and backed up their factory image before they rooted. I need that person to step forward please. My device is severely f**ked up. ODIN doesnt fix it, neither does smartswitch. It has been altered with linux folders that get over looked. Please. Im a good guy. Im not gonna abuse anything you send me. Promise on everything. If you prefer to email me a link, its [email protected].
Sleepycloud said:
Somebody share their 100% stock nandroid with me. If you are worried about your data, restore the backup, do a factory reset then back up that nandroid and send me a link in a pm. I need it badly. This crap that i have isnt going away with anything. In four years, this is the ONLY device that I have not been able to fix. I know somebody was smart and backed up their factory image before they rooted. I need that person to step forward please. My device is severely f**ked up. ODIN doesnt fix it, neither does smartswitch. It has been altered with linux folders that get over looked. Please. Im a good guy. Im not gonna abuse anything you send me. Promise on everything. If you prefer to email me a link, its [email protected].
Click to expand...
Click to collapse
If you have two note 5 why dont you just root the other one and make a nandroid backup or just use one of the many resources here like the marshmellow tar or a custom rom to get what you need. Just seems odd
greco2003 said:
If you have two note 5 why dont you just root the other one and make a nandroid backup or just use one of the many resources here like the marshmellow tar or a custom rom to get what you need. Just seems odd
Click to expand...
Click to collapse
If I could use a .tar or a zip file to fix my phone, I wouldn't be here asking for a nandroid. Rooting my second Note 5 would be stupid because I see the same app data already infected on this one. Once I fix my 64GB Note 5 I'm going to sell this 32GB . Nobody buys a rooted phone. I own a cell phone repair shop. I know they won't buy rooted phones unless they are stupid. They always come back complaining about Samsung pay or something security wise that alerted them to the fact that is has been rooted. I'm seeing some of the same **** on my unrooted phone that I see on my rooted phone. It is the app-data, but at least with this phone, I can factory reset and get rid of it and start over. I 'm going to send emails to Google and ask them to clear my stored app-data on every app that is on my account. I can't keep this **** off my phone. This mother***ker wrecked my device. I have removed two of the 6 extra partitions, and now it won't boot. Even if I flash a new .tar with a pit file and nand erase. This is my first phone is four years of flashing and modding that I have not been able to fix. I am not getting any help. Just dumb questions like this one over and over. Lol IF I COULD DO ANY OF THAT, I WOULD NOT BE ASKING FOR HELP. I need a nandroid because that will fix my phone. The one I have is altered and the rest got wiped from my computer when I posted that I had logs. Those got wiped too. This person behind this is all up in my computers and phones and I can't keep them out. I've done everything. Wiped hard drives and started with a clean install on both, bought a new router and set up new passwords. and flashed my phones. It slows them down, but hey get right back in everything over the course of a week. I'm so f**king sick of this. The funny part, I bet more that half of you have the same problems, but you aren't intimate with your devices enough to know that someone is there. This person behind this is highly skilled.... to say the least. This **** was on my phone for at least 3 months, maybe four, before I even realized something was wrong. That is how smooth this is. The phone works flawlessly still. (until I removed two partitions anyways. Now it won't boot.) Share your stock nandroid after wiping it with a factory reset. I don't need any of your personal information.... Just your legit partitions layout. What is so funny about that? I have seen this request a few times in the last four years. I never thought it would happen to me though.
You wanna know a little secret? The app power saving feature has been hacked to allow apps to retain some of the battery power when the device is turned off. Here is the deal. It is not really turned off. It is in a hibernate mode that retains the app-data so that when you turn the phone back on, everything comes back. You think this is not possible? Lol you better study more, and start opening scripts on your device and reading them. You'll find all sorts of neat things if you have been flashing and modding.
Sleepycloud said:
You wanna know a little secret? The app power saving feature has been hacked to allow apps to retain some of the battery power when the device is turned off. Here is the deal. It is not really turned off. It is in a hibernate mode that retains the app-data so that when you turn the phone back on, everything comes back. You think this is not possible? Lol you better study more, and start opening scripts on your device and reading them. You'll find all sorts of neat things if you have been flashing and modding.
Click to expand...
Click to collapse
I'm a flashaholic I've been flashing and rooting since my first smartphone back in 2009 the HTC Evo 4g but I always remember rule number one make a nandroid backup I make them weekly even if I change nothing on my phone
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
Are you wanting a marshmallow one or a lollipop one they take different bootloaders
Sent from my SM-N920P using XDA-Developers mobile app
greco2003 said:
I'm a flashaholic I've been flashing and rooting since my first smartphone back in 2009 the HTC Evo 4g but I always remember rule number one make a nandroid backup I make them weekly even if I change nothing on my phone
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
Are you wanting a marshmallow one or a lollipop one they take different bootloaders
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
I'll take anything that I can get as long as you are 100% sure that it is unaltered. I'd love to have the L and the M if you don't mind. Just so I have options. I'm dying to end this b.s. Please send me either one or both. I promise I"m not gonna abuse you in any way.
The truth is, it doesn't matter. You can still revert all the way back to OI6 from PC3. I tried AOK but it wouldn't flash. Send me anything bro. I'd be grateful.
I'll see what I can do when I get home at work now what version is your phone currently running??
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
Also is rooted gonna be OK because all of my backups are from a rooted device
Sent from my SM-N920P using XDA-Developers mobile app
greco2003 said:
I'm a flashaholic I've been flashing and rooting since my first smartphone back in 2009 the HTC Evo 4g but I always remember rule number one make a nandroid backup I make them weekly even if I change nothing on my phone
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
Are you wanting a marshmallow one or a lollipop one they take different bootloaders
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
You are absolutely correct. I used to always make nandroids, but I got cocky and lazy and quit doing it. Now I regret totally regret that. I will never in my life root another phone without making a nandroid and keeping it safe in two spots. One in the cloud, and the other on a OTG all by itself. I need you bro. Please send me a good nandroid so I can end this nightmare. Lol
greco2003 said:
I'll see what I can do when I get home at work now what version is your phone currently running??
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
Also is rooted gonna be OK because all of my backups are from a rooted device
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, that is fine. Rooted is great as long as you didn't mod it before that nandroid. If so, the partition layout will be intact and when I flash it, it will wipe my device completely and I'll be good again. I have seen a few others with this problem over the years, and the only way they fixed it was by using someone's nandroid. I'm am a big fan of the Evo 4G! That is what started it all for me! Lol I made some pretty awesome JB roms for the Evo. You can see them here. http://android.aokforums.com/roms-vf3.html When I get this cleared up, I'm going to make something nice for the Note 5. It's been awhile since I've compiled any roms, but I am suddenly eager to start up again. Thank you for stepping up here bro. I won't forget this.
I can send you a backup of my current setup now but it's the deodexed marshmallow rom with sky-high kernel version 3.0
Sent from my SM-N920P using XDA-Developers mobile app

Categories

Resources