Database Users

OTA 4.2 & SuperSU v0.98

Has anyone been successful in update their Nexus 7 device with the following configuration:
1. Stock ROM
2. Rooted
3. SuperSU v0.98 (recently updated)
4. Voodoo RootKeeper
5. DPI set to 160, need confirmation but assuming this needs to be reverted back to 213
I have been viewing other posts of successful upgrades but with prior versions of SuperSU, so I was hoping i could find that one person who has the above configuration and was successful in updating.
Thanks,
JBIRD

Apart from 4, the Rootkeeper, that was my setup when I updated from 4.1.2 via the 4.2 OTA (adb sideload).
Worked fine.
Re-rooted using superboot and am happycat ever since.

SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.

rmm200 said:
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
Click to expand...
Click to collapse
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?

jbird92113 said:
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
Click to expand...
Click to collapse
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.

rmm200 said:
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
Click to expand...
Click to collapse
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?

jbird92113 said:
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
Click to expand...
Click to collapse
Yes!

rmm200 said:
Yes!
Click to expand...
Click to collapse
One last thing, I changed my DPI settings to 160, do I need to revert to back to 213...

I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you recommend to be on the safe side that I disable supersu as well prior to the upgrade?
Thanks again...

Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app

Oh, you didn't mention you were on Safestrap. That may bring up some additional issues. And you do need to revert your build.prop to the original. With any luck, you have a build.prop.bak that you can restore. SuperSU hasn't caused me any problems, but I don't use multi-user.

rmm200 said:
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Thanks again for all your help..

jbird92113 said:
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Click to expand...
Click to collapse
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.

If you use MSkips Nexus 7 Toolkit and use option 8 it will not only unlock the boot loader, but root, install busy box, your choice of either cwm or twrp, recommends using the 3.34 bootloader, and recommends using SuperSu 0.98 due to problems with superuser not being updated yet. I can attest to the fact that the 4.13 bootloader causes root issues. At least on my 7. Apparently that isn't so on all 7s.
Sent from my Nexus 7 using xda premium

rmm200 said:
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
Click to expand...
Click to collapse
I am not going to use the multiuser feature as I am the only one who uses the tablet. Will rerooting work on the primary user?

Seems to work fine.
Sent from my Nexus 7 using xda app-developers app

So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium

Gigabitex2 said:
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Only problems I have seen are trying to set up / use a second user while rooted.
Stay away from multi-user and you should be fine.
Note - problems I have reported with SuperSU may just be related to multiuser and root, no matter how you get root.
I have not tried the "superuser" app, so I have no idea if the problems will be the same.

Lost root after 4.2 update. Need help!

Hi guys, I just updated my N7 to 4.2 and I lost root during the process. I made a su backup with Voodoo OTA rootkeeper before I did the install. After the install was complete, went back into voodoo to restore root, rebooted, and did a root check using 3 different apps. Voodoo shows my device rooted and root checker and titanium backup cannot find my root access. Is there something I did wrong, and is there any way to restore root access without a fresh wipe. Thanks in advanced!!!

Try uninstalling your root App and then reinstalling it. You also might want to wipe cache and data for your root App in Apps under Settings. Do this before uninstalling.
If that doesn't work push root to your device using one of the many methods available.
Sent from my Nexus 7 using xda premium

ezas said:
Try uninstalling your root App and then reinstalling it. You also might want to wipe cache and data for your root App in Apps under Settings. Do this before uninstalling.
If that doesn't work push root to your device using one of the many methods available.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tried that with no luck. I am trying Wug's toolkit right now, but android 4.2 doesn't show up under the model list.

Need to push the superuser app via fastboot. Either adb or use wugs toolkit.
Sent from my Nexus 7 using Tapatalk 2

Testingchip said:
Need to push the superuser app via fastboot. Either adb or use wugs toolkit.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Wugs worked perfectly. THANKS!! For anyone who is having the same problem, I used wugs toolkit, and I chose Nexus 7 "any build type" under the model type.

Glad you got it. I did the update at work and had the same problem till I got home to the pc.
Sent from my Galaxy Nexus using Tapatalk 2

silentbeatz said:
Wugs worked perfectly. THANKS!! For anyone who is having the same problem, I used wugs toolkit, and I chose Nexus 7 "any build type" under the model type.
Click to expand...
Click to collapse
I hesitate asking thjis but being greener than grass I need you if you would please explain in very noob terms how to push superuser in Wugs. I use the tool kit and was sucsefully rooted in 4.1.2 but the "upgrade" to 4.2 has brought me back to square one and having spent the money on apps like titanium backup I would like to one again use them. Thanks and sorry to be so needy but I'm trying.

