Database Develop

[Q] How to perform OTA 4.2 update to a rooted Nexus 7?

I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...

hinsdale1 said:
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Click to expand...
Click to collapse
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.

volarchico said:
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
Click to expand...
Click to collapse
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
2) I would like to know more about how you avoided this issue described in this thread here with stickmount not functioning with v4.2 because of the new mulituser framework that causes it no longer to see files in the mounted folders.
Thanks for your help and to anyone else that chimes in... any help is appreciated. Again sorry for being stupid.

hinsdale1 said:
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
Click to expand...
Click to collapse
i tried with OTArootkeeper app. but it don't update.... at restart for installing, it gave a black screen with android in the middle, with a RED icon inside it...... then it restart and 4.1.2 is always there

Perhaps these questions are so rudimentary that they hardly seem worth bothering with - but for some of us, these hacks and the info being thrown around in here are pretty confusing at times. I would be very grateful to anyone with some insight willing to help out?.

i found that this could be a problem with recovery mode... infact if i tr y to restart in recovery, it gave the same error...
i rooted with toolbox, and i'm thinking that it could have removed my recovery... now i'd like to try to recover the stock recovery with the same tool... but i'm not sure about that.

We seem to have veered off topic a bit here (at least for me)... so let me re-post the questions and beg again for mercy from any kind soles who can offer some advice?
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet?
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...

Bueller...... Bueller...... Bueller?

Hi! Last month I did the 4.1.2 OTA update. I was rooted but on stock. It updated with no problems. I used Voodoo OTA rootkeeper, restored the root, and either renistalled super su, or just updated the binary. Can't remember.....But I did lose my custom recovery. Didn't realize it till tonite when I went to do the 4.2 update.
So to your question. I forced the OTA 4.2 update. And it downloaded. I made sure voodoo rootkeeper was set to save the root. Then let it install. It rebooted. I opened voodoo, restored root, was asked to update super su binary, accepted. Still not rooted till I rebooted.
So far I have root, and am on 4.2 JB. So my goal was to get my custom recovery back on. Install goo manager from market. Open it, go to the settings button top right, it will give you the choice to install open recovery script. TWRP- Then it will ask you twice are you sure you want to do this and reboot? Say yes. Mine did not reboot and it looked like it did nothing. So, I flipped into recovery and Teamwinn recovery was installed. I made a backup, and rebooted.
Good luck!

Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.

hinsdale1 said:
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
Click to expand...
Click to collapse
Hi hinsdale,
Have you tried updating to 4.2 yet? Also i heard that if you update SuperSU to version 0.98 the latest version it could cause issues and you will have to reflash the device.
Thanks,
JBIRD
Thanks,
JBIRD

4.2 OTA already loaded, lost root
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.

Hi hinsdale! I am not a techie- I just learn as I go and read, read, read.
So, my voodoo app has 4 checks in the boxes. I seem to remember only 3 boxes checked when I did the update, but I'm not sure. It would make sense that all are checked.
After I updated, I opened the voodoo app first, and there is a box that says restore root. Then it asked if I wanted to update the su binary. Did that, still not rooted according to Tit. BU. Rebooted, then I was rooted. Good luck with your update.
I'm sorry I can't tell you how to run the initial save root on voodoo. I did it a while ago and don't remember, but it was not hard. Very easy.. Just make sure you Read, re- read, and read again before you do any modifications to your tablet. Know the possible bad outcomes, and be prepared to trouble shoot. This site is very good about helping you out if things go wrong. That's why it's a very good idea to be aware of the possible bad outcomes. The only way to know is to READ-READ=READ!
Did I mention READ??? lol. That's how I figure stuff out. If you read about others mistakes, you can avoid them. I also wait a day or 2 to see how it goes for others before I attempt modifications. That includes new roms. You never know what goes wrong until someone is the guinea pig! I am not techie enough to be the guinea pig!

