Related
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:
Verizon G2 - stock rom, rooted and had OTA updates blocked for at least 5 months.. 4.2.2 ver 11a build JDQ39B
restarted phone the other day and it would boot and you would briefly see your home screen and then boot loop to the white verizon logo screen. Every other time it looped, it would not show the home screen, just a blank screen. I did get it to boot to safe mode and unistalled a few apps I thought might be problems,,, didn't help. I discovered that if I quickly tapped the home screen in that brief 2 seconds during the loop, it would boot.
I really hate to undo tether, un-root and factory reset. I hate to go through updates and re-root and hack tether but I will as last resort.
Any thoughts on cause or suggestions?
Thanx
check lgocat for logs and try to eliminate the cause that way.
check kmesh in logs, dunno exact wording, but it also says something about boot there.
Use a tool like android tuner or something similar to disable startup stuff and try to eliminate that way
Weird G2 bootloop - got a fix?
Thanks for suggestions, I will give them a try.
Weird G2 bootloop - got a fix?
bachera said:
check lgocat for logs and try to eliminate the cause that way.
check kmesh in logs, dunno exact wording, but it also says something about boot there.
Use a tool like android tuner or something similar to disable startup stuff and try to eliminate that way
Click to expand...
Click to collapse
I didn't find any lgocat or kmesh folders/files anywhere
still stumped
r9ball said:
I didn't find any lgocat or kmesh folders/files anywhere
still stumped
Click to expand...
Click to collapse
try any logging tool from playstore. also try searching on how to obtain those logs. probably requires root. mind warrantee ofcourse.
at which point I would do a total complete clean install. that eliminates software issues. still there and you did not restore anything/install anything then its hardware.
Hi, I woke up earlier and then got that error message when I was trying to view images in the gallery of my Note 4.
I tried all the tips they had online but have not found one for the note 4 on 4.4.4
I still don't want to resort to do a factory reset.
Does anyone know any more ways to fix this? Thank you
Edit: I kinda fixed it after taking out a file via my laptop.
After my bone stock Huawei Nexus 6P (on Google Fi) got the OTA Android 8.1 update this morning, it shortly thereafter went into what I now understand is the Boot Loop of Death. This subsequently kicked my day off into Nexus 6P education. So TLDR, I've got a BLOD device. I can boot into recovery mode., but that's it. No other functions work other than "Power off". No recovery mode, etc. (everything else goes into boot loop). The phone is bone stock as was from Google. Not rooted. Bootloader is locked.
In the mean time, while I'm in the middle of hopefully getting warranty support from Google or Huawei, I've since replaced the phone with another store bought 6P. At this point, I simply need my data off the phone that wasn't included in my "restore from google" backup on the new phone. Files, images, video, sms text messages, etc.
Is it possible to boot to recovery mode, and then connect via abd and pull files off the phones internal storage?
Any help getting pointed in the right direction would be greatly appreciated.
Thank you very much.
I'm surprised your text messages where not backed up by Google. My last two restores from Google returned all my texts and phone calls. Are you running the same Android version that was on the boot looped 6p? Anyways not sure about the stock recovery but I know if you unlocked your bootloader and flash TWRP you could. However believe that wipes system partion so by by text messages but pictures, videos and downloads should be safe. Maybe someone else will chime in with some alternative methods. ?
Exodusche said:
I surprised your text messages where not backed up by Google. My last two restores from Google backup loaded them all up. Are you running the same Android version that was on the boot looped 6p? Anyways not sure about the stock recovery but I know if you unlocked your bootloader and flash TWRP you could. However believe that wipes system partion so by by text messages but pictures videos and downloads should be safe. Maybe someone else could chime in with some other ways .
Click to expand...
Click to collapse
As I understand it, if I were using Hangouts for sms messaging, it would have backed up. I was using the sms app instead. Unknowingly this was not part of the restore.
Same android version on the new phone as what was pushed to the one that is now boot looping.
I don't know (remember) if I unlocked the bootloader from the settings menu. I was hoping to get some expert opinions before charting down the adb path blindly.
Still reading / trying to figure out if that's something I can do.
iamQuads said:
As I understand it, if I were using some expert opinions before charting down the adb path blindly.
Still reading / trying to figure out if that's something I can do.
Click to expand...
Click to collapse
It was Android messages that Google restored for me maybe you didn't select it to back up or missed it in the restore options. Either way I hope you are able to get your important stuff best of luck mate. ?
Scratch the request. After a rather long argument with Huawei, the device was returned for a full refund.
So I learned a few things about my backup strategy, a hardware manufacture, and Oreo 8.1
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Yo. I got the same tablet bro. Been trying to figure out a custom recovery for her. A stock ROM would be great to have and I haven't been able to find one anywhere. Might I inquire as to where you found yours? It would be a huge relief to know I can fix it if I break it lol.
encryption
If you download the Lenovo MOTO smart assistant from Lenovo support it has a resque option. I also used that to root my tb-x104f. It downloads the original everything and if you take the boot image from the file it downloads and replace it in one that has been modified from magisk it will rescue it and you will have root also thatd what I did with mine
same problem here, reflashed with stock rom. and not resloved
frankieuk said:
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Click to expand...
Click to collapse
Did you fix this issue?
I am having the same problem.
Thanks
Same problem here (my error reads "Decryption unsuccesful", but I think it's the same as yours).
After a few tries, I believe that it is a problem with the internet connection. After the factory reset, if I skip the wifi connection step, it starts normally. And it is completely usable. I can load pdf documents or apks by the usb from a computer and it runs correctly. But whenever I try to set the wifi connection, it updates something and it causes the tablet that the next time I turn it off, I find the error on the picture when turning on. It asks for a password and no matter which password you enter, then it delivers this message.
In resume, right now it is a completely functional tablet if you NEVER connect it to the internet and load anything you need via usb or bluetooth.
I tried to reset it with Lenovo Smart Assistant, but the result is the same.
I am looking for custom roms to try if it's something about the stock rom, but I haven't found any. Can anyone reccomend me a rom for Lenovo E10 X104F 2GB?
Solution: (Worked for me)
Format Data as F2FS in TWRP. (Advanced Wipe)
Then reboot and wait.