patience1 said:
I hesitate asking thjis but being greener than grass I need you if you would please explain in very noob terms how to push superuser in Wugs. I use the tool kit and was sucsefully rooted in 4.1.2 but the "upgrade" to 4.2 has brought me back to square one and having spent the money on apps like titanium backup I would like to one again use them. Thanks and sorry to be so needy but I'm trying.
Click to expand...
Click to collapse
I ran into same problem, if you use Wug Toolkit, make sure you set to "android Anybuild". this Toolkit is not yet updated for 4.2.
There is another Nexus Toolkit by Mark Skippen which was updated to 4.2, however you need to donate to get the latest version. It works well for me
It's woth the donation of Pounds 5 or $8++ something
Good Luck

dominicvn said:
I ran into same problem, if you use Wug Toolkit, make sure you set to "android Anybuild". this Toolkit is not yet updated for 4.2.
There is another Nexus Toolkit by Mark Skippen which was updated to 4.2, however you need to donate to get the latest version. It works well for me
It's woth the donation of Pounds 5 or $8++ something
Good Luck
Click to expand...
Click to collapse
All fine and dandy and I dont mind spending the money but if I use Wugs do i just plug in to the computer open Wugs choose any build and then hit root? TIA and thanks for responding. Like I said NOOB

silentbeatz said:
Hi guys, I just updated my N7 to 4.2 and I lost root during the process. I made a su backup with Voodoo OTA rootkeeper before I did the install. After the install was complete, went back into voodoo to restore root, rebooted, and did a root check using 3 different apps. Voodoo shows my device rooted and root checker and titanium backup cannot find my root access. Is there something I did wrong, and is there any way to restore root access without a fresh wipe. Thanks in advanced!!!
Click to expand...
Click to collapse
Hi did you by any change have SuperSU v.0.98 installed prior to the upgrade with survival mode enabled?
Thanks,
JBIRD

Android is upgrading message everytime I reboot phone.

This wasn't happening yesterday. Every morning I reboot my phone when j remove from the Wireless charger to prevent the wireless charger wakelock.
This morning however I notice that everytime I reboot I get the Android is upgrading message as if I just performed a OTA.
The phone finishes the upgrade and looks and acts fine bit if I reboot again it does it again.
Anyone else experience this before? Its still happening if I reboot everytime.
Sent from my Nexus 7 using xda app-developers app

Clear cache and maybe load a new kernel maybe?
Sent from my Nexus 4 using xda app-developers app

if you didnt do it yourself, then its either an app, a mod, or the rom/kernel that youre running. whats happening is that your dalvik-cache is getting wiped then rebuilt on boot.

I'm on stock 4.2.2 rooted and running motley kernel. Have been running this setup for a month no and no issues and haven't installed any weird apps that could do this.
Doesn't make sense
Sent from my Nexus 4 using xda app-developers app

I think it happens when you wipe davlik with apps disabled.
if it only pops up for a second or so, don't worry about it.

It was the beats audio root app (paid version) I noticed it would consistently say permission granted even when the phone was idle.
Uninstalled the drivers using the inapp uninstaller and now no more message when rebooting.
Anyone know why this app clears dalvik cache every reboot?
Sent from my Nexus 4 using xda app-developers app

nextelbuddy said:
It was the beats audio root app (paid version) I noticed it would consistently say permission granted even when the phone was idle.
Uninstalled the drivers using the inapp uninstaller and now no more message when rebooting.
Anyone know why this app clears dalvik cache every reboot?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i use the beats+xlouder flashable mod, and it clears dalvik upon flashing. its nonsense that the app clears dalvik after a reboot, i definitely wouldnt be happy with it.

nextelbuddy said:
I'm on stock 4.2.2 rooted and running motley kernel. Have been running this setup for a month no and no issues and haven't installed any weird apps that could do this.
Doesn't make sense
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This started in 4.0, its just part of system startup to check system integrity I believe
Sent from my Jelly Nexus 4

So how do you find out which application is the one that's wiping the cache?

yahoowizard said:
So how do you find out which application is the one that's wiping the cache?
Click to expand...
Click to collapse
its probably one that needs root. it could be a flashed mod too.

simms22 said:
its probably one that needs root. it could be a flashed mod too.
Click to expand...
Click to collapse
Thanks, I think I found what the problem might be.

yahoowizard said:
Thanks, I think I found what the problem might be.
Click to expand...
Click to collapse
sweet

Thank you for sharing what was the problem.

I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click Toolbox button then select 4th last option i.e Remove all odex files. Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachement for help.
:good:Hits Thanks If I helped u:good:

[Q] Downgrade to 4.3?

What is the easiest way to downgrade from 4.4 to 4.3? My devise is completely stock. 4.4 is just too laggy