paulie7880 said:
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Click to expand...
Click to collapse
same thing here...I tried to use TWRM to flash SU but it seems that after going into recovery using TWRM I can't see any any file or folder on my SD except 3 folders???? Can someone please help us....

YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.

sashusmom said:
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
Click to expand...
Click to collapse
Nexus Root Toolkit

The OTA update downloaded to my cache folder, I moved it to my sdcard. Wouldn't install since I had to fix a couple of files I had edited. So once those 2 files were fixed it installed just fine. Haven't had any issues yet.

The same on here...
But I guess it is better until they fix all this bugs they are reporting.
I'll wait until then.
Sent from my Nexus 7 using xda app-developers app

Updated to 4.2
Hi have updated the nexus to 4,2 and used Voodoo OTA Rootkeeper to keep my root followed the instructions as I did when updated to 4.1.2,my Nexus appears to be rooted superSu is working also stickmount sees the usb but it will not show any files on the sd card any help here please to get it to see the files on the sd card, thanks for your time
Nick

i dont post often as i am usually here looking for help. this time i get to help
i just downloaded and installed 4.2 OTA.
if your nexus was previously unlocked and rooted, it will download and install just fine. however you will lose root, but KEEP the unlocked state.
to root it again, you must goto "about tablet" and tap your build number 7 times to become a developer, this is not a troll, i got this info from another thread on xda.
then using the nexus root toolkit 1.5.4 with modeltype set to "android *.*.* any build", just do the root procedure.
reboot and ur in business, no need to update supersu, and busybox will still be installed already.

[Q] ICS vs JB, should I OTA? root post OTA

Hi all,
Just got the A.HD. still stock ICS.
I've been reading many threads and Google searches since, and have a couple of questions....
I would like to get answers from people who have had this phone for a while and rooted and/or done the OTA update.
I've read several conflicting user reports about the JB OTA update.
Is there any real performance gain? I've read articles showing JB boots faster than IcS and has a better overall feel.
The only solid thing I've read to make me want to do it is the ability to resize widgets in JB.
I've used JB ROMs on my captivate glide and Acer a500 and didn't care for them; but idk if they were just buggy ROMs or what (never used stock JB)
1) so who would recommend the JB OTA update and why?
2) does the motofail2go root method work after the JB OTA update? If not, what does work to root the official JB?
Again, I've read conflicting reports and would like to hear from folks that have done it.
Thanks!
-Eric

Motofail will not work on JB.
Root ICS, then you have to do some things to backup root with voodoo root keeper and what not, then install jb then restore root.
Do it carefully I am now without root on JB because I didnt know what I was doing.
To answer your other question, I think JB is worth it but meh up to you.

i kept mine on ics because the webtop feature.....
i modify a cheap atrix 1 lapdok 100 and when im away i use and love it...
of course root it to get ride of the att junk and installed safestrap recovery to install other roms....
i will start shacking about update to JB when custom kernel can be flashed to the phone but who knows when is going to happen

Backup your root on ICS and update to jb. I love having the latest and greatest and jellybean is definitely another and has some nice features that I couldn't go without now. Just my opinion
Sent from my MotoAHD Maxx

I reccomend updating to JB. I have JB and root and I couldnt imagine going back to ICS.
If you do decide to update, just be sure that you:
1) Root ICS first using motofail.
2) Open Superuser, scroll left to the info tab, select su binary, select update, exit when it finishes.
3) Next, install OTA Rootkeeper from the Play Store. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
4) Open OTA Rootkeeper and select backup su.
5) When it's finished select temp un-root, restore root, temp un-root, restore root. (I reccomend doing it twice as stated just to be safe.)
[IMPORTANT: Don't forget to update su binaries and don't forget to temp un-root and restore root. Do NOT update while temp un-rooted. Can't stress enough.]
6) Go into settings and download/install the JB update.
7) Once booted up and running JB, open OTA Rootkeeper (if it isn't still installed just re-install it) and select the first option. Something along the lines of restore su backup.
8) Once it is finished restoring root, if anything still shows up unchecked, exit the app and re-open it. Now it should all be checked. (At least that's how mine worked out.)
9) Download Root Checker or open an app that requires su to make sure you're rooted.
10) Enjoy rooted JB.
Sent from my MB886 using xda app-developers app

