Nexus 7 slow after 1-click root? - Nexus 7 Q&A, Help & Troubleshooting

I recently downloaded the Nexus 7 Toolkit and performed a 1-click unlock bootloader, root, flash recovery, and installed busybox .. or option 8. Afterwards, the homescreen widgets and the switching between screens seem somewhat delayed/slowed. Is anyone else experiencing this?

mmcypark said:
I recently downloaded the Nexus 7 Toolkit and performed a 1-click unlock bootloader, root, flash recovery, and installed busybox .. or option 8. Afterwards, the homescreen widgets and the switching between screens seem somewhat delayed/slowed. Is anyone else experiencing this?
Click to expand...
Click to collapse
I'm experiencing exactly the same issues

it is highly unlikely that the cause is from the actual rooting process. have you installed any weird apps after rooting your tablet?

redundant409 said:
it is highly unlikely that the cause is from the actual rooting process. have you installed any weird apps after rooting your tablet?
Click to expand...
Click to collapse
No. Its the exact same apps, data previously, before the process.

Odd mine actually seems to be quicker since I 1-click rooted it and I've stuck AdAway and AVG on it since doing so as well!!

My nexus 7 has been running slower lately but it turned out to be google maps autoupdated and needed to be run. I open maps and boom this thing is running superfast

Related

[Q] Re Root Nexus 7 after JZO54K

Steps to now.
Used Nexus Root Toolkit 1.5.3 to unlock and root my virgin Nexus 7 running JRO03D. All went well, StickMount worked and I installed Titanium and Clockwork Rom Manager. Everything great. It seem like I should have installed some sort of unlock protection but I did not know about that.
Read abut JZO54K and liked rotating launch screen idea.
(Big Mistake) used Rom Manager to install downloaded zip file. Got warning that this was going to lock me up but did not see any way out. I am running locked JZO54K and all my apps are intact.
Device is now locked and not rooted. Tried Nexus Root Toolkit 1.5.4 but can not unlock the device.The Unlock button just ends up rebooting the device into locked JZO54K. If I power off and restart the padlock shows open at first. then the X, and then the padlock is locked.
I really miss StickMount.
Any ideas?????
Roger
rsipson said:
Steps to now.
Used Nexus Root Toolkit 1.5.3 to unlock and root my virgin Nexus 7 running JRO03D. All went well, StickMount worked and I installed Titanium and Clockwork Rom Manager. Everything great. It seem like I should have installed some sort of unlock protection but I did not know about that.
Read abut JZO54K and liked rotating launch screen idea.
(Big Mistake) used Rom Manager to install downloaded zip file. Got warning that this was going to lock me up but did not see any way out. I am running locked JZO54K and all my apps are intact.
Device is now locked and not rooted. Tried Nexus Root Toolkit 1.5.4 but can not unlock the device.The Unlock button just ends up rebooting the device into locked JZO54K. If I power off and restart the padlock shows open at first. then the X, and then the padlock is locked.
I really miss StickMount.
Any ideas?????
Roger
Click to expand...
Click to collapse
Maybe try a newer version of the Root Toolkit. Current version I think is 3.4.0
rerood nexus 4
ich11 said:
Maybe try a newer version of the Root Toolkit. Current version I think is 3.4.0
Click to expand...
Click to collapse
I am using WugFresh Nexus Root Toolkit. The latest version is 1.5.4. Perhaps I should try Root Toolkit if it is a different program.
rsipson said:
I am using WugFresh Nexus Root Toolkit. The latest version is 1.5.4. Perhaps I should try Root Toolkit if it is a different program.
Click to expand...
Click to collapse
You can find it at here
ich11 said:
You can find it at here
Click to expand...
Click to collapse
I downloaded and tried the Nexus 7 Toolkit 3.2.0. I tried several times. It reports that bootloader is unlocked but when I try to root it ends up telling me that the device is not found and it can't puts su etc. I always end up booted into stock 4.1.2.
Looking at this forum it seems that I am not the only one with this problem.
Is there some way I could go back to 4.1.1 and restart from there? Does the fact that I was once rooted and have SuperSU, BusyBox, Clockwork etc installed mess things up? Should I uninstall them and try again? Very frustrating.
Roger
Got root again by using WugFresh Nexus Toolkit. Used suggestion on his Page to replace bootloader. Then I rooted without needing to unlock and wipe. Stick Mountain works again.
Sent from my Nexus 7 using xda app-developers app

[SOLVED]Lost root after flashing SmoothROM 4.4

Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Also, sorry if this is in the wrong section, forums are so damn confusing. Mods, feel free to move this to the right spot if it ends up being the wrong spot.
Re: Lost root after flashing SmoothROM 4.4
Solved. It was SuperSU. Remove it, then switch to superuser instead.
Sent from my Nexus 7 using xda premium

Still no stock image? cmon google...