coppercents said:
What is the easiest way to downgrade from 4.4 to 4.3? My devise is completely stock. 4.4 is just too laggy
Click to expand...
Click to collapse
You can flash the factory image but you'll lose all your data. Or you can use wugs toolkit and use flash back to stock option and it will do it for you but you still lose all data. Are you sure you want 4.3? 4.4 is smoother for me
Sent from my Nexus 5 using xda app-developers app

Rooted Device Downgrade
So to be clear, even if the N10 is rooted, in order to go back from 4.4 to 4.3 one has to flash the factory image? Wiping the device and restoring a 4.3 Nandroid backup of a previous 4.3 ROM will not work?

gbeardmore said:
So to be clear, even if the N10 is rooted, in order to go back from 4.4 to 4.3 one has to flash the factory image? Wiping the device and restoring a 4.3 Nandroid backup of a previous 4.3 ROM will not work?
Click to expand...
Click to collapse
Yes it will work but your progress since that nandroid is lost if you dont backup. You can also flash a 4.3 rom. Or mod the Factory image to not wipe your SD.
Sent from my Galaxy Nexus using XDA Premium HD app

If 4.4 is more laggy for you than 4.3, you're doing something wrong.

Maybe just trying a factory reset of 4.4 might cure it.

xsalemx said:
Maybe just trying a factory reset of 4.4 might cure it.
Click to expand...
Click to collapse
I've tried factory reset with no luck. Still laggy.
Thank you all for your replies. It is really appreciated.
So what would be the easiest way for me to return my device to 4.3 using Google's factory images? Sorry for being a little annoying. I don't want to brick my device

My Nexus 10 is also more laggy on 4.4. Strange.

Is it laggy immediately after the factory reset or after you've set up your apps?
Sent from my SGH-I747M using xda app-developers app

gc84245 said:
Is it laggy immediately after the factory reset or after you've set up your apps?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Yes it is laggy even after reset and reflashing the factory image with wugs toolkit. When the screen rotates, there is some stutter. I'm back on 4.3 and it's much better for me.
Thanks to abdel12345 for recommending wugs toolkit. It was an easy process

I installed via the factory image, and have no issues with 4.4. If anything, it's better.

Hi,
i go now also back to 4.3 because Simpsons is not playable on 4.4! It's soooo laggy. But only this Game.
Greets
Chris

jimh425 said:
I installed via the factory image, and have no issues with 4.4. If anything, it's better.
Click to expand...
Click to collapse
Yep I've figured out that the resulting system when you do 4.3---OTA---4.4 is a slower system than if you do a stock flash install. I've also now unclicked the "backup and restore" to not carry over anything.
Prove it yourself, by all means... if you're going to flash down to 4.3, flash to 4.4 first, try it and then flash to 4.3 if its still laggy, but I betta 5cents you'll find it better. That one game - Simpsons - just install it and benchmark.
As I do not know what is the cause of this lag-from-upgrade, I now also don't click on the "backup and restore" to make mine as vanilla as possible. I've just now done this to my N4 also having found it better having done it on my N10 yesterday.
I been using WUGS NRT to do unlock (one time), flash+unroot, and root.

Am thinking of downgrading as well..
Mine is completly stock..but after updating..i get graphical artifacts..battery charge time has doubled...it lasts 25% less...mic is badly placed even before
Google seems to in denial with nexus 10 problems..did not exect this from google
Sent from my HTC One X using xda app-developers app

When my n10 Finish's charging but if still hook up to pogo charger it becomes laggy... Try that if y have pogo chargsr . this does not occur w USB charging.
Anyone successfully bk to 4.3 w.o losing data?

Hi,
If you ever wondered if there was a way to restore stock without losing all your data, there's a way, which is not hard too... Just do the following:
Reboot in your custom recovery and then factory reset your device
Reboot system
Now download the Factory ROM and move it (the img files) to your adb/fastboot folder
Open a cmd there and do the following (remember to have the USB Debugging on)
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot reboot
Now wait for it to boot
Hope this helps you guys who want to downgrade to 4.3 and were afraid of losing your data (remember, the recovery still deletes your apps data, but you can backup it with an app like Titanium Backup).
I may write an script to do this soon... If you want you can wait for it (but it may be delayed up to this weekend).
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10

XxLordxX said:
Hi,
If you ever wondered if there was a way to restore stock without losing all your data, there's a way... <snip>
were afraid of losing your data (remember, the recovery still deletes your apps data, but you can backup it with an app like Titanium Backup).
Click to expand...
Click to collapse
That is useful to know but how is it any easier than simply copying to Wifi NAS or connecting external storage, copying it out and back in again? You'd be backing up anyways as a good techie. As you say it deletes everything bar data.
FYI if you did ever want to WRITE to NTFS volume then selinux mode changer app is what I use.

