Database Users

[Q] eLocity just quit...won't boot up

I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
My a7 was running well for about a week since it quit...but today when I booted up device, it failed to recognize sd card...same card used for updating to mod 1.4...same card I've been using to listen to my music, etc...but now won't recognize...I've tried two different micro sdhc cards..formatted, reformatted, but device continues to display mount sd card...all else works fine! Does anyone have any new ideas? I can't even reinstall mod since a7 can't read my cards. Thanks for any input that would be helpful. I understand these issues are ongoing for many out there...what to do?

deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Mine has hung on a black screen on me. Seemed that it didn't fully come out of sleep mode.
I was able to recover by holding the power button for 15 seconds to hard power down. No data loss.

deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Exact same thing happened to me this morning. Tried to reset - not happening. Hard powered down. Don't have time to try anything else right now. I'm new to the forums and new to android. Wish me luck! I've been loving my A7, and much appreciation to Dexter and all the other knowledgeable hackers/modders/posters.

hey the same thing happened 2 me twice. Once the first day after i got it, since i had only had it for 1 day i wiped it reinstalled dexter's mod 1.41 and it worked. First app i installed was backup root. Now, a week later the exact same thing is happening. This time i dont want to wipe it because of all of the apps i have installed, games ive played etc. Any ideas? Could we just try reinstalling dexter's md without wiping? Or wiping reinstalling and recover from a backup?
Also have you installed busybox? I had just installed it both times before it failed to turn on. Maybe its just coincidence but you never know..
-D
Thanks to anyone who can help! and also thanks Dexter for all your hard work as well as everyone else that has contributed to the elocity, im lovin it! (when it works )

success!!!!
I got it to work! I don't have a permanent fix but if it happens again just boot into recovery and reinstall the dexter's mod update 1.41 and it works again! No wiping required. This isn't a permanent fix but it will work until we find one
-Dylan

Hasn't happened to me (yet) but I didn't upgrade to the newest ROM. I'm still using 1.3and it has been very stable. Only issue I've had was when I tried to use Killswitch to go to sleep mode when the cover is shut (great idea) but it didn't work and froze all except the live wallpaper. Weird.
Good luck, guys.

in the event it does happen to you, you might want to check out my apx thread for reflashing the factory firmware if you can't get your tablet unstuck. theres alternatives if you don't want to get stuck again.

The method you outline seems so complex...way above my abilities, but makes me wish I had followed though on some early programming training opportunities. That was the road not travelled.

okantomi; while i wouldn't encourage others to follow thru with procedures they fear would cause more harm, i would mention that if you google up my nick you'll find i've been able to do much w/ android software and devices while not knowing anything about programming. if i can do it, anyone can. i just wanted some themes for my phone.
i'm just an android hobbyist by night (and when i get a chance during the day), and a computer tech by day. no programming expertise, but i can reasonably reverse engineer and port software and components using simple file managers like ztreewin(trialware).
don't be mistaken that the folks out there providing you solutions necessarily know anything about programming or software development. just how to chef up files at different levels. i understand this doesn't go for everybody.

Thanks for the encouragement. I'm impressed with what you've been able to do. It is also nice to read upbeat comments about the A7. There is something sort of special about a device that you really almost have to build yourself... putting so much into it... biting your fingernails to nubs with each ROM flashing. You don't get as attached to any device that is 100 percent complete right out of the box, though of course there would be a lot less aggravation.

Nexus 4 TWRP encryption with password - I think the phone is gone

So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.

Bump

Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4

eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.

This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app

It's happening to me now too
Sent using T-Mobile S4 4.3 MK2

LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?

I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2

[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:

[Q] Diminished Storage Capacity and other update issues

Hello all.
I have an SGH-I337 and I am having some issues as of late.
The phone would not complete an update to the latest (4.4.4) OTA... and that's when my issues began.
I acquired this phone from a family member that got themselves an LG-G3. The power button was broken (would reboot constantly) and the card reader was busted. Nothing that $50 didn't fix... so after that, I received the phone and towel rooted. Decided to keep the phone stock so I could use it for work and leave my personal Nokia 1520 out of my work related tasks... so I removed Towel Root, and did OTA to NI1... but when the new one came in, the OTA would stop at 25% and reboot. On reboot, the phone would display the custom screen with the unlocked padlock... so I thought maybe the root/safestrap was not removed properly... so I decide to give it the Odin treatment.
First try, it stopped at writing.
Second try, more errors at the beginning, I can't recall them.
Third try, Odin stops at writing again.
So, I download Kies in hopes of using emergency restore... to no avail. Kies would simply lock up and tell me the phone was incompatible. I downloaded the previous version and no go. I then tried Odin just for S and Gs... and this time, it did work. I successfully installed . I337UCUFNB1_4.4_Stock_Odin_tar from here:
http://forum.xda-developers.com/showthread.php?t=2674223
Now, the phone reports only (and exactly) 16.00GB total storage available... and it STILL won't accept OTA updates. If it helps, which I don't think so, I am using Google Now launcher, and UCCW apps for customization, nothing else.
Help? How can I get the rest of my storage back and be able to get OTAs for when the STOCK Lollipop comes in?

I would Odin nb1 again them do a factory reset and clear cache right afterwards. Hopefully that'll get the storage correct.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I would Odin nb1 again them do a factory reset and clear cache right afterwards. Hopefully that'll get the storage correct.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I will try this and get back with the results. Thanks for your quick reply.

Update from RU1.1.112 to RU1.1.124 issue

USA user of Russian version yotaphone 2. Got notified three days ago of the 1.1.124 update but every time I tried the phone would reboot, fail to update, reboot back to android and re-download the update to try again. I made a video of what it did. After two days of trying and an unanswered tweet and support email later it magically corrected itself.
https://youtu.be/kG4tyuoOq0M
I did try copying the update from cache and sideloading. I'm rooted but with stock recovery. Recovery at least gave me a better understanding of what could have happened. Seems there was a problem with the zip. Apparently there was a problem with ALL of them since I re-downloaded it about 8 times before it worked!
I post this here as a reference.
Sent from my YD201 using Tapatalk

UK user of the same. Tried the OTA but was still on TWRP, didn't work. Then flashed stock recovery. Now it downloads, and that's kind of it: I press 'restart & install', it count down to restart then just switches to prior screen saying "your system is up to date". Going to try pulling it from the cache and adb sideload weh I get a chance.

How'd the sideloading go?
Sent from my YD201 using Tapatalk

radbme said:
How'd the sideloading go?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Any decent new features / battery improvements?

Just updating to say have got a new phone. Loved the Yota for the first year and it's use when outside is outstanding but have spent far too long trying to update and fix things, it doesn't really last more than a month without getting intolerably slow so I've upgraded. Might get around to sorting the Yota out but probably more likely to just reset it and save it for sunny days reading in the park or summit.