Shesh...the device been out for over a week now, im shock to see theres still not a official firmware image
immunityx said:
Shesh...the device been out for over a week now, im shock to see theres still not a official firmware image
Click to expand...
Click to collapse
I agree. I wanted the stock images to test if my device got a bad flash from the factory causing all of the multi touch and freezing issues. I ended up just exchanging at BB and have yet to upgrade to JSS15 in case that is the culprit.
Rod3 said:
I agree. I wanted the stock images to test if my device got a bad flash from the factory causing all of the multi touch and freezing issues. I ended up just exchanging at BB and have yet to upgrade to JSS15 in case that is the culprit.
Click to expand...
Click to collapse
There is no official one but there is an unofficial one, when the TWRP bug got me, it saved my system. It would still be soft-bricked waiting on Google otherwise.
I know right we need that incase something goes wrong and we can restore right to that i know we have ones on here but i want official
Sent from my Nexus 7 using Tapatalk 4
Hmmm nexus4 all over again
>^.^< Sent from meow HTC One which is like catnip to me atm
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Midnight_Rider said:
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Click to expand...
Click to collapse
they want a factory google released image
Midnight_Rider said:
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Click to expand...
Click to collapse
Nope. A factory image contains all the partitions, not just an update zip. Its used mainly to help devices that are completely broken (won't turn on), or people who want to unroot and go back to complete stock.
If it was there, it would be here: https://developers.google.com/android/nexus/images
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
gotcha, i understand the diff
danvee said:
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
Click to expand...
Click to collapse
It is extremely rare to have anything go wrong just unlocking the phone. You might as well go ahead and do it because eventually you will and it'll force a wipe data. Might as well do it now before you install too much stuff.
You can leave root and custom recovery until the images show up if you are concerned about borking your system.
sfhub said:
It is extremely rare to have anything go wrong just unlocking the phone. You might as well go ahead and do it because eventually you will and it'll force a wipe data. Might as well do it now before you install too much stuff.
You can leave root and custom recovery until the images show up if you are concerned about borking your system.
Click to expand...
Click to collapse
Not the unlocking. The rooting...
danvee said:
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
Click to expand...
Click to collapse
danvee said:
Not the unlocking. The rooting...
Click to expand...
Click to collapse
this is what i did, after unlocking and rooting and installing TWRP go into recovery and make a nandroid backup and keep it safe off the device, keep it on the device, so if you need it you can restore it
That's what I'd be do once rooted, but it's the risk of the process failing without the factory image as a backup....
For example, rooting fails, no custom recovery flashed, OS hosed.....
I like having that safety net....
danvee said:
That's what I'd be do once rooted, but it's the risk of the process failing without the factory image as a backup....
For example, rooting fails, no custom recovery flashed, OS hosed.....
I like having that safety net....
Click to expand...
Click to collapse
oh i gotcha, but you have your steps out of order. first you unlock the bootloader which doesn't flash anything to your device. then you push the recovery image to your device from your PC using adb. yes this step could go horribly wrong, but if you have everything in place you should be ok. this step is very easy as well, not much to screw up and doesnt take any time at all, none of this does.
then once the recovery is installed, reboot your phone so you know everything comes up fine. then reboot into the recovery and flash SuperSU and voila! you have a rooted phone. boot back into the OS and run an app that requires root (Root Checker is a good one to use as a test) to make sure all is well
i understand your concern, but of all the android devices i have owned, the new nexus has been by far the easiest one of all to root and it is meant to be that way so developers can play with it and customize it and learn from it
plus there's this too
http://forum.xda-developers.com/showthread.php?t=2381582
Midnight_Rider said:
oh i gotcha, but you have your steps out of order. first you unlock the bootloader which doesn't flash anything to your device. then you push the recovery image to your device from your PC using adb. yes this step could go horribly wrong, but if you have everything in place you should be ok. this step is very easy as well, not much to screw up and doesnt take any time at all, none of this does.
then once the recovery is installed, reboot your phone so you know everything comes up fine. then reboot into the recovery and flash SuperSU and voila! you have a rooted phone. boot back into the OS and run an app that requires root (Root Checker is a good one to use as a test) to make sure all is well
i understand your concern, but of all the android devices i have owned, the new nexus has been by far the easiest one of all to root and it is meant to be that way so developers can play with it and customize it and learn from it
plus there's this too
http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
these are all wonderful points, but it doesn't change the fact that google should have released the image already
indianajonze said:
these are all wonderful points, but it doesn't change the fact that google should have released the image already
Click to expand...
Click to collapse
agreed, but im sure they are waiting to make sure there are no major bugs reported so they can fix it first, then release it. it will be out
That would mean yet another update, then.
Midnight_Rider said:
agreed, but im sure they are waiting to make sure there are no major bugs reported so they can fix it first, then release it. it will be out
Click to expand...
Click to collapse
Google has never waited before. The only thing that generally holds up posting factory images are licensing issues. They posted the 4.3 images for the Nexus 4, Nexus 7 (2012), and various Galaxy Nexus devices. There is no reason they didn't post the Nexus 7 images unless it is licensing related.
bozzykid said:
Google has never waited before. The only thing that generally holds up posting factory images are licensing issues. They posted the 4.3 images for the Nexus 4, Nexus 7 (2012), and various Galaxy Nexus devices. There is no reason they didn't post the Nexus 7 images unless it is licensing related.
Click to expand...
Click to collapse
good point

[Q] jwr66y- few apps immediatly crash

Hey, I've done a full wipe as well as return to stock, then proceed to install jwr66y from scratch, after installing i proceeded installing twrp and superuser, everything seems to run fine with root and all. The only thing which has been bothering me is that some apps are displaying force close error immediatly after starting them. Examples are Adaway, Adfree and Yelp.
Anyone knows what's going on there?
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
CCDillon said:
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah i also installed though a Zip which was supposed to be vanilla with added busybox and root.
I had my nexus 7 running so i was backing up from there which fixed the problem. However i am really wondering why apps which were downloaded straight from google play messed around.
I hope they won't mess around later.
I was completely stock and the same thing happened to me. I had to erase recovery, data and boot loader through fastboot and then reinstall everything new from the factory image on Google's site.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Oh wow. I had to do that with the initial 4.3 release. Don't think I'll do it for such a minor update unless I have a lot of free time. Though, the software update notification is in the way most of the time.. In surprised this isn't affecting more devices.
Sent from my Nexus 4 using Tapatalk 4

[Q] Micromax Canvas Knight A350

I have rooted my Stock ROM, and i am facing boot loop issue. It sometimes get restart automatically or else get stuck while using it.
Can anybody help me for this..????
dinesh.malvey said:
I have rooted my Stock ROM, and i am facing boot loop issue. It sometimes get restart automatically or else get stuck while using it.
Can anybody help me for this..????
Click to expand...
Click to collapse
What did you use to root? Also are you using a custom recovery? Try flashing latest super user binaries with custom recovery. It should solve the problem.
I have rooted my phone with some Chinese application.
piyushdev said:
What did you use to root? Also are you using a custom recovery? Try flashing latest super user binaries with custom recovery. It should solve the problem.
Click to expand...
Click to collapse
I have rooted it with some Chinese application, it had some blue color jellybean sort of icon. Sorry i don't remember the name of that app.
But i remember the procedure what i used. It is as below.
I connected my phone to PC and run that application in my PC.
So after a while that application detected my phone, and it started root process.
First the same application got installed in my phone and then it rooted. It hardly took 2-3 minutes to root.
Then I installed superuser latest version manually, and updated the binary in normal mode. That's it.
But now i am facing some problems like when i open some particular app, my phone get stuck and i have to restart it. And it is working quite a bit slower as compare to earlier (before root).
dinesh.malvey said:
I have rooted it with some Chinese application, it had some blue color jellybean sort of icon. Sorry i don't remember the name of that app.
But i remember the procedure what i used. It is as below.
I connected my phone to PC and run that application in my PC.
So after a while that application detected my phone, and it started root process.
First the same application got installed in my phone and then it rooted. It hardly took 2-3 minutes to root.
Then I installed superuser latest version manually, and updated the binary in normal mode. That's it.
But now i am facing some problems like when i open some particular app, my phone get stuck and i have to restart it. And it is working quite a bit slower as compare to earlier (before root).
Click to expand...
Click to collapse
Although there is nothing that you seem to have done wrong, but a lot of chinese rooting apps install some bloatware in your phone, the performance of the phone should not be affected. Also do check once again if you have the root access using root checker app from the playstore. You also may have 2 different superuser apps installed, which might be causing the problem.
piyushdev said:
Although there is nothing that you seem to have done wrong, but a lot of chinese rooting apps install some bloatware in your phone, the performance of the phone should not be affected. Also do check once again if you have the root access using root checker app from the playstore. You also may have 2 different superuser apps installed, which might be causing the problem.
Click to expand...
Click to collapse
The application what i used was "iRoot", and i am using superuser with the updated binaries. But still it causes the problem of getting stuck. There are few apps like Solid Explorer, Gallery, and more get stuck while opening them and i have to restart the phone.
dinesh.malvey said:
The application what i used was "iRoot", and i am using superuser with the updated binaries. But still it causes the problem of getting stuck. There are few apps like Solid Explorer, Gallery, and more get stuck while opening them and i have to restart the phone.
Click to expand...
Click to collapse
Someone please reply to this...?????
dinesh.malvey said:
Someone please reply to this...?????
Click to expand...
Click to collapse
You should consider using custom ROMs.

Categories

Resources