thanx
^
^^
^^^
^^^^
Thanx for the responses
one more q:
does anyone notice battery probs on JB.
on other two devices, JB custom rom was awful on battery... (again, dont know if they were buggy ROMs/kernels or what)
thanx again

I stayed on ICS. It seems a few things got removed on JB. I had started a list.

Do the battery mod man. Then you won't have to worry about bad battery life.
Sent from my ATRIX HD MAXX

[Q] Bionic won't activate Pageplus after JB upgrading

I'm a Pageplus user. After flashing 6.7.246 (ICS 4.0.4), I got OTA to 98.72.22 (JB 4.1.2) successfully.
But I'm stuck then when trying to activate Pageplus OTA by calling *22800:
I kept getting "Sorry, this SIM card is not recognized or registered..", no matter how many times I tried.
There's another notified error: "Unknown SIM card detected"
It's abnormal b/c it should fail only 2-3 times, then taking me to the activation screen.
The 4glteSIM card inside was activated before and used on the 6.7.246 stock build.
FYI, I also reflashed 6.7.246 one more time on top of 6.7.246 and didn't encounter the activation problem. So I'm superised to have this issue after upgraing.
Please advice me if you have any idea.
Thanks in advance.

Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app

Thx for your reminding. I'll try this way.
Did you install the cm10 with safestrap 3? I tried to install it on the JB but failed. Does it require a rooted JB?
I tried to search but cannot find an effective way to root Bionic JB.
I'll appreciate if u can give some detail abt: A. the JB rooting method, and B. How to install cm10 (or the justed released Blurry-JB_2.4.zip) while keeping the JB stock rom.
Thanks a lot!
Wilsono1050 said:
Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app

I managed to have the JB stock rom rooted anyway (by the virtual box approach).
Then I was allowed to install safestrap 3.1, then the newest Blurry JB 2.4.
I tried to "activate" from the step 2 ("2-Getting phone ready for OTA Activation") of the old instaruction:
http://www.howardforums.com/showthr...CS-OTA-Activation-TXT-MMS-3G-ROOT-on-PagePlus
But the CDMA Workshop didn't find the port. I assume the reason is that safestrap has blocked the normal bp-tools booting way.
So I can only start from "3-OTA Activation".
After changing "Network Selection" to "CDMA Only", I rebooted and dialed *22800. Still get the same error "sim card not recognized or registered".
Can you please detail how did you "activate" it under cm10?
Many thanks.
Wilsono1050 said:
Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse

Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app

I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Wilsono1050 said:
Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse

may thx. that work!
taller238 said:
I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Click to expand...
Click to collapse

taller238 said:
may thx. that work!
Click to expand...
Click to collapse
Did you get it to work?
Sent from my XT875 using xda app-developers app

did anyone get this to work?
Thinking of just saving myself the headache and getting a droidx2.
I'm running cm10.1 and safestrap 3.11 3. I'm going to try a dealer tomorrow to see if they can activate it on pageplus.
I haven't activated a phone on pageplus for a while. I've been using simple mobile, straight talk and h20

