Database Users

Broken Wi-Fi & Camera after TWRP

So I have the Razr M Retail, and I was rooted with Safestrap and running Hashcode0f's CM10, completely stable. Yesterday I decided to move to TWRP with the bootloader unlock, so I backed up my ROM to an external SD, and also separately used TiBu to backup my apps, and then used mattlgroff's Razr M Utility to unlock the BL and flash TWRP, which all went fine. Then I wiped internal storage and restored my backup from TWRP. It restored and booted fine, but the Wi-Fi and camera didn't work. The Wi-Fi is stuck to a toggled off position in the settings, and it's greyed out so I can't change it. If I click to see networks, it gets stuck in "Turning Wi-Fi on..." and I never see anything. The camera force closes with "Can't connect to camera." Since I hadn't been sure from the start that a restore would work, I was expecting trouble at this point, so I flashed a fresh version of CM10 from Hashcode's goo.im with the intention of restoring my apps with TiBu. It booted, but it seemed like it was running slow and the Wi-Fi didn't work, with the same issue as before. I didn't try the camera. I messed around with a few things trying to get it to work, and although nothing worked, I tried doing all of these separately and then reflashing:
a) Flash stock Moto 4.1.2 with the utility
b) Restore my stock rooted Moto 4.1.1 with safestrap (Just sayin, this gets weird, I end up with both TWRP and Safestrap)
c) Restore to b) and then restore my CM10 backup as a Safestrap ROM-slot 1
d) Dial *#*#526#*#* to reset Wi-Fi driver (did nothing afaik)
ALSO, I charged the phone last night and this morning at 8:30 it was at 100% battery. 3 hours later, with wi-fi, data, and GPS all off, and using the phone very very lightly, it was at 46%, so there is significant battery drain coming from somewhere.
Any help or suggestions would be greatly appreciated.

First off, you need to fastboot back to stock and start over. TWRP didn't break your phone, restoring a backup from SS did. If you flash a fresh CM10 build, not a backup, you should be okay and you should only get the bugs that are associated with CM10.
Ok, now you're going to ask why the backup didn't work. SS is designed to work on top of the stock boot.img, but CM10 has its own boot.img and that's the reason that CM10 builds were so buggy when used with SS. When you saved CM10 with SS, it probably saved the stock boot.img with it and the stock boot.img is not going to make CM10 happy. If you had saved a stock based ROM and tried to restore it, you probably would have been okay.
Now, with all that being said, if you fastboot back to 4.1.2, then you'll need to use a 4.1.2 based ROM or a CM build. If you want to use a 4.1.1 based ROM, you'll need to flash the 4.1.1 boot.img, prior to flashing the ROM. You battery is probably dying so quickly because CM10 is trying to fight with the stock kernel. You need to fastboot and flash clean.

Tmfle from
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\

VoraciousGhost said:
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
Click to expand...
Click to collapse
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.

RikRong said:
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
Click to expand...
Click to collapse
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.

VoraciousGhost said:
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
Click to expand...
Click to collapse
Yeah, definitely use Mic's builds, they are more current. TWRP shows that the sytem is mounted, but it is fact not. That's why you need to reboot recovery. When you reboot, you'll see that it's not mounted.

Mic's CM10 is very, very stable. Very good build.
10.1 is a little more buggy but still a good build.
Sounds like you're either using one of Hash's old builds or new, buggy ones. Mic is the way to go for now
Sent from my Nexus 7 using Tapatalk HD

[Q] Slimrom 4.3 freezes on reboot (mako)

Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks

ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.

abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.

bump

then, wipe data/factory reser and flash the stock rom. the rom might be the problem

davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.

Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)

OmniRom build2 - FC on boot NFC and phone service

Just flashed OmniRom beta 2 build together with gapps linked in the OmniRom thread and I get fc on first boot on both NFC service and one more android service something something - can't get passed the pop ups and a reboot into recovery is all I can do.
Wiped system using TWRP 2.6.3.2 and cleared cache after install - did another wipe after reboot just to be sure. I have seen this on other roms that I try to flash?
am I doing something wrong during the flash process?
Wipe (default twrp)
install rom and gapps
clear cache/dalvik
reboot
Tried different gapps with no success..
I tried to flash the first OmniRom (build 1) with the same problems and I also got CM start tutorial when I had flashed OmniRom?? So it feels like the wipe is not working as it should?

TheErk said:
Just flashed OmniRom beta 2 build together with gapps linked in the OmniRom thread and I get fc on first boot on both NFC service and one more android service something something - can't get passed the pop ups and a reboot into recovery is all I can do.
Wiped system using TWRP 2.6.3.2 and cleared cache after install - did another wipe after reboot just to be sure. I have seen this on other roms that I try to flash?
am I doing something wrong during the flash process?
Wipe (default twrp)
install rom and gapps
clear cache/dalvik
reboot
Tried different gapps with no success..
I tried to flash the first OmniRom (build 1) with the same problems and I also got CM start tutorial when I had flashed OmniRom?? So it feels like the wipe is not working as it should?
Click to expand...
Click to collapse
Where did you get the build? If you got a CM start tutorial then you definitely didn't wipe, and i wonder what exactly you're flashing? This would be anything official Omni

jerdog said:
Where did you get the build? If you got a CM start tutorial then you definitely didn't wipe, and i wonder what exactly you're flashing? This would be anything official Omni
Click to expand...
Click to collapse
Got the Omni from
http://forum.xda-developers.com/showthread.php?t=2517309
and the twrp from
http://forum.xda-developers.com/showthread.php?t=2469995
Others have succeeded using this so no clue what I'm doing wrong? I have flashed other roms, recovery works. Sometimes it seems like it is not wiping it all?

TheErk said:
Got the Omni from
http://forum.xda-developers.com/showthread.php?t=2517309
and the twrp from
http://forum.xda-developers.com/showthread.php?t=2469995
Others have succeeded using this so no clue what I'm doing wrong? I have flashed other roms, recovery works. Sometimes it seems like it is not wiping it all?
Click to expand...
Click to collapse
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.

jerdog said:
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
Click to expand...
Click to collapse
That would be awesome, thanks

jerdog said:
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
Click to expand...
Click to collapse
Think I found the problem - a "default" wipe in twrp won't do it - I had to go in to advanced and choose "cache,dalvik,data and system" now it works like a charm! Good to know for the future..

Having Problems in flashing roms

On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)

I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.

audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem

htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?

Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.

no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)

OmniROM Annoying Bootloop

I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks

matthewclso said:
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
Click to expand...
Click to collapse
you can...try this!

@halfdevil said:
you can...try this!
Click to expand...
Click to collapse
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.

FIXED
Turns out that I just had to flash the boot image through fastboot, works great now! Thanks

matthewclso said:
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
Click to expand...
Click to collapse
well you can try AOSP too, just remember all these projects are discontinued, so any support in case you break anything support won't be there..so always backup.
for AOSP!