Database Info

[Q] v21y/GB 2.3.4 update causes apps to not be able to install/update

I recieved the OTA update for the G2x to the latest v21y firmware and Gingerbread 2.3.4 OS. Everything seems to have gone fine, except that now in Google Play apps it gives me the following error when trying to install or update *any* app:
'Error downloading "xxx". There is insufficient space on the device.'
Of course, I have an additional 8 GB micro SD card that is almost totally empty, and the internal phone storage has 3.2 GB available. The phone memory lists 0.94 GB available as well.
I followed the usual advice of clear data / clear cache for both Google Play and Download Manager. I unmounted/mounted both phone and SD cards. I turned off the phone, pulled the battery for a bit, took out the external SD card, put the battery back in, and booted back up. I rebooted a bunch of times. I put the external SD card back in. I cleared off extra crud from phone storage via a file manager, and I cleared caches on all installed apps.
This has never happened before, and directly after the update it has happened 100% of the time I have tried.
Any ideas? Is this happening to anyone else who got the update? (I'm completely on stock, btw, still not out of warranty.)

Clear market apparently cache/data
Sent from my LG-P999 using xda premium

kwes1020 said:
Clear market apparently cache/data
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
mikefarny said:
I followed the usual advice of clear data / clear cache for both Google Play and Download Manager.
Click to expand...
Click to collapse
Isn't that it? Is there something more that constitutes clearing market cache/data?

mikefarny said:
Isn't that it? Is there something more that constitutes clearing market cache/data?
Click to expand...
Click to collapse
Oh reading fails me sometimes. Try wiping cache and dalvik in cwm maybe.
Sent from my LG-P999 using xda premium

kwes1020 said:
Oh reading fails me sometimes. Try wiping cache and dalvik in cwm maybe.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Does that require rooting? I haven't installed CWM yet, as I was holding off on all the experimentation until my year was up.
If there's no other usual thing to try, if T-mo doesn't come back with a reasonable response I suppose that's the next step.

mikefarny said:
Does that require rooting? I haven't installed CWM yet, as I was holding off on all the experimentation until my year was up.
If there's no other usual thing to try, if T-mo doesn't come back with a reasonable response I suppose that's the next step.
Click to expand...
Click to collapse
No it requires Nvflashing cwm. But that will ruin your "warranty" on a end of life phone
Sent from my Galaxy Nexus using xda premium

Or a factory reset beofre rooting, although if you factory reset might as well root the phone lol.
Sent from my LG-P999 using xda premium

mt3g said:
Or a factory reset beofre rooting, although if you factory reset might as well root the phone lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
You can factory reset without root. That's what T-Mobile will tell you to do anyways. I've went through six g2x in the past two weeks...that's their answer to everything lol
Sent from my Galaxy Nexus using xda premium

I'm aware of that, just saying that's an option.
Sent from my LG-P999 using xda premium

mt3g said:
I'm aware of that, just saying that's an option.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I root everything I get on day one. Nothing stock and limiting my user options appeals to me. You can always revert to stock or if you hard brick no one could tell anyways.
Sent from my Galaxy Nexus using xda premium

So a factory reset fixed it. I didn't have to wipe the phone and external SD, and so I'm just reinstalling apps and setting up a few of them. This was a good time for some spring cleaning anyway, I suppose.
It was probably some stupid permissions thing, but without root I can't even fix that.

mikefarny said:
So a factory reset fixed it. I didn't have to wipe the phone and external SD, and so I'm just reinstalling apps and setting up a few of them. This was a good time for some spring cleaning anyway, I suppose.
It was probably some stupid permissions thing, but without root I can't even fix that.
Click to expand...
Click to collapse
U got the ota? Nandroid it, and send it to kwes
Sent from my LG-P999 using XDA

What is this update supposed to accomplish anyway? I'm rooted and trying ROMS pretty much every week (since no ICS rom works for me as a daily driver). Should I / can I do the update to 21y?

V21y 2.3.4 Rooted Touch Key lights
so everything else works fine when it comes to rooted app root request, but for some reason when a touch key light app request permisson it can do the job of adjusting the touchkey brightness, however the screen becomes very unresponsive, to the point where you cant slide left and right... I have run out of ideas as to why this is? has anyone else experienced this? I like to be able to turn that brightness down

Wiping cache and dvalik in twrp

Is it just my phone or does it take absolutely ages?
Sent from my Nexus 5 via Tapatalk

Nope it's not just you.
Sent from my Nexus 5

Good! Lol. Cus on my Xperia its a few seconds of a process!
Sent from my Nexus 5 via Tapatalk

Same for me! Takes a good few minutes :/ On my Nexus 4 it would be a couple seconds!
Must be something to do with Android 4.4 I assume?!

Every time I do it, wipes my imei and I have to flash the factory image...I'm actually looking for a twrp flashable cwm file if that makes any sense
Sent from my Nexus 5 using XDA Premium 4 mobile app

mrakifa said:
Every time I do it, wipes my imei and I have to flash the factory image...I'm actually looking for a twrp flashable cwm file if that makes any sense
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haven't seen a zipped cwm for the N5 yet. Why not just flash the .img in fastboot?

I just load up fastboot in my computer and
Code:
fastboot format cache
takes 3 secs
and format data separately in recovery mode....

george241312 said:
I just load up fastboot in my computer and
Code:
fastboot format cache
takes 3 secs
and format data separately in recovery mode....
Click to expand...
Click to collapse
Lol. Not with my laptop! It takes half a day to turn on
Sent from my Nexus 5 via Tapatalk

MattyPW said:
Same for me! Takes a good few minutes :/ On my Nexus 4 it would be a couple seconds!
Must be something to do with Android 4.4 I assume?!
Click to expand...
Click to collapse
It took several minutes also for me. Really awkward. With my previouse phone, LG p880, it was a matter of few seconds.

Probably the best part of 10 minutes to wipe cache/dalvik for me today!

Its a know issue with the N5. I believe its hardware related. TWRP devs will figure it out.

eep2378 said:
Its a know issue with the N5. I believe its hardware related. TWRP devs will figure it out.
Click to expand...
Click to collapse
Yes, it is. And there is a workaround for that issue: Go to the TWRP settings and activate "format rm - rf", so your wipe takes normal time as known.
You can find more about that in the TWRP Nexus5 main thread here .
Regards
Koetermann

For me personally, wiping the cache entirely deletes my internal storage so I would avoid it at all costs until there is an update..

Ben36 said:
Is it just my phone or does it take absolutely ages?
Sent from my Nexus 5 via Tapatalk
Click to expand...
Click to collapse
It takes my device a little while to wipe via TWRP.

scottdouglasdick said:
For me personally, wiping the cache entirely deletes my internal storage so I would avoid it at all costs until there is an update..
Click to expand...
Click to collapse
Such thing never happened to me. Formatting cache takes like 3 minutes for me, but it doesn't do any awkward. Unless you reboot while formatting ofc.

I'm avoiding wiping cache in TWRP at the moment...
first time i did that it borked something and i couldnt even switch airplane mode off or open play store when i got wifi on etc...wasnt that nice

Koetermann said:
Yes, it is. And there is a workaround for that issue: Go to the TWRP settings and activate "format rm - rf", so your wipe takes normal time as known.
You can find more about that in the TWRP Nexus5 main thread here .
Regards
Koetermann
Click to expand...
Click to collapse
Yep. Everyone should use this advice.
Sent from my Nexus 5 using Tapatalk

mrakifa said:
Every time I do it, wipes my imei and I have to flash the factory image...I'm actually looking for a twrp flashable cwm file if that makes any sense
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which factory image do you use? I just ran into this issue and it's driving me nuts.
I wish I would have found this thread sooner. I just wiped my internal storage and IMEI doing this. I have a backup of my IMEI, but restoring it with TWRP doesn't seem to do anything.
Will restoring the factory image fix this, or do I need to do that and restore this backup?

SO if you change it to rm-rf it doesn't bork your cell connection? I know it'll wipe faster but still leary on cell connection. Or is it that this only happens if you make the mistake of rebooting instead of waiting???? I'm wanting to jump on SlimKat and coming from an Evo LTE the procedure to clean wipe I'm familiar with is wiping system/data/cache/davlik cache so I've been holding off worried about the cache part. I've been using 2.6.3.2

Why would wiping cache screw up your cell connection? And how does this wipe your entire phone?
sent from my beantastic almost retired Bionic

(Q) (Help) Problems flashing Roms - can't mount system

Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would try: fastboot flash cache cache.img. use cache.img from the 4.4 factory image.

golem95 said:
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one
Click to expand...
Click to collapse
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app

I've used cataclysm rom with franko kernel and have gotten 24 hours with over 7 screen on

nelomen said:
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wow, 5hrs i get barely 3h +/-

golem95 said:
wow, 5hrs i get barely 3h +/-
Click to expand...
Click to collapse
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Maybe u must change ur cwm
Sent from my GT-S5360 using xda app-developers app

nelomen said:
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
(not sure if pics attached but they are of my 5hrs screen time)
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk

OptimusVDarwin said:
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I've never tried that but am willing to give it a shot after I finish my testing of battery life on stock compared to custom roms.
For some reason I am getting about 2 hours more screen time with stock then with custom rom.
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] Any way to recover lost EFS?

Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.

Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.