taller238 said:
Still get the same error "sim card not recognized or registered.
Click to expand...
Click to collapse
I had the same problem when I went from GB to ICS. I just ignored it and kept trying and trying (based on advice/steps I found elsewhere) and after a few times it worked. So I would suggest trying it about 10-12 times in a row to see if it works.
Also, here is the method I used for GB to ICS, I'd be interested to know if they help you move from ICS to JB:
Re-activating phone
1. Remove any old Motorola Droid Bionic drivers you may have on your computer and install the newest ones.
2. Turn phone off and turn back on in BPTools mode. Then plug the phone into your computer via USB.
3. Open DFS. Click "Ports" and select the COM port for your phone. Next, click the "SPC" button.
4. Click the "Programming" tab and then the "General" tab. Change the "Ruim Config" to NV_ONLY and click "Write".
5. Click the "Data" tab. Under the "Mode" section, change the "HDR SCP force AT config" option to "RevA_MFPA" and click "Write".
6. Close DFS and unplug phone from USB port.
7. Go to the dialer and dial ##7764726 (##PROGRAM). When prompted for an SPC password, enter "000000" and hit verify.
8. Go to "06 Test Mode". Hit "Next" twice. Then, change the Network mode to "CDMA Only".
9. Back out to the home screen; the phone will automatically restart.
10. After the phone has restarted, go to the dialer and dial *22800. Ignore any SIM card error messages you may see; just keep trying *22800 until you reach the activation screen.
11. Follow the instructions to activate the phone.

I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.

has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD

BuonaDomenica said:
has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD
Click to expand...
Click to collapse
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
well your links are not working as I want to check it out

primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
BuonaDomenica said:
well your links are not working as I want to check it out
Click to expand...
Click to collapse
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
http://www.howardforums.com/showthread.php/1794056-Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
http://www.howardforums.com/showthread.php/1795498-Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms!
they weren't links,,, google is your friend,,, they are at howardfourms enjoy these links though...
gonna be looking them over myself
.

Kralik said:
I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole[/URL] (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.
Click to expand...
Click to collapse
THANK YOU so much for making this post! I was finally able to activate my bionic after a week of reading the internet. lol. To update this post, yes, you need to do 4b. That step was what got me over the hump.

Anyone know the reason why no 3G? 1x works just fine. When toggle cdma/evdo, it still shows 1x.

I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.

ShadyDreamer said:
I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.
Click to expand...
Click to collapse
THIS! This so much! I had given up on flashing custom rom's after successfully switching my XT912 to page plus (3g/MMS working) and from there had just given up on custom roms after such a large headache. That was a year ago when the phone was coming from ICS to Jellybean (that was a rookies worst nightmare when google is your only quick resource: wrong versions, wrong tools, old information and didn't know a damn bit better. Ugh) anyways, I recently came back to try it out but found out yet again I was trying to use old information when getting through the activation process. This solved it though. I used Titanium Backup (trial version) to delete the system app/process and activation screen popped up on first try! If anyone else has the same issue that I had, where US Cellular answered my activation call, don't fret. I imagine it has to do with the SID (CDMA Network ID) but then I had let the phone sit for a minute and noticed at the bottom "a special number needs to be called to activate this phone" hit that button then the Verizon activation system answers and its good to go from there.
I'll now install safestrap and hopefully get a version of CM11 to run properly which caused this whole re-flashing process. I had a "working" stock rom that would constantly try to activate on phone startup, but 3g would work after skipping all those annoying screens, however when booting to CM11 it was not working with 3g.
Thank you again for that information, I can confirm com.motorola.setupwizard.phoneservice is the culprit to OTA activation problems when switching to PagePlus network.

Andoid 4.3 Discussion

So finally Android 4.3 has arrived and our Beloved Nexus 7 is Upgradable Now.....
here is the link to the download of factory Image:
https://developers.google.com/android/nexus/images#nakasijwr66v
Follow this Method and flash the New Android OS...
[GUIDE] Flashing a Factory Image with fastboot / return to stock Thanks @comminus for a great Guide...
Report Back with screenShots and new featuers as well as Bugs because new pudates bring New Bugs.....

The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....

hassam_tariq2003 said:
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
Click to expand...
Click to collapse
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.

tbonezx11 said:
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
Click to expand...
Click to collapse
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.

mhl12 said:
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
Click to expand...
Click to collapse
haven't tried it (I'm yet to receive the update) but someone referenced this link: https://plus.google.com/u/0/+Chainfire/posts/WqS2E9kkN1L

