Related
Anyone else having trouble installing anything. I have trying cyanogenmod and skyraider. Both wont let me install apps. Yet I can on my stock rom. I am rooted. This all started when I got the ota update popup.
Sent from my ADR6300 using XDA App
andrebigrod said:
Anyone else having trouble installing anything. I have trying cyanogenmod and skyraider. Both wont let me install apps. Yet I can on my stock rom. I am rooted. This all started when I got the ota update popup.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Do mean anything, or is it only specific apps? There is a way to disable the update pop up, so if you don't want that to pop up (assuming it still is...) do a search to disable that.
Can't install anything. What I ended up doing was installing stock letting the ota update then rerooting. But it still wont let me install anything when on another rom. Just my rooted stock.
Sent from my ADR6300 using XDA App
Before installing another ROM, did you do a full wipe of user data and dalvik cache? So if you go into the Market, does it download then say that it couldn't install? Did you try clearing the Market cache?
also...sometimes you have to unmount the SD card, install app, mount SD card. I have no idea why, but thats what i need to do for a lot of apps....quite a pain
Tried remounting sd card. Still same weird bug. All I can use is stock rom. Thanks for trying to help guess I'm stuck for now.
Sent from my ADR6300 using XDA App
Not sure exactly what happened. I was using the tablet and all of a sudden the bottom three buttons disappeared as well as the top bar. The system kept getting force closes. I rebooted and it just sat in the reboot mode. I tried to recover from the system but that is not working. I cant seem to get the system to mount via usb now. I am in clockwork mod v5.8.0.2 and do not see an option. If I could mount it I could put an img file back on and get it to work. Any help would be great.
xndrxw said:
Not sure exactly what happened. I was using the tablet and all of a sudden the bottom three buttons disappeared as well as the top bar. The system kept getting force closes. I rebooted and it just sat in the reboot mode. I tried to recover from the system but that is not working. I cant seem to get the system to mount via usb now. I am in clockwork mod v5.8.0.2 and do not see an option. If I could mount it I could put an img file back on and get it to work. Any help would be great.
Click to expand...
Click to collapse
You could try to flash back the stock software to see if that helps? Look here for some help.
Are you running a custom ROM or anything else? ALSO, once you do manage to get everything fixed, I would upgrade your CWM to the most current version 6.0.1.0 by flashing this in the older (5.8.0.2) version.
Sounds like it might be permission related, you could try a 'fix permissions' in recovery
Sent from my GT-I9300 using Tapatalk 2
Permissions did not fix it. I am trying to figure out the ADB.
xndrxw said:
Permissions did not fix it. I am trying to figure out the ADB.
Click to expand...
Click to collapse
Just do a bunch of reading! We were all noobs once
I keep getting the message "error: cannot load 'bootloader-grouper-3.34.img' . It seems like something is wrong with the file. Is there a way I could just flash another Rom on this way or even update the clockwork mod using adb?
xndrxw said:
I keep getting the message "error: cannot load 'bootloader-grouper-3.34.img' . It seems like something is wrong with the file. Is there a way I could just flash another Rom on this way or even update the clockwork mod using adb?
Click to expand...
Click to collapse
Did you download the nakasi file from the google site? You shouldn't have an issue with that. And you can update CWM using ADB, just check over in the Android Development section.
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Finally got it working. Now just need to install the new clockwork mod and move this thing to the GlazedJellyBean rom.
Boooty said:
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This is seriously not the advice to be giving out on the forums for a minor software issue on an unlocked and rooted tablet especially.
Boooty said:
A lot of people have been having problems with the nexus 7, best bet is return it and get a new one
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Worst advice i've heard, ever.
Sooo true.. You root/ unlock its yours NOT GOOGLES TO REPLACE
CharliesTheMan said:
This is seriously not the advice to be giving out on the forums for a minor software issue on an unlocked and rooted tablet especially.
Click to expand...
Click to collapse
similar issue with TWRP.. I did temp root thru nexus root/recovery app (thanks dev) Then pushed cwm recovery to data/media.. Booted back into temp cwm from above and flashed up to date cwm.. will stick with cwm for now..
good luck OP .
xndrxw said:
Finally got it working. Now just need to install the new clockwork mod and move this thing to the GlazedJellyBean rom.
Click to expand...
Click to collapse
i'm having the same issue. how did you finally get it to work? i've redownloaded the file a bajillion times and still nothing. HELP
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
MERKJONES said:
On AOKP 4.2.1 the phone app crashes when I receive a call. I've reflashed a fresh downloaded GAPPS on here and it does the same thing. When coming to this ROM I wiped all data and factory reset everything. I've tried that again and it's still doing this. Starting to get on my nerves. Anyone have this problem?
Click to expand...
Click to collapse
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
simms22 said:
try a different rom. you can also try to delete the data for the phone app(then wipe dalvik after).
Click to expand...
Click to collapse
I tried clearing the data from the phone app. I can reboot and clear dalvik again. I also flashed http://forum.xda-developers.com/showthread.php?t=2127498 and it's still acting up.
are you using any mods or themes?
simms22 said:
are you using any mods or themes?
Click to expand...
Click to collapse
Nope.
MERKJONES said:
Nope.
Click to expand...
Click to collapse
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
simms22 said:
did you dirty flash your rom or did you make a clean install? also, after you installed aokp, did you restore system apps with titanium backup? and, have you tried a third party phone app?
Click to expand...
Click to collapse
I did a clean install and manually installed all of my apps again. I managed to fix it by dirty flashing the 4.2 version of AOKP. However; my phone still has that random reboot issue. The thing that's odd is, when it comes back online it loses it's settings. So I'll have to setup Google Wallet and Google Voice again. My keyboard goes back to the default AOSP one.
I think I might just RMA this phone and start over. I do love it, and the negatives don't outweigh the positives.
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
molesarecoming said:
rma? dont.
wipe that thing clean with a factory reset. all your problems will be gone. then, if you like, start trying out roms again.
but bugging lg and nexus because you trashed your phone, thats not so cool. i can kinda understand samsung tries hard to lock their bootloaders sometimes.
links here: https://dl.google.com/dl/android/aosp/occam-jop40d-factory-ca7602f0.tgz
theres a batch file inside, make sure fastboot is around and click it (you must be in fastboot mode aswell). in a couple of seconds youre back to stock.
Click to expand...
Click to collapse
Um... I had the problem on stock 4.2 as well, factory from Google themselves. It rebooted at random for no reason. I have wiped everything... multiple times. It's still doing it.
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
same thing happened to me this whole week. I have been flashing custom ROM custom this whole week. People have been texting saying my phone dont work. I called in to re-fresh with TMobile network and still the same thing. I also got a new micro sim card still the same. i have to revert back to stock with root in order for the phone calls to work. i have been searching for a fix.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
MERKJONES said:
I thought it was the MicroSIM too - I got a brand new one with them, but nope - it's been all strange. Do you have 4.2 Stock rooted anywhere? I can only seem to find 4.2.1. I just wiped everything, restored factory etc etc and threw stock 4.2.1 on here, got the reboot issue. Phone has been working lately finally. I had to dirty flash AOKP 4.2.1 build-1 over build-2.
Click to expand...
Click to collapse
i just used the stock 4.2.1 ROM and kernel. I am using the backup I made for my phone when i first rooted my phone. I don't a copy of the that. try using WUG rooting kit. u should be able to load it in that way. good luck. i missing flashing custom ROM, but I need my phone call to work. and by the way my last custom ROM was AOKP.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can always follow efrants guide to go fully back to stock.
Sent from my Nexus 4 using xda premium
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
tokuzumi said:
Did you make any changes to the dpi in the build.prop? I remember messing with that on my nexus s on ics, and the phone app would crash.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No. And even on stock 4.2 I'm now having the sound disappearing problem. Where it'll just stop for no reason.
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
toanau said:
i am trying download a new gapp and see if that fix the problem. stock is very boring
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
MERKJONES said:
I tried to get a new gapps in case the download was bad. I'm just going to RMA it. I'm on 4.2.0 stock, unrooted with default everything and it's still acting up. Phone.apk works now; which is lovely, but it reboots at random and Music stops working after 3 minutes.
Click to expand...
Click to collapse
Everything is good now. Just flash new AOPK mr1 build 3 with newly doiwnload gapp. So far so good. Make sure you download the gapp from 12/12/2012
Sent from my Nexus 7 using xda app-developers app
I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...
Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.
netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.
patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!
Hey, I've done a full wipe as well as return to stock, then proceed to install jwr66y from scratch, after installing i proceeded installing twrp and superuser, everything seems to run fine with root and all. The only thing which has been bothering me is that some apps are displaying force close error immediatly after starting them. Examples are Adaway, Adfree and Yelp.
Anyone knows what's going on there?
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
CCDillon said:
Same thing with me, some apps just crash immediately. I'm glad I made a backup before I installed. I installed the ota through a zip to preserve root/custom recovery and also just installing it normally. Same thing happens with crashes.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah i also installed though a Zip which was supposed to be vanilla with added busybox and root.
I had my nexus 7 running so i was backing up from there which fixed the problem. However i am really wondering why apps which were downloaded straight from google play messed around.
I hope they won't mess around later.
I was completely stock and the same thing happened to me. I had to erase recovery, data and boot loader through fastboot and then reinstall everything new from the factory image on Google's site.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Oh wow. I had to do that with the initial 4.3 release. Don't think I'll do it for such a minor update unless I have a lot of free time. Though, the software update notification is in the way most of the time.. In surprised this isn't affecting more devices.
Sent from my Nexus 4 using Tapatalk 4