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] Only emergency calls

Hi, I have a problem with my nexus s.
Since yesterday my phone is stuck on "Only Emergency Calls"
I tried an hard reset, i tried to flash another rom (i used to run cm 7) but nothing works.
If i insert another sim card (different carrier) in the mobile it works!
If i insert my sim card in another mobile it works!
That's very strange!

I got this trouble twice, whit CM7 and CM7.1.
Did you used power widget control to switch between 2G/3G on CM7? I did, and twice, the network gone k.o. Yesterday that happened again, and after a little bit of swearing, I tried a cache/dalvik wipe and a permissions fix, and now it seem to be ok. Of course, I'll never use that damned widget again.

Yes i used it.
But unfortunately with cache/dalvik wipe but the device is still stuck!

What happen when you boot your phone? It ask you for pin code? Have you tried to manually scan for available carrier and eventually set 2g or 3g through settings?

Yes it asks me for the pin code.
I tried to switch 2g/3g and airplane mode on/off but nothing change.
If i tried to scan for the available carrier it shows me my carrier but i can not catch it.
In the notification bar appears the network indicator without the X (when you run the phone without sim) so it's like it knows that there is a network but it can't catch it!

PS: I tried a sim with my same carrier (vodafone) and it doesn't works.
Other carriers works!

Could be the efs folder?
The imei looks good, is the same on the mobile's box

Flash a stock rom and then see whether it works. If it works then do a clean install of CM7, I had an data issue, My data din't work.
I did a full wipe and then installed a stock ROM, It started working/

I wipe data cache, dalvik cache, everything i suppose.
I tried to install a stock rom via odin.
But it doesn't works.

Flash a stock ROM for your phone from here in recovery,
http://forum.xda-developers.com/showthread.php?t=1063664
Do a full wipe before flashing. Don't use ODIN.

saranyan said:
Flash a stock ROM for your phone from here in recovery,
http://forum.xda-developers.com/showthread.php?t=1063664
Do a full wipe before flashing. Don't use ODIN.
Click to expand...
Click to collapse
why not odin?

Odin sometimes can terribly go wrong, That's why its advisable to flash stock rom from recovery,
Safest way.

Besides rom, have you tried reflashing radio?
Sent from my Nexus S using XDA App

saranyan said:
Odin sometimes can terribly go wrong, That's why its advisable to flash stock rom from recovery,
Safest way.
Click to expand...
Click to collapse
Ok, i hope nothing went bad with odin
gnaurittiello said:
Besides rom, have you tried reflashing radio?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I suppose.
When i flash the rom with odin I insert a file called mobile, is this the radio?
However how can i flash a new radio?

I never used Odin for Nexus S, so I don't know if it can cause issue with flashing. However, flashing recovery, rom, radio (even manually restore nandroid if you want..) is very simple with fastboot:
Code:
fastboot flash radio radio.img
If you haven't fastboot, you can follow this guide

flashed two different radios from modaco
XXKB3
XXKB1
Nothing change :|

It's strange..
You can try flashing last OTA update (2.3.6, GRK39F build, KA3 bootloader, KF1 radio) through CWM:
1) Install CMW using fastboot
2) Reboot into recovery
3) Wipe Data/Cache/Dalvik Cache and format System (mounts and storage=>format /system)
4) Install OTA update from SD
PS. I think you have i9020T or i9023, so that OTA will be fine. Instead, if you have i9020A, dowlonad this package .
PPS. I don't think it would make any difference, but I suggest you to remove SIM before flashing.

No way man, it doesn't works

Help! Trying to revert to stock rooted from CM10

I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.

How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.

mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?

Boot into recovery and wipe your cache and dalvik cache again

mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app

This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use

I still want to keep my phone rooted. This wont kill the root right?

No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner

Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):

I'm going to install cm10 right now them go back to stock rooted and see what's up with this

There's no issues going back and forth. You probably flashed a bad ROM

yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.

What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.

DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!

Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10

redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.

[Q] Accidentally wiped system, how to revert back to stock without losing root?

So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?

xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps

xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images

Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?

xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.

xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?

Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk

xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.

gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?

xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.

gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk

xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).

gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk

[HELP!] Not booting after stagefright update!

Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.

If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..

Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?

Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed

Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.

reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app

Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.

hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone

sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files

Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?

Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.