Database Info

[Q] gapps problem

Hey,
I recently installed cyanogenmod 7 from this page:
http://forum.xda-developers.com/showthread.php?t=941346
Everything seems to be fine except for there is no market and I cannot link my google account to my phone under cyanogenmod 7. I tried through the settings/accounts area and also through the e-mail application but no luck. I tried reinstalling after wiping the cache, deleting the data but even that didn't work. I also tried to update using "gapps-gb-20110503-signed" and it says that it is successful but it still isn't fixed after that. I then tried to restore my old firmware then flash "gapps-gb-20110503-signed" and then reinstalled cyanogenmod 7 but I don't see any difference.
Any help would be much appreciated.
Regards,
Bob

You install gaps the same way you flash the ROM. Put it on your SD Card, reboot into recovery and install the zip. When you reboot, you should be good to go.

I'm not 100% sure but I think you need to flash gapps straight after you flash CM7, while still in recovery.
Sent from my Desire HD using Tapatalk

Thanks for your prompt replies, I think I should also add that I installed it the same way I installed the mod.

hmm, thats weird that it didnt work then. What phone and recovery do you have? After you flash the ROM, you can try to fix permissions before you flash gapps. If you have clockwork recovery, that is located under advanced. If that doesn't work, I would do a full wipe, reflash the ROM and then flash gapps again. Also, you may have a bad download of gapps..that happens quite a bit. Just trying to throw the different scenarios out there.

lowandbehold said:
hmm, thats weird that it didnt work then. What phone and recovery do you have? After you flash the ROM, you can try to fix permissions before you flash gapps. If you have clockwork recovery, that is located under advanced. If that doesn't work, I would do a full wipe, reflash the ROM and then flash gapps again. Also, you may have a bad download of gapps..that happens quite a bit. Just trying to throw the different scenarios out there.
Click to expand...
Click to collapse
Ok I will put everything I did. When I received the phone it was on android 2.0 imported from Italy. I then upgraded to 2.1 at which point this is all the information that I wrote down:
FCCID: IHDP56KC2 = GSM (Quad-Band GSM (850/900/1800/1900) & Dual-Band Euro 3G (900/2100))
A853
firmware: 2.1-update1
firmware configuration version: GAS_EMEA_USASHL00WNDIT_P031
baseband configuration version USASHLSMR2WNDITB1B806D.0R
kernel versioin 2.6.29-omap1 [email protected] #1
build number SHOLS_U2_02.38.0
bootloader 90.73
I then rooted the phone using universal androot. I then Installed RSD lite and used the SBF named "GOT_WINDITALY_2_2_1FULL.sbf" Then I installed open recovery and installed cyanogenmod/gapps. I tried redownloading the latest gapps from the cyanogen latest release wiki page (cannot link because my forum account is too new) but am stuck a bit. Could it be because I used a 2.2.1 sbf instead of the 2.0 that it came with?
So what would you recommend I do next? Should I download clockwork recovery now?

I managed to get it working! Here is how I did it. I re-downloaded cyanogen mod, I then re-downloaded gapps "gapps-gb-20110307-signed" and "gapps-gb-20110503-signed" tried both after clean wipe of dalvik cache data and cache partition and the "gapps-gb-20110307-signed" worked. I'm still not sure what the problem is but after trying again and again I can only assume the downloads must have been corrupt. Thanks for all of your help.

[Q] Flashing a new kernel onto an existing mod

Hi all,
I've recently tried to update the Matr1x kernel to the 9.0 CFS version on my already installed NSCollab 1.0.50 mod. Unfortunately, this didn't seem to go so well, because my Nexus S (i9023) entered an infinite reboot loop. I was a bit surprised since a lot of people seemed to have no problems with this kernel, and even though I'm new to this stuff, I tried to follow all the guides & tutorials around.
Anyways, here's what I did:
- I downloaded the kernel on my phone from this forum;
- I used ROM Manager, selecting the "Install ROM from SD Card" option;
- I let the "Wipe Dalvik Cache" option enabled.
Once I experienced the reboots, I dropped into recovery and tried to re-wipe the cache & the dalvik cache several times, with no luck. I then proceeded to restore the backup I made before doing this...
Did I do something wrong or stupid?

