Database Info

[Q] Cyanogen Did Not Work No Service

Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work

lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
Click to expand...
Click to collapse
Anybody?

I'm a beginner myself, and i do not know much about installing custom roms on samsung phones, but maybe you did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. my last guess would be that you need to also install a baseband perhaps. all this information should be there in the galaxy s3 section of the forums.

ishaang said:
did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. .
Click to expand...
Click to collapse
Hey there, first off, thank you for replying.
I didn't manually use odin or other flashing software to flash the ROM. Unlike the rooting method (which went smoothly) I used the cyanogen mod installer. The installer itself said that cyanogen was installed successfully, but it was not. After it said this, my screen (on the phone) turned off, and I was brought to a fresh install of touchwhiz. I've actually fixed the networking issue by flashing touchwhiz stock,but that still doesn't explain why my CWM backup wasn't working.

I see...I haven't used the cyanogen mod installer myself so cannot say...
What I suggest is that, if you're up for trying again, to manually flash a rom - either Cyanogenmod or any other. There seem to be a lot of good roms available for your phone, and whichever rom you choose will come with instructions for how to install. The usual method will involve the following steps as far as I know:
- Root
- Unlock Bootloader
- Flash Custom Kernel with recovery
- Flash ROM
- Flash GAPPS
These steps are not difficult at all as long as you follow the instructions for your specific phone. I have a Sony Xperia SL and thats how I installed a custom rom on it many times. Sorry I could not help much not knowing Samsung procedures but good luck!

lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work
Click to expand...
Click to collapse
OK,
Download stock ROM for your device from Samsung-updates.com according to device model and region.
Then flash it with Odin.
Good luck

Oppo N1 Problems. Please, Please help

I recently bought an Oppo N1 off of Swappa. I just got it today and its been one problem after another. Heres the story...
Rooted with Towelroot and installed Super SU/binary. Rebooted. The phone was running the stock Cyanogen 10.2 but it told me that CM had an update, so I figured id go ahead and update that aswell. It downloaded and installed but when it rebooted, the phone is just stuck on the OPPO screen. I can get into the recovery but I have absoutley no idea where to go from here. I've tried installing other versions of CM11 but it just says installiation failed. Still stuck on boot. It is also getting stuck and staying black and im having to leave it sit for awhile before it will boot. I'm literally begging anyone to help me out here. I'm lost. I will be closely monotoring this thread
After some research, apparently CM11 needs a custom recovery installed which i do not have. Is there a way i can install TWRP, or possibly revert the N1 back to 10.2???
Please, somebody help me

Having real trouble updating to Lollipop (recovery help?)

Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.

tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.

The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.

Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !

OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse

Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.

[Solved] Not Bricked yet.. Need assistance

Brief back story goes like this. Working TF300T running JB, was running slow and laggy so it seems a good time to flash something new. I'm no android/linux pro but I have a good base knowledge (you may question this statement later) . Successfully unlocked and flashed CM12 and TWRP. Tablet ran ok, sometimes significant lag, updated to a few different nightlies, then eventually decided to go back to stock. This is where it all went wrong. I followed the instructions here on XDA by d_crossfader. The flash seemed to go as expected, wiped cache/dalvik, rebooted. Loaded up to stock JB but no wifi, rebooted, all went bad. Stuck at the silver ASUS with spinning dots screen.
here's what working at this point.
I can load to fastboot, recovery etc, and have re-installed TWRP, the latest 2.8.1 failed install, but 2.6 is working (since I've read that this rev has issues).
I went back to the CM12.1 ROM I had working and it seems to flash fine but GAPPS fails, gives 'E: error updating binary in zip' for /boot and /recovery.
I think I've exhausted my abilities so it's time to call in people with actual skills.
What should my next move be? I'd be happy with stock or custom ROM's just like to get it back to functioning.
Thanks

Hardbricked Moto G after CM 12 Nightly Update (Did not downgrade to KitKat)

Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks

Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic

motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far

Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?

Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.

CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.