SM-P905V Root. US Verizon - Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting

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.

Related

Cant update phone/flash with odin/root

*Copied mostly from my topic on AndroidForums*
/*from June 27th, thread start*/
So I found out that on the 25th or 26th there was an update for the Verizon GS3. Every time I try to update, it gives me this error (see below) after it reboots. I should also probably note that when it reboots, you briefly see "Booting into recovery" in the top left corner, though it doesn't actually boot into recovery. I was rooted, but I did a full unroot with SuperSU, and it still doesn't work. I dont want to flash a stock image because of all my app data that I do not want to lose.
Here is what the update screen looks like: i . imgur. com/oC04moq.png
And after the "update": i . imgur. com/oC04moq.png
Scroll down a little bit on that same box: i . imgur. com/iSqwQl0.jpg
Please someone help me! This is driving me crazy!
/End post 1\
Click to expand...
Click to collapse
/revive post October 6th\
So its been about 3 months now. Problem still persists. Again, I can not flash anything with ODIN(307), or update the phone. I have tried with Kies and in the phone. I can boot into download mode and recovery mode fine. Any help would again be greatly appreciated. I don't have access to my pc atm but any suggestions are still appreciated.
*The phone runs flawlessly, I just want to be able to root again *
/end post
Click to expand...
Click to collapse
/suggestion from user
"I would wind this back to the start.
It may not be just a phone issue. Uninstal kies and any android drivers and reboot.
Try this first:
★[8/27] [Casual] [Root, Unlock, Recovery] Vzw S3 Toolkit or 1-Click!! [ALL OTA's]★ - xda-developers
For the Verizion only. Anyone else thinking of using this start a new thread!!"
Click to expand...
Click to collapse
and my respose after trying: gyazo . com/3827e1487bf8cb3aeb0871b946fde785.png
Been on this for about 10mins, videos I have seen have done nearly instantly. I don't want to disconnect anything...
EDIT: I tried again twice. Same issue. I'm going to uninstall all drivers etc and try again.
Nup, still not working. Any more suggestions?
So far I have tried:
Odin(for root)
Kies(for updating)
Casual
Uninstalling kies/drivers and reinstalling and retrying all
All recognize the device, but nothing happens.
Click to expand...
Click to collapse
Now I'm here. I've never seen or heard anything like this before. Please post any suggestions you might have. I am down to try almost anything.
Sorry if I'm breaking any rules or anything. I just want this resolved.
And sorry for long post.
I'm assuming you've done all this with the same USB cable? Try a different cable (preferably the included one), different usb port, and also a different computer.
Sent from my SCH-I535 using Tapatalk 4
I can't even tell what is going on, this post is very confusing. Is Odin giving a fail message?
1. Odin should work, if it doesn't in a normal circumstance, then this method will work http://forum.xda-developers.com/showthread.php?t=1840030. This is will wipe all your data, but you'll be good to go from there.
2. Why did you unroot through super su? What rom are you running right now?
3. You can try using this image:
http://forum.xda-developers.com/showthread.php?t=1974114, then after you do this method you can run casual and root from there, while preserving your data.
Sent from my SCH-I535 using Tapatalk 2
Thanks to both of you!!!!!! I used a different port on my PC, and used the nowipe image BadUsername posted, and now I'm rooted, custom recovery, unlocked bootloader, and no data loss!! Again, thank you so much.
:highfive: yea teamwork! And last thing I'll suggest is to backup your IMEI if you haven't done so before.

[Q] Is it worth rooting 907A AT&T version?

So I just got the Note Pro like a week or two ago, I generally always root my devices, but I've seen lots of reports of random reboots. Does removing all of the Knox apps fix that?
So, do you guys think it's worth rooting? I've never had a Samsung device, so I know I'm going to have to read up on Odin and Kies a bit, but are there any easy step-by-step tutorials posted around anywhere?
911jason said:
So I just got the Note Pro like a week or two ago, I generally always root my devices, but I've seen lots of reports of random reboots. Does removing all of the Knox apps fix that?
So, do you guys think it's worth rooting? I've never had a Samsung device, so I know I'm going to have to read up on Odin and Kies a bit, but are there any easy step-by-step tutorials posted around anywhere?
Click to expand...
Click to collapse
It was definitely worth it for me just to have X posed installed and be able to use the GravityBox module along with some Note specific mods. Especially useful is the mod to allow any apps to be multi-window pop up apps.
l had to downgrade to an earlier build because Samsung patched the Towelroot exploit earlier this year. That required using Odin which isn't difficult at all to use. Once I downgraded the Towel root app worked perfectly and I was able to install Supersd from Chainfire. There is a debloat script you can run in Terminal Emulator and it will disable all the Knox stuff but also gives you individual options to de bloat other apps in the stock AT&T TW Rom. I've been running for a couple of weeks with no problems whatsoever.
Here's the link to the Odin files l used to downgrade. The Odin application to use is in post # 2
http://forum.xda-developers.com/gal...rsion-news-t2850564/post54879249#post54879249
Then get towel root app at towelroot.com and install → run.
And here is the debloat script to use. Just make sure you get the ATT one at the end of the first post
http://forum.xda-developers.com/showthread.php?t=2797540
Thanks for the info and links... I may break down and just do it, although I've been debating waiting for the Lollipop update.
I can always flash back to stock later, right?
The links he posted are stock, just an earlier build that towelroot works with. You should be able to go into settings and run "check for updates" when lollipop is released from AT&T.
You guys are awesome, thanks for the info. Just rooted, debloating now. Any suggestions on the best Xposed modules to use? Anything else I should install?
Awesome! I'll be giving this a go once I get home. I just picked up my note pro last weekend. Only complaint is not being able to multiwindow every app so this is perfect!
Did you guys install TWRP? If so, did you use Odin?
911jason said:
Did you guys install TWRP? If so, did you use Odin?
Click to expand...
Click to collapse
You're rooted but the bootloader is still locked and there is no way to unlock it at this time. Therefore no TWRP or custom ROMs.
---------- Post added at 11:43 AM ---------- Previous post was at 11:27 AM ----------
911jason said:
You guys are awesome, thanks for the info. Just rooted, debloating now. Any suggestions on the best Xposed modules to use? Anything else I should install?
Click to expand...
Click to collapse
GravityBox gives you the most customization options. You can get Multi Window Manager from the Play store and it works with Xposed to give you multi window for any app. Those are the two I'm using so far bit have had mine for only a few weeks.
The end of the first post has a few good xposed modules to try, http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069 And I've attached an image of the ones I like.
Hangouts?
After downgrade....does hangouts work for video calling?
help!
dsEVOlve said:
It was definitely worth it for me just to have X posed installed and be able to use the GravityBox module along with some Note specific mods. Especially useful is the mod to allow any apps to be multi-window pop up apps.
l had to downgrade to an earlier build because Samsung patched the Towelroot exploit earlier this year. That required using Odin which isn't difficult at all to use. Once I downgraded the Towel root app worked perfectly and I was able to install Supersd from Chainfire. There is a debloat script you can run in Terminal Emulator and it will disable all the Knox stuff but also gives you individual options to de bloat other apps in the stock AT&T TW Rom. I've been running for a couple of weeks with no problems whatsoever.
Here's the link to the Odin files l used to downgrade. The Odin application to use is in post # 2
http://forum.xda-developers.com/gal...rsion-news-t2850564/post54879249#post54879249
Then get towel root app at towelroot.com and install → run.
And here is the debloat script to use. Just make sure you get the ATT one at the end of the first post
http://forum.xda-developers.com/showthread.php?t=2797540
Click to expand...
Click to collapse
Hello, my first time posting of the forums.. I followed all these steps except the last step before I found this thread, and allowed the forced Ota update to screw up my root... now I can't access custom recovery mode to reinstall the old firmware. Tablet works fine, but no root and no chromecast... Not sure if you can use odin in stock recovery mode.. Is there a way to install firmware you gave the link by SD card so I can reroot? Thanks in advance!
No Odin is the only way. You can access recovery by turning the tablet on while holding down vol down and the home button.
Jargin said:
No Odin is the only way. You can access recovery by turning the tablet on while holding down vol down and the home button.
Click to expand...
Click to collapse
I'm such an idiot.. I figured that out right after I made this post.. Everything is good to go.. The only issue I'm having now is that even after debloating I'm still getting the ota update ... Not sure if I need to disable all bloatware.. I kept some of the apps like YouTube enabled but disabled the ATT ones and a few others from what I can remember .. Any suggestions on how to stop the ota update ?
Will this trip Knox and device status?
dsEVOlve said:
It was definitely worth it for me just to have X posed installed and be able to use the GravityBox module along with some Note specific mods. Especially useful is the mod to allow any apps to be multi-window pop up apps.
l had to downgrade to an earlier build because Samsung patched the Towelroot exploit earlier this year. That required using Odin which isn't difficult at all to use. Once I downgraded the Towel root app worked perfectly and I was able to install Supersd from Chainfire. There is a debloat script you can run in Terminal Emulator and it will disable all the Knox stuff but also gives you individual options to de bloat other apps in the stock AT&T TW Rom. I've been running for a couple of weeks with no problems whatsoever.
Here's the link to the Odin files l used to downgrade. The Odin application to use is in post # 2
http://forum.xda-developers.com/gal...rsion-news-t2850564/post54879249#post54879249
Then get towel root app at towelroot.com and install → run.
And here is the debloat script to use. Just make sure you get the ATT one at the end of the first post
http://forum.xda-developers.com/showthread.php?t=2797540
Click to expand...
Click to collapse
Quick question about this procedure: if I use oden to downgrade my tablet from NK2 to ND7, will my device status change from original to custom?
The purpose for this is to network unlock my tablet. I sent in my tablet for warranty repair due to the blue screen of death. They replaced the main board and reflashed the os with NK2. I've had my tablet back for 2 weeks but it came back network locked. It had been previously unlocked by a seller prior to purchase/arrival in January. I was using my T-Mobile tablet sim with the tablet which worked great.
I've tried sim network unlock codes from various sources, the code is always the same regardless of the source, with no success. I'm working with 2 theories as to what occurred at the repair center: they didn't reinstall the LTE modem properly or the flash messed up ability to successfully network unlock. If I can get the tablet to network unlock then I'll continue with the root because having the capability to use multiwindow for all apps with xposed is great.

Is 21r rootable?

So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
shxrm_ said:
So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
Click to expand...
Click to collapse
I have the same question. According to the release notes for 21r, the purpose was to update security. It appears that this is the stagefright patch.
EDIT: Appears to still be rootable.
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
aybarrap1 said:
I have the same question. According to the release notes for 21r, the purpose was to update security. I hate to think that AT&T might have intentionally worked to prevent rooting and Bump'd. Would not surprise me. AT&T has strangely been releasing a lot of updates over the last 6 months or so which is very unlike them. I have to wonder if they have not been working to prevent rooting as rooting has become harder and harder.
Click to expand...
Click to collapse
That's literally the only reason why I'm still on 20f, and usually I would just update my phone right away to get the security. I just wanted to know if it's possible
autosurgeon said:
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
Click to expand...
Click to collapse
I see your point.
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Hopefully it works for me, cause people said root worked for them on 21q, but it never worked for me
pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Looks like I will go through the long process of unrooting now. Been avoiding the OTAs since lollipop update because of the hassle of having to unroot. I am glad to see that AT&T actually worked quickly with LG on patching stagefright. Being able to root again was a main concern.
UPDATE: Thus far, after backing up all my data and apps (I use both LGs backup and TiBu to do batch backups), I have downgraded to stock unroot, and it took 3 OTAs (21f, 21q, and 21r) to get to where I am at. The unroot method only took about 10 minutes but I already had everything set up from my previous upgrade to Lollipop. The OTA updates were painful as they took a while to download and install (700+mB, 205mB, and 23mB respectively so about 1gig of wifi data) along with the optimization of apps each time. I have now successfully rooted.
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Firebourne said:
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Click to expand...
Click to collapse
Thanks for the confirmation of root as well as the the exact method that worked for you. I will be giving this a shot this afternoon. I want to take advantage of the stagefright patch while keeping root.
UPDATE: This root method worked. Had to do it twice but got it working.
Mjengles said:
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
It still refuses to work for me. I didn't change the diag port from when I restored back to stock, and I've tried it a few times just now, all to no effect.
Edit: the thing finally worked for me! I just closed the command prompt after the "send_command" part didn't work for me, and just did that part over, and it worked!!
CAUTION!!!!
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
You don't need to start all over. Just install the Gabriel kernel in twrp and you are good.
Sent from my LG-D850 using XDA Free mobile app
---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------
Firebourne said:
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
Click to expand...
Click to collapse
That only refers to secure boot errors booting twrp not booting the phone.
Sent from my LG-D850 using XDA Free mobile app
Link please? I searched the development threads, but didn't find the kernel you mentioned
shxrm_ said:
Link please? I searched the development threads, but didn't find the kernel you mentioned
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/lollipopstockkernelgabriel5-d855-t3120893
aybarrap1 said:
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
Click to expand...
Click to collapse
Second method of rooting worked for me. Hello control.....goodbye warranty
Sent from my ASUS MeMO Pad 7 using Tapatalk
Is there a bootable zip of the lastest stock Att ROM? Thanks.

SM-G930T Root Doesn't Void Warranty

The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"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"
}

			
				
method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse
djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.
Does this work for the latest November 1st update APK1?
Hello, I too would like to know if this is still the current root method and if there have been any changes?
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?
GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.
jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??
GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.

Kyocera -C6745 Help

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.

Categories

Resources