try flashing the rom(gapps if needed) then the kernel, then reboot.

simms22 said:
try flashing the rom(gapps if needed) then the kernel, then reboot.
Click to expand...
Click to collapse
Does this mean I have to wipe my data again?

I've never used ROM Manager to flash anything (I prefer to be hands-on and do it myself), but if you told ROM Manager to install a ROM from zip and fed it a kernel file, I can't see how that can possibly have a positive outcome hahaha.
Go into CWM, do a factory reset/full wipe and reinstall NSCollab 1.0.50. Once you've installed that, you can immediately install a custom kernel. Reboot, wait for it (the first boot always takes longer) and you should be fine.
Greetz
PS: Remember to always make backups with Titanium Backup, or even Nandroid backups if you're not sure about the actions you're about to do.

mux_ said:
Does this mean I have to wipe my data again?
Click to expand...
Click to collapse
no. go to recovery(dont use rom manager), flash your rom(and gapps), flash the kernel, reboot.

Well, since my system was still fully functional (as I said, I had done a backup from ROM Manager previously and restored it), I tried the manual method first; that is dropping into recovery, wiping dalvik cache, and using 'install zip from sdcard'.
Everything went just fine, and I'm running the Matr1x 9.0 CFS kernel without any issue for now!
Thanks a lot for the help.

flashing back to stock rom. Update: Bricked?!?! Update 2: Unbricked :)

Hey all,
I've tried the various custom rooms out there and I'm looking to flash back to stock rom. Is there a tutorial how to do this. I also noted that when flashing between roms the files in the directory don't get wiped and are still there? Is there a way to flash to all original tf300t like the day I first bought it?
Thanks!

Ok I think I may have screwed up my transformer.
I remembered I made a backup using twrp recovery and tried to restore it (all the options were checked for the restore: boot, system, data, recovery).
After the reboot it gets hung up on the asus sign with the swirly circles. I can still get to recovery so I tried to flash back to one of the custom roms (aokp build 38) but it gets stuck in the loading screen as well. Arggg.
Any suggestions? Is it bricked?

Ok, I did a factory reset and that looks like it fixed the problem.
Now back to my original question, does anyone know how to load everything back to stock?

yes, I am interested in this as well. Backed up my first stock rom before I rooted, and then after I rooted, and am ready to start flashing but wanna take the proper precautions. Thanks for you guys help

i have the same issue... i flashed aokp, but as i tried to restore my stock rom, it freezes at the second asus sign...
but, when i restore, and do a factory reset like the op, i can see the android welcome screen, but when i select my language, he reboots...

for me this worked.
1. get the latest .30 firmware from the http://forum.xda-developers.com/showthread.php?t=1697227.
2. copy to the sd card.
3. reboot to recovery.
4. wipe
and then flash zip and wait.

Anyone know if I can do this through twrp?
Sent from my LG-VM670 using Tapatalk 2

nihal1983 said:
for me this worked.
1. get the latest .30 firmware from the http://forum.xda-developers.com/showthread.php?t=1697227.
2. copy to the sd card.
3. reboot to recovery.
4. wipe
and then flash zip and wait.
Click to expand...
Click to collapse
by "sd card" he means internal storage. at the moment cmw does not support extrrnal sd cards.
Sent from my ASUS Transformer Pad TF300T

DMardroid said:
Anyone know if I can do this through twrp?
Sent from my LG-VM670 using Tapatalk 2
Click to expand...
Click to collapse
I had to flash CWM over TWRP to go back to stock.......TWRP gave me an error repeatedly.

Recovery Issue with both CWM and TWRP

I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log

Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.

grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.

I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.

Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.

I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.

I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.

Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.

grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app

Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2

runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2

[Q] phone will not boot after installing any kernel

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?