he is right.....You loose root but bootloader remains unlocked...
i have heard people say that you do not loose root if you use the OTA Method and your bootloader also remains unlocked....So its your choice its either Fastboot or OTA...

Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.

Yeah OTA wont work for most people, seeing as they probably have a modified ROM. In any sense, chainfire has a root method that works. I can confirm it working, because I installed it using TWRP

khaytsus said:
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Click to expand...
Click to collapse
When 4.2.2 came out I had problems updating because my ROM was modified. But someone modified OTA not to check for changes in ROM and it worked.

no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."

I am running 4.3 unlocked but I did the one click method for root using nexus tool kit and for some reason it did not work, I have to try again tonight.

Want a single click ADB setup? Go to my thread I've made a Tool for that. No need to download the whole SDK it's just 2MB
http://forum.xda-developers.com/showthread.php?t=2374071
What to know how to easily pull ota link with ADB follow my thread.
http://forum.xda-developers.com/showthread.php?t=2270429
For official nexus 7 windows 7 - 8 driver download them from ASUS site. No trickery needed.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP

So, I played around a bit,
First of all, I did a "clean, unrooted and even locked bootloader install".
So I'm 1000% stock, just to avoid stuff like "maybe root caused it"..
(I locked it because I wanted to go 100% stock, just FYI, I know it's normally not necessary...)
The welcome screen was a bit weird... I got asked 2 times to tick or untick boxes for saving passwords and all that stuff.. (I think they mixed up the new and the old "first boot setup"?)
The Apps and widgets in the drawer were kinda confused, took 2 reboots for them to settle... (Icons disappeared and reappeared.. The widget tab in the drawer threw some widgets in and out, and the previews were mixed up, so dots and a weird sign was the result (as a preview of the widget)...
The initial setup was pretty laggy, but after setting stuff up, until now, yes I can say the performance of the nexus 7 is improved..
First I was like "OH HELL NO" but after the setup and the reboot everything was smooth...
Oh, and the back button was destroyed 1 time, blinked up but didn't go back... I pressed the home button and it worked then.
Edit: And sadly, no new wallpapers in stock... ):
Sent from my Nexus 7 using xda premium

I booted it up, restored my Google Play stuff (flashed a factory image, completely wiped everything from it, so it's clean, I think).
It lagged a lot, so I rebooted it and it still isn't 4.2.2 smooth. Maybe it's just me, I'll see.
Is it just me, or does it feel like the only thing that changed for us is the number in settings menu besides Google Apps?
OpenGL ES as it was already said, doesn't appear to be here for us, not to mention the fact that Miracast had never actually worked on N7 until recently when someone had it ported over.

Has anyone managed to find the link for the OTA yet?

SO I flashed the stock 4.3 kernel on a 4.2.2 rom and discovered that the stock android 4.3 kernel breaks wifi and gps on 4.2.2...

Eregoth said:
Has anyone managed to find the link for the OTA yet?
Click to expand...
Click to collapse
I have literally hours working on that.

Flashed the stock image using fastboot, took like 2 minutes to do, flashed the chainfire root patch and rebooted and restored apps, so far everything is pretty smooth no disappearing apps or icons or buttons, the kernel seems to be quicker, opening websites was quite a bit quicker, one thing I noticed while trying out different browsers was ads opening up new tabs automatically, that's something that's never happened before.

ffaiz.m said:
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
Click to expand...
Click to collapse
Tegra 3 does not support GLES3. Even Tegra 4 won't, because nvidia are still using their old gpu architecture.

What's the performance like? Better than 4.2 or 4.1?
Sent from my GT-I9300 using xda premium

[GUIDE] How to root Salaxy Tab S2 T817T

How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/

phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.

Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!

An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!

patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply

phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.

patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.

Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.

patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!

Yep! Been using this for two weeks now and no problems!

Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.

phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.

androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.

Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app

androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.

My mobile data and SIM functions all work fine. Not sure why yours didn't

patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!

phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?

patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.

One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.