nigelhealy said:
That is useful to know but how is it any easier than simply copying to Wifi NAS or connecting external storage, copying it out and back in again? You'd be backing up anyways as a good techie. As you say it deletes everything bar data.
FYI if you did ever want to WRITE to NTFS volume then selinux mode changer app is what I use.
Click to expand...
Click to collapse
In my case this one is way easier, as I have almost 32GB used, and it takes a whole lot time to just backup, who says copying it back. I know it's good to always backup, however in some cases (like mine) it's a way easier method to do like I explained above.
This is just an alternative method I'd like to share, I actually used this many times already, due to soft bricks, then I can't simply plug a external hard drive on my recovery and it would take ages to backup my data via adb. This is the best unbrick method IMO, as you're installing fresh ROM without the need of formatting your data, and works as well with installing a new ROM .
Just my point of view hehe
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster KitKated S4

XxLordxX said:
In my case this one is way easier, as I have almost 32GB used, and it takes a whole lot time to just backup, who says copying it back. I know it's good to always backup, however in some cases (like mine) it's a way easier method to do like I explained above.
This is just an alternative method I'd like to share, I actually used this many times already, due to soft bricks, then I can't simply plug a external hard drive on my recovery and it would take ages to backup my data via adb. This is the best unbrick method IMO, as you're installing fresh ROM without the need of formatting your data, and works as well with installing a new ROM .
Just my point of view hehe
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster KitKated S4
Click to expand...
Click to collapse
I have made note as I need to get into command line habit, I only go to Windows now to do Android recovery type operations, I use Ubuntu desktop and they have the adb and fastboot commands all native since Ubuntu made their own tablet is. Actually I'd quits like to know if can Android-usb-Android say my phone fix my tablet. Is that possible?
Sent from my Nexus 10 using Tapatalk

nigelhealy said:
I have made note as I need to get into command line habit, I only go to Windows now to do Android recovery type operations, I use Ubuntu desktop and they have the adb and fastboot commands all native since Ubuntu made their own tablet is. Actually I'd quits like to know if can Android-usb-Android say my phone fix my tablet. Is that possible?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Hi,
This one thing I still want to do, I managed to make my Nexus identify my S4, and the same on the other hand, however I didn't manage to get adb/fastboot working yet, I'll try some more researches and then we can see hehe.
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Monster KitKated S4

New Update: 14.3.2.2

HDX 8.9" - Today - UK - 06:06 BST

Got mine last night around 1am.
HDX 7" here
Sent from my Nexus 4 using Tapatalk

Is a changelog available?

Tilgi said:
Is a changelog available?
Click to expand...
Click to collapse
All I can see on Amazon is:
"The software update includes general improvements and the following feature enhancements:
Enhance your device's security with encryption
You can now encrypt your accounts, settings, and downloaded apps and their data, media, and other files on your Kindle Fire. To learn more, go to Protect Your Data with Security Settings.
Test your knowledge with Flashcards for Kindle Print Replica textbooks
Create flashcards to help you learn more about key terms and concepts in a textbook. To learn more, go to Reading Enhancements."

Mine is Downloading now.
Should I stop it?
Sent from my KFTHWI using XDA Premium HD app

damianlph said:
Mine is Downloading now.
Should I stop it?
Sent from my KFTHWI using XDA Premium HD app
Click to expand...
Click to collapse
Only if you want to either keep root or possibly root sooner rather than later.

Nirrik said:
Only if you want to either keep root or possibly root sooner rather than later.
Click to expand...
Click to collapse
I got the update. I'm not ahving much luck with 14.3.2.1, so maybe this will have something I can spot more easily. I still think using stream writter with a fudged update may be possible, but I am running into signature issues. Maybe including it as a part of the fwupdate tar archive, but not 100% on that.
At any rate, IF YOU INSTALL SafeStrap on the stock slot & then install safestrap again while in the working rom-slot (i.e., rom-slot 1), the update will reboot into fastboot, then you will reboot (do not wipe device) & the safestrap popup will display. Otherwise the device cannot boot, because the new boot.img CANNOT insytall if you have safestrap installed on rom-slot too. At that point, all you need to do is reflash the 14.3.1.0 COMPLETE firmware bin (Hashcodes stripped zip won't do it) & you are good again. Just keep the supersu zip in sdcard for flashing right away as well.

amazon app store
Not working after update

So I activated my "stock" rom slot because I wanted to try something. I forgot about the auto update, and my kindle updated and now I lost safestrap so I can't get into my other rom slots. Naturally root is gone too. CRAP! My Kindle was running so well with GAPPS too.