Database Info

Tab 2 10.1 GT-P5113 WIFI OTA Rooted.....

So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?

Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.

I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.

I'm wondering if I should remove CWM and unroot it first...

Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.

Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)

No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.

I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.

Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..

I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say

To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.

I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.

I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.

Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.

[Q] Update stock rooted galaxy tab

Hey all, I have a bought a galaxy tab 2 on android version 4.1.1 a while ago.
Back then I rooted the tablet so I could run whatsapp etc. on it.
After some research last days I noticed there were a few updates for the tab, and I decided that i want 4.1.2, (but still with root)
now my question is(since I can't update over the air):
How can i update my tab to version 4.1.2 while keeping the root acces and without losing or need to reinstall my apps?
because if i download the stock 4.1.2 ROM and install it, I lose all my apps and I need to reinstall it (from my experience with the htc legend).
thanks in advance!

Make a backup in CWM and install the ota; it seems that usually with this device OTA's will install properly when rooted.
You know, it's a sad day when your cellular service is faster than your home broadband.

MultipleMonomials said:
Make a backup in CWM and install the ota; it seems that usually with this device OTA's will install properly when rooted.
You know, it's a sad day when your cellular service is faster than your home broadband.
Click to expand...
Click to collapse
No, that is the problem. It is not possible because it will say taht my device is modified. But i decided to try cyanogenmod on it. And if it doesn't suit me then i will install stock 4.1.2.
but still thanks

[Q] HELP! Weak signal issues and a hot mess.

Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.

Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).

buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...

I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.

Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.

buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?

s3 root failed

I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John

648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)

I have signed into kies and it says
dawgdoc said:
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
Click to expand...
Click to collapse
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?

648charlie said:
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
Click to expand...
Click to collapse
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?

dawgdoc said:
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
Click to expand...
Click to collapse
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk

got launcher from google apps
Droidriven said:
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Loaded launcher from google apps, talked to verizon and they put s3 inservice for 5 minutes and I made a call.
all is well
thank you thank you
John

Was stock, rooted on 8.0, restarted phone, now unrooted on 10...WTH?

Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim

same here

Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.

I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?

fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.