Database Users

[Q] N7 4.4 update issues?

Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.

Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart

StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.

Yeah I have the latest OTA also, but I am still having the same issue!!

StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.

Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?

manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.

JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days

manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:

[SOLVED] Suddenly G2 boots only into recovery mode (loop)

Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.

Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.

I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.

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.

N910F problems - emmc read fail/ flashing stock no longer boots the phone.

Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.

engwee said:
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
Click to expand...
Click to collapse
read this - http://forum.xda-developers.com/note-4/help/note-4-issues-t3453048
there are links to more threads related to your issue.
Short version though:
it is dying. install wake lock application, add it to start up and set settings to #4.
accept the fact that your phone will eat the battery faster and one day WILL die completely

Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.

engwee said:
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
Click to expand...
Click to collapse
no need to be rooted, just download, install and set it to autostart

I'll try it if I somehow manage to get the phone working again, Smart Switch just fails now midway through.

golden_m said:
no need to be rooted, just download, install and set it to autostart
Click to expand...
Click to collapse
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.

engwee said:
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
Click to expand...
Click to collapse
yes, that is the app.
i've read it does not allow your phone to go to sleep mode.
drains the battery faster, but this is the only way to keep note 4 working without swapping its motherboard...

I have a question, my gf recently bought a note 4 and we may swap our phones and if we do, i'll flash CM and tinker with it because i find this phone very interesting, just a question, does this bug affect the N910C (exynos) model? Do i have something to worry about? Because the phone is warrianty protected and if it's the case, i don't want to break it. I hope someone will shed some light on this

Normal (rooted) phone, went full retard all of a sudden. Need help extracting data

Hello all,
I have a Nexus 6P, stock, rooted, with Xposed installed. The phone is completely functional for the better part of its life time since I bought it at release -probably first or second batch- (except for random reboots once daily on average, deemed by my investigation and exhausting all options to be a hardware issue or Xposed related).
Today, out of nowhere, the phone randomly rebooted itself and surprisingly it launched the "Android is starting..." dialogue which, if I'm not mistaken, optimize apps for ART. The battery was at 19% before it randomly rebooted, so when it started that optimize apps it went down to 0 (I assume) and it turned off. The charger wasn't connected correctly so that happened. Now the phone keeps restarting itself up to before it gives me the boot up decryption phase of the Data partition and reboots again. I assumed it can't decrypt Data for some reason, so I launched TWRP recovery to try and decrypt data and take a backup copy of my Titanium Backup folder on storage... Unfortunately, TWRP reports "failed to decrypt data" even though I'm 100% positive that the pattern is correct because I'm literally inputting it almost 10-20 times a day for the past two years...
Note: there seems to be a red blinking LED in the top left corner of the the phone. I never even knew this existed.
WHAT I WILL DO
I'll reflash everything system-wise.. I'm ok with that. I'll reflash the factory images, root it, install Xposed, no problem.
WHAT I NEED HELP WITH
I need to extract some folders from my phone storage, namely the Titanium Backup folder. I know the pattern protection of the encryption.
How do I go about doing this?
UPDATE:
Help is urgently needed now indeed: The phone doesn't even turn on to bootloader mode anymore now. It was able to, just half an hour ago. Now all I see it the red blinking LED.
UPDATE2: https://support.google.com/nexus/troubleshooter/3337561?hl=en-GB#ts=3337942
I'll try in 30 minutes.
Meanwhile, please help me with my original problem; extracting data.
I was thinking, if I boot into bootloader mode, can I use adb to pull any folder? If so, will that work in my case with decryption fails or Data partition doesn't seem to mount correctly?
Relevent:
Reviewing some other threads:
TWRP: 3.0.2-2
Bootloader: UNLOCKED
I did NOT upgrade to Android 7.0 nor was I planning to, until Xposed is available.
I did NOT flash anything **new** recently. However, Installed an Xposed module yesterday which caused a bootloop. I rebooted into TWRP, uninstalled Xposed, rebooted into system (which looped once, out of the ordinary) and I uninstalled that module, back to TWRP installed Xposed, and rebooted back into system. It worked for 12 hours and then what I wrote this post for happened as stated above.
UPDATE3:
15 minutes into charging... NOT EVEN A RED BLINKING LED ANYMORE.
Last? UPDATE:
Almost 1 and a half hour into charging and there is no longer ANYTHING. Is it hard-bricked now?
How the **** is this possible? I'm very much capable of solving any sof-brick but not a hard-brick...

Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck

KLit75 said:
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
Click to expand...
Click to collapse
I was indeed able to connect to a PC after I saw the problem (the bootloop essentially)... But I didn't at the time as I didn't have a plan of action as to how to get my data, so I turned it off. After sometime, I couldn't do anything with the phone... Not able to boot into bootloader, not recovery, the phone is essentially not turning on to anything, not even the splash screen; like a hard-brick. I'm not sure if this indeed is a hard brick as I've never seen any.. and don't currently know what to try next.

Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.

TnT_ said:
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
Click to expand...
Click to collapse
I honestly declared it hard-bricked.
Will Fastboot show any devices if the phone didn't show bootloader screen?
I'll try again today.
Update:
Didn't work.

check out my post
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311