not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app

ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.

_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go

So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk

Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox

TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk

Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though

ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.

_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:

I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app

Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )

ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app

_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .

the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app

Need Help asap!!!

Last night i tried to flash purity kernel on my nexus 5, it rebooted fine. then after about 5 mins it rebooted again, this time for only about a minute. so i rebooted to recovery, then reflashed faux kernel. ever since then, no matter how many times i wipe cache and dalvik cache, it wont reboot. it goes to the 4 circles thing after the google logo, but never restarts. I've reflashed my rom, and the kernel several times. I'm in the army and currently over seas so this my on;y way to talk to my family besides borrowqing my friends phone. any help is appreciated

What are you wiping prior to reflashing your ROM and kernel?
sent from my Hammerhead Nexus

just cache partions and dalvik cache. incase it does reboot, i dont want to lose all my seetings and mods and such

Sounds like you may need a complete wipe(excluding internal storage). Then reflash your rom
sent from my Hammerhead Nexus

****. thats what i was hoping i wouldnt have to do. thanks for the help anyways

Please could you use more descriptive thread titles moving forward?
Sent from my Nexus 5 using Tapatalk

I will next time. Sorry
Sent from my Nexus 5 using xda app-developers app

Problem solved. Please delete
Sent from my Nexus 5 using xda app-developers app