Related
My Wifi-Only US Xoom is rooted with the universal xoom root, and has the EOS-Wingray-60 Rom successfully installed, but everytime I try to download Gapps, this comes up:
How do I fix that?
EDIT: That is no longer the problem. Everytime I flash Gapps now, my xoom ALWAYS gets stuck on the dual core screen after reboot.
Double EDIT: I was too lazy to stock flash it, so I simply wiped everything again, downloaded EOS wingray 60, Then I wiped my cache and my dalvik (Not data), then reinstalled Gapps, and fixed permissions and it finally loads now. Thank ****ing god.
Can anyone help me with this please??
Slayergramp said:
Can anyone help me with this please??
Click to expand...
Click to collapse
Okay
1. Dont use v9 gapps you should always use latest v10.5 is the latest...
2. Check the md5 of the file
3. Wipe cache and dalvik cache
4. Install said gapps
5. Fix permissions
6. Win
Sent from my mind control device
Where's v10.5?
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Slayergramp said:
I still need help with this D:
I can get the EOS-Wingray-60 ROM to work, and then I fixed permissions, and then tried installing GApps and it's still (bad)!!!
Click to expand...
Click to collapse
Go to the eos rom.. There is a gapps link.. Click it and it will take you to all the gapps packages ... Download 10.5 check the md5
Sent from my mind control device
Goo-inside.me/roms/teameos/gapps
Download the most recent EOS gapps from there. The (bad) in your attempted install means the zip is corrupt.
Sent from my MB860 using xda premium
Alright, so my problem continues. I was running stock unrooted ICS, then flashes recovery. Then I wiped data, cache and dalvik. Then I rooted with the Xoom universal root. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, and flashes eos Rom 60. Rebooted, works fine. Then I went to recovery, wiped data, cache, and dalvik, successfully installed gapps 10.5 for the first time, it wasn't (bad). Rebooted, andddd stuck. After I rebooted in permanately stuck on the dual core Motorola logo thing. What did I do wrong?
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
okantomi said:
You need to flash the GApps file immediately after the EOS rom...no reboot first. This is a must.
Click to expand...
Click to collapse
When I flash them, is there anything I need to wipe or clear? Or do I leave everything alone?
God Dammit! This is pissing me off!!!!!!!!!!!!!!!!!!!!! It ****ing takes for ever to upgrade back to ICS when I have to flash the ****ing stock of 3.0!!!
I upgraded to ICS, after flashing 3.0, I flashed the R4c Recovery, I did a factory reset, and wiped Dalvik and Cache, then I installed the Universal root (Is there a different root I should use?), then I went back (Still in recovery mode) and did a factory reset, and wipe cache and dalvik. Then I install Wingray-60, then *immediately after* I installed Gapps v10.5!!!! I rebooted and my ****ING xoom is stuck on the dual core screen AGAIN!!!
WHAT THE ****.
Not quite sure what those first few steps were, but boot to recovery, go to mounts and storage and wipe system and cache, then go to the wipe menu and do a data wipe and dalvik wipe.
Then flash ICS and gapps.
Shouldn't have any problems after that unless your Xoom doesn't like ICS for some strange get reason.
Sent from my Xoom using xda premium
about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks
and to clarify , it was gapps 4.2.2
Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.
If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app
i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .
You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.
actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.
i figured out twrp. never gave it achance. ill see if that does the trick
tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks
Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?
Hey guys, I downloaded the official LiquidSmooth v2.7 installed it on my Galaxy S2 i9100 following the usual installation procedures. The problem is when I try to reboot it, it can't go beyond the new boot animation. I tried to re-install it but same problem persists. I would like to hear your advice, please.
LiquidSmooth Bootloop
spectator123 said:
Hey guys, I downloaded the official LiquidSmooth v2.7 installed it on my Galaxy S2 i9100 following the usual installation procedures. The problem is when I try to reboot it, it can't go beyond the new boot animation. I tried to re-install it but same problem persists. I would like to hear your advice, please.
Click to expand...
Click to collapse
Sounds like you have corrupt system files. You might need to start from scratch here. Try downloading the ROM again with a solid internet connection. A big factor is if you are coming from a different rom or stock android. Use Titanium Backup Pro or GO Backup Pro to back your phone up. The official Roms are from [goo.im] then navigate to your model make sure you have the correct one. Make sure you aren't crossing any data from a different rom including app data this can corrupt system files unless you are coming from a previous version of LiquidSmooth. If you are coming from a different rom you need to factory reset > wipe cache partition > then wipe dalvik cache all in the CWM recovery menu or whichever recovery you have then don't forget it to install your gapps zip. If you are trying to upgrade from a older version of Liquid Smooth before you install you need to wipe the cache partition and dalvik cache > Install Liquid 2.7 > wipe dalvik cache again > then install your gapps zip again I had to. If you are still having problems you might have to [format the sdcard] also in the recovery menu but can be risky. This is your last resort to try I've had to format mine before. Let me know if this helps. If not then you'll need to use a different rom or flash stock android back to your phone.
ive been running into a strange issue installing roms lately. I can install anything touchwiz no problem and they run great. but for some odd reason if I install any of the numerous aosp roms the just hang on first boot. ive tried almost every aosp there is and they all sit there and hang, ive even let a few sit for hours with no luck. yet touchwiz will boot fine in just a few minutes. anyone have any suggestions or ideas?
Have u done a clean wipe factory reset wipe delvk catche.. Wipe everything clean.. Some stuff from the tw roms could stay behind.. Wen ppl change from aosp rom to a tw rom they use synergy rom cuz it does a clean install .. I could be wrong about this
Just be sure to wipe data/cache. The ROM zip install erases system for u.
Sent from my SCH-I535 using Tapatalk 4
Erasing data problem
I have unrooted Verizon S3.
It was working ok until I decided to put some new ROM. I instaled Synergy S3 r420 rom. It worked OK, but did not have mobile internet. WiFi and mobile hotspot were working fine. I decided to put back my old system, not to mess around any more, and went into CWM mode.
After entering CWM I tried wipe out/factory reset but it stacked at Formatting /data
Previous formating of cache and wiping of Dalvik went OK.
Part of the message was E:unknown volume for path [sd/ext]
What di I done with my phone? Is it soft bricked or what?
I can still boot last ROM, and is functional
How can I return my phone to the state saved in my CWM backup ?
Thanks!
EDIT
I have tryed to instal a different ROM - Hyperdrive, and install went normaly. At the end asked me to reboot and I said OK. Then, upon rebooting, a Warning message appeared warning me that non Verizon softvare is detected and that I should take the phone to them.
Is there anything to do to reverse this state?
You need to use odin to restore stock
Sent from my SCH-I535 using Tapatalk 4
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app