[Q] Device Seems to be running Very slowly - Nexus 7 Q&A, Help & Troubleshooting

Hi there, since I updated (manually) to 4.2 I have noticed that my Nexus keeps giving me a message randomly Saying "Your Device Appears to be running Extremely Slow" or something along those lines?
I have also noticed abit of a laggy experience and the device struggling a little since the update
I updated manually using adb using:
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Which is the update I flashed.
After noticing the Message and the lag issue, I went back into recovery and tried to wipe cache.
Which changed nothing
Also, I now have no root and both toolkits report a successful root but it isnt.
What should I do?
Would a factory reset help? (Last resort? :/)
Thanks all, any answers appreciated !

Related

[Q] - Error when updating to 4.4 - Official

To my delight, I got the OTA update or whatever it is, the official thingie to update to 4.4, icon and all.
I start it up, it goes through the motions, then it gives me a nondescript error (( The little Android looked like how it did when it's awaiting a bootloader instruction. ))
Does this mean my Android stock is borked? Do I need to factory wipe? I am confused. I did, however, download the Google-based Nexus 2012 KitKat build and I attempted to ADB it, and it gave me yet another error, with this - E:Error in /tmp/update.zip.
Any help that can be given would be wonderful.
I have the same issue. I wiped the cache and done a factory reset but it didn't fix the issue. I downloaded Nexus root toolkit as it has a unbrick feature and ran that but it seems to have made it worse, I can no longer get into recovery.

[Q] Nexus 10 stuck - read only? I can't update or change anything.

Hey guys,
I'm experiencing a weird problem with a Nexus 10 that was gifted to me. For some reason the Nexus 10 can't receive any updates and reverts to it's last state after a reboot. That probably doesn't make sense so here's an example:
I turn on the Nexus 10. I change the language in the settings. I connect to wireless. I install apps. When I reboot the nexus 10 has no history these changes were made.
Wiping/factory reset from Recovery does nothing. I can select the option but when I turn the tablet back on there is still a completely configured profile with personal data present.
It's currently stuck on 4.2.2. When I try to install the OTA update the installer downloads, the tablet reboots, then no record of the install is seen.
Finally, I've tried to flash Google factory images via ADB and fastboot. But, I can't complete the install because the bootloader doesn't remain unlocked after a reboot so the install never finishes. It seems to me the tablet memory is stuck in a state of read-only.
It seems to me the tablet is stuck on Read-Only somehow... does anyone know what else I can do? I've never experienced this problem before. Most of my research indicates an eMMC problem?
Thanks!

No root access, cannot update, no way to fastboot.

Okay guys, I need your help. I wanted to return to complete stock and update to newest version. So I downloaded a stock ROM and let it flash the stock recovery. I got a notification for 4.3 update and went ahead and flashed that sucker. During the installation, up popped "Error". It stayed frozen on that screen, so I hard rest it, and restarted my nexus. Well, the installation went through fine. Disabled super user and went about trying to force the 4.4.2 update. Sure enough that kicked in as well. Now, I also got the error on installation of that as well, but this time, when I rebooted, it was still 4.3. I've gone through it about 10 times now. And it gives me the error every single time and remains 4.3. I did a little googling and found out how to get there error log, and it says unexpected content in boot animation.zip.
Unfortunately one of my data pins is busted in my Nexus's USB port, so connecting to PC is not an option for me. Plus my PC is down for the count until I can get a new motherboard in her. Is there anyway to obtain root without connecting to a PC on 4.3 or at least get the update to take?
Is there possibly anyway to wirelessly adb from another android device? Would that even help in my situation?
I've tried " root master" and it seemed to work, even made the Chinese root permissions manager(as a system app) for me, but I can't grant access to anything, nor am I even give the option to. Also, when I tried that, it kicked SuperSU out of system and into regular old data apps.
I suppose I can just stick with 4.3, but if you guys could, I'd love some help.

Trying To Recovery N10 (old version).

Hi guys,
I have searched around the forums and still unsure, weary of what to do. I got my nexus when they first came out. I used it for a while and eventually unlocked it so that i could get certain apps that needed root access. I dont think i flashed a custom rom on it though. I havnt updated android to 4.4 yet. Its been a long time since i updated anything. Hence the start of my dilemma. I went to backup my tablet. It told me SuperUser or the bootloader needed to be updated. So im like oh fine update. Tablet then restarts brings me to my boot screen and says downloading target do not turn off. Its been stuck like this and nothing happens. I held down the power and rocker buttons and got back to boot option screen. Here's where im lost and dont remember what to do. I have tried start, recovermode, restartbootloader, and nothing seems to work. They all bring me back to the dead little android guy ​
Here's the device info.
product name: manta
variant: wifi
h/w version 8
bootloader version: mantam03
carrier info: none
serial: ****
lock state: unlocked
reboot mode flag: recovery
I slightly recall when i first unlocked it using twrp or clockworkmod? I could be wrong. Either way i no longer have the rootkit nor the computer i originally used to unlock it. What software do i need to install to get me back up and running. I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Jshannon22 said:
... I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Click to expand...
Click to collapse
Considering that you have not used the N10 in a very long time your user data may not be all that important so here are some options.
1) You could flash the factory image for Android 5 which will wipe out your user data but give you a clean system including stock recovery.
2) You could flash the factory image for Android 5 but first you need to change the "flash-all".(bat,sh) script by removing the "-w" option which will prevent your userdata from being wiped. That takes some knowledge to edit the script but all you need is a simple text editor.
After either of those options you can root and replace your recovery. Root before you change your recovery or you will run into an issue due to specific changes in Android 5.
Instructions for installing a factory image.
Nexus 10 lollipop factory image.
How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)
Good Luck
I'm having similar issues! When trying to install lollipop over sideload it always errors and states not enough space.
I've formated all the data so I'm at a loss.
Any ideas to install lollipop?
Sent from my Galaxy Nexus using XDA Free mobile app
I'm concerned I've bricked the device. To be honest I'd be happy just to get kitkat back!
When the device powers up it automatically goes into a "no command" bootloop. With the android on its side with an exclamation point sign coming out.
Holding power and the volume it then goes to the android recovery where I have four options: reboot, apply update from adb, factory reset, wipe cache.
When in command, typing adb devices shows my device.
Using adb sideload I've tried to update, but I always get the error "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip
status 7 installation aborted"
So I downloaded the kitkat image and tried to run the script "flash all". But then the command screen just says "waiting for device"
After all that failed, I tried to hold power and the volume button when it restarts. That takes me to the odin screen, where it just states "downloading, do not remove target" The volume buttons do nothing. pressing the power button just reboots.
Any help would be much appreciated!
I have the same issue. There does not seem to be a way to install any (old) version of android. All I get is the same error message "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip status 7 installation aborted"
I did not root my device nor did I install a custom rom. I just started installing the OTA update and that's when the tablet got stuck in the boot loop thingy.
I also searched the internet and all I found were similar instructions on how to install factory images etc. using adb sideload.... as I mentioned, following those instructions lead to the error message.
I can' believe this.
Thanks for your help
I also have similar issue. I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device. As novice even I do not know to install ADB sideloaded.
Can you suggest how best I can revive N10?
Regards,
Guys,
I also had the exact problem. What finally worked for is to flash custom recovery (TWRP latest version) with "fastboot flash recovery <recovery.img>" command.
Then from the recovery I installed custom ROM (http://forum.xda-developers.com/showthread.php?t=1998585), as the official ROM also failed.
Hope it will help someone.
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
fliuwoek said:
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
Click to expand...
Click to collapse
No worries, glad it helped you.

M9+ Marsmallow random restart problem

Hi!
First: Sorry for any miss spelling.
I successfully installed Marsmallow on my device with a weird way, but I have a problem with it.
It turns on well and I can use it (no bootloop or freeze on HTC logo).
After a random amount time, it seemingly freezes and exactly 10 secs after, it restasts itself from the HTC logo.
First, my way of installing 6.0:
I experienced the 25% error when I first tried to install 6.0 with the legit OTA software upgrade with my Europe version M9 plus (I Don't remember it's original build number, but this is a European modell). So I started the trial/error way of upgrading.
First thing was, bootloader unlock, and factory reset through recovery.
Second was finding here on xda a RUU collection for this device here
And I downloaded this one:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_MR_HTC_Europe_1.85.401.6_Radio_1.1506V24P21.2005.0505_HT[W.T]_release_446584_signed.zip
I renamed and installed it with download mode.
I barely set it up, knowing what is my goal, and started OTA from there.
In short:
3 security update popped up for Lollipop, and then the first Marsmallow update.
It got through the 25% error, and installed without any problem, and with many update reboot.
After it booted, I checked if any more update was available and a second (security/bug fix) update popped up. (More on that later)
I did not updated thinking I got this far I might as well set it up (it is my daily driver).
I started to download my apps, but in the middle of it, freeze and automatic reboot.
I though it was okay, I continued the downloads and got into the settings to set that up... random freeze and reboot.
These happened random , not related to anything
I started to worry so I did that update.
After that, the problem remained, but less frequent and still seemingly unrelated.
What I tried:
Safe mode - nothing changed.
Factory reset - nothing changed.
First setup, then cache reset - nothing changed.
Keeping the phone's temperature low and monitoring it - nothing changed except it was cooler a bit of course.
Tried to block every possible app (even some system apps) without root access and using it a bit - nothing changed.
I tried these with the first 6.0 update as well.
This is where I need help. Any ideas what is the problem? I can post screenshots if needed.
I really like this phone despite the negative reviews and the lack of custom roms.
Thanks for every question and answer!

Categories

Resources