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

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..

[Q] LG G2 stuck in TWRP 2.7.0.0

Hey guys,
I am kind of a noob when it comes to android, but I'm decent with PC. I wanted to get Cyanogen mod 11, as I have used it before on previous Android phones and liked the features it had.
I was on the Kit Kat OTA update for the Verizon VS980 version of the G2. I downloaded TWRP v2.7.0.0 using AutoRec. I had put the newest nightly build of Cyanogen Mod 11 in the /sdcard file path. However, when I tried to install it using TWRP, I got "Skipping MD5 Check: no MD5 file found" in the prompt. It says the install is successful, however I am stuck in a boot loop at the LG logo. I read somewhere that totally formatting the data worked for someone so I gave that a shot and still nothing. I have cleared both cache and Dalvik Cache and completely wiped the phones memory.
I have been using ADB sideload to try to flash different ROMs to the phone, but no success. They all transfer to the phone successfully, but when the phone tries to apply them, I get the same response "Skipping MD5 Check: no MD5 file found". It says the file has been applied successfully but I am still stuck in the boot loop. I have also attempted what has been listed in this thread http://forum.xda-developers.com/showthread.php?t=2451696
The only part of my phone I still have access to is TWRP recovery mode.
Any help would be awesome. Just ask if you need any clarification.
Thanks.
Mike

The skipping MD5 check means nothing. Most ROMs I've seen say that. Which other ROMs have you tried? Since you're on 24A the ROMs have to be made with true 4.4 sources to boot. CM nighlies are not one of them. I suggest trying Mahdi. Download the newest ROM, patch and whatever gapps you prefer. Transfer them to the phone. Go to TWRP Advanced Wipe and select Dalvik, System, Data, Cache. Then flash Mahdi, Patch and gapps. It should boot up just fine.

JRJ442 said:
The skipping MD5 check means nothing. Most ROMs I've seen say that. Which other ROMs have you tried? Since you're on 24A the ROMs have to be made with true 4.4 sources to boot. CM nighlies are not one of them. I suggest trying Mahdi. Download the newest ROM, patch and whatever gapps you prefer. Transfer them to the phone. Go to TWRP Advanced Wipe and select Dalvik, System, Data, Cache. Then flash Mahdi, Patch and gapps. It should boot up just fine.
Click to expand...
Click to collapse
Ill give this a shot right now. I can do this through ADB sideload right? because thats the only way i have access to transfer data to the phone.

I just tried it and it worked! Thanks so much!
Why couldn't i have thought of that...

djilluminate said:
I just tried it and it worked! Thanks so much!
Why couldn't i have thought of that...
Click to expand...
Click to collapse
Glad you got it! Make sure the ROMs you flash from now on are specifically 4.4.2 sourced. If you don't see mention of it you can always ask in the thread. Most of the ones that are will say in the OP you need a true KK modem. If you want CM11 again you can go here http://forum.xda-developers.com/showthread.php?p=53232344. Its for 24a.

[GUIDE] Clean CM13/RR install with no FC and working Camera & SD. (ZE551ML)

A lot of people asked me why i had a fully working Resurrection Remix M on my ZF2 (ZE551ML) while actually they're having troubles with Camera (not working at all/FC), Gapps and/or with initial setup.
Well, actually it isn't really difficult.
I read some posts about CM13 ports for other phones, and I figured out that we had alot of common bugs, such as the Camera, for example.
Well, let's see how to solve this, starting from a simple and clean install.
Download CM13 or CM13 based ROM, and OpenGapps x86 for 6.0. KEEP SURE TO DOWNLOAD THE FULL PACKAGE (NOT THE STOCK ONE!!!) OR THE SMALLER ONES, KEEP SURE THEY DON'T REPLACE AOSP CAMERA WITH GOOGLE CAMERA!
Perform a full TWRP or Nandroid Backup.
Perform a full wipe (wipe data, cache, dalvik)
Install CM13/CM13 based ROM
Fix Permissions (for TWRP, it's under the Advanced menu)
Wipe Cache and Dalvik Cache
Reboot to System, then wait for the phone to boot. (~10min)
Config your phone, and now you'll see that Camera it's fully working now.
Reboot to Recovery
Install Gapps, then wipe cache and dalvik cache again.
Reboot to System and enjoy your CM13
EXTRA: To get the ASUS PixelMaster Camera working, you should download the flashable zip from THIS thread, and flash it in TWRP. DON'T TRY THE SUPER RESOLUTION MODE AT ALL OR CAMERA IMAGES WILL BE RENDERED GLITCHED UNTIL YOU RE-DO A CLEAN INSTALL!
Tested on ZE551ML with Resurrection Remix M v5.6.0r3 build 20151230, and CM13 NIGHTLY 20160102.
It's fully working, also with Retrica and PixelMaster Camera.
I'll post some screenshots soon.
When i'll find some friends with ZE550ML, i'll try this also on that version of the phone, but i'm pretty sure this will work, as the workarounds I just found are common, for other non-ASUS devices, which are also ARM!

Could you please explain how I would install TWRP? Seen alot of different guides, but most of them are old ones or leave a few questions still remaining...
Sent from my ASUS_Z00AD using Tapatalk

domacikolaci said:
Could you please explain how I would install TWRP? Seen alot of different guides, but most of them are old ones or leave a few questions still remaining...
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
You need to unlock your bootloader first. If you need help, we can talk via PM (Private Messages), because there are alot of threads and guides about this.

Added to index, thanks for your work!

Paranoid Android Discussion Thread

One of the most popular custom ROM projects of the last few years, Paranoid Android lost many of its core developers to OnePlus in February 2015. OnePlus recruited them to develop its in-house, following its breakup with Cyanogen. Predictably, PA releases slowed to a crawl, with the last major release, based on Android 5.1, [coming out in July. In October, project lead Matt Flaming announced what pretty much everyone had been suspecting for a while – the Paranoid Android project was on hold.
Now the Paranoid Android project is back into the spotlight, with over a dozen new team members and a new feature-packed release that’s been nine months in the making.
Features coming in this release, some of them familiar and some new, include an improved floating window mode, immersive mode, on-the-spot controls for the behavior of the notification dropdown, a polished quick settings re-order mechanism, battery style, an advanced power dialog, support for Paranoid OTA updates, a theme engine, and support for layers. For certain devices, including OnePlus and Oppo phones, the release offers advanced features like an enhanced kernel, advanced gesture control, and support for the alert slider and fingerprints scanner.:laugh:
Flashing Instructions:Using Twrp
Boot into recovery
wipe/System/Data/Cache/Dalvik
Flash latest Cm Nightlies
Let it boot
reboot to recovery
Wipe system/Data/cache/dalvik
Flash Pa and gapps
Reboot.
Win.
OnePlus One Paranoid Android 6.0 2016 ROM Review! Thanks to @nrp31
www.youtube.com/watch?v=V89296fkzc8
Paranoid Android g+ Page(post your bugs and comments):https://plus.google.com/+ParanoidAndroidCorner
Link: http://get.aospa.co/official/bacon
Source: Android Authority

Some revival. I flashed it and I'm stuck at the OnePlus logo. Apparently someone with a OP2 had the same problem and he fixed it by flashing the system partition before flashing the ROM. I did the same and my phone still won't boot up. Oh well.
I used both TWRP 3 and 2.8.7.0 and am also coming from an unaltered COS 13.

Same issue as @aarthyn. Wiped data, flashed it stuck at OnePlus logo. Used TWRP 2.8.6.1 and came from Sultan's Unofficial CM13 (6.0.1) May 26 build. Restored my backup and now it comes up with a SIM Card not found error.
Not happy.

ch4o5 said:
Same issue as @aarthyn. Wiped data, flashed it stuck at OnePlus logo. Used TWRP 2.8.6.1 and came from a custom rom. Restored my backup and now it comes up with a SIM Card not found error.
Not happy.
Click to expand...
Click to collapse
The download page is blank. Where did u download from?

Stuck on boot logo. Came from cos13. Wiped everything except internal storage.

ch4o5 said:
Restored my backup and now it comes up with a SIM Card not found error.
Click to expand...
Click to collapse
Oh great, I was hoping that wouldn't happen. Looks like I'll have to do the full fastboot works to make sure everything's the way it should be.
At least I know it's not just me.
pa1281 said:
The download page is blank. Where did u download from?
Click to expand...
Click to collapse
From here, but it looks like it's just not working on the OPO for now.

rom is awsm booted for me 9/10 battery life is good just need a bit improvement on charging and camera ! daily driver rom for sure!

aarthyn said:
Oh great, I was hoping that wouldn't happen. Looks like I'll have to do the full fastboot works to make sure everything's the way it should be.
At least I know it's not just me.
From here, but it looks like it's just not working on the OPO for now.
Click to expand...
Click to collapse
Thanks . how did u flash? Did u flash over COS?
---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------
Dhairya said:
rom is awsm booted for me 9/10 battery life is good just need a bit improvement on charging and camera ! daily driver rom for sure!
Click to expand...
Click to collapse
How did u flash? Ppl here are reporting that ROM is not booting..

Booted fine . coming from omni 6.0.
Here are some screens
http://imgur.com/a/j86BA

pa1281 said:
Thanks . how did u flash? Did u flash over COS?
---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------
How did u flash? Ppl here are reporting that ROM is not booting..
Click to expand...
Click to collapse
the normal way which we always flash was on cos 13 use twrp 3.0.0.1 and rom is ssly having dam slow charging thats the issue ! nothing else !

How to flash PA rom....
1. Boot into recovery
2. Flash latest CM nightlies (optional)
3. Factory reset
4. Flash PA rom and Bank's Gapps
5. Reboot into system
6. Setup your devices
7. Reboot into recovery
8. Flash SuperSu
9. Wipe Cache and Dalvik
10. Reboot into system
11. Done
Only PA rom and Bank's Gapps can be flash together....if you're planning to flash SuperSu or Custom Kernel you need to reboot into system first then boot back to recovery to flash them (wipe cache and dalvik after flashing them)....

People who are coming from CyanogenOS 13, check your partitions. They might be formatted to f2fs, which may be why your phones don't go past the bootanimation. Mine were formatted to ext4, and I had absolutely no problems doing a clean flash from SultanXDA's latest CM13 build.

iPusak Gaoq™ said:
How to flash PA rom....
1. Boot into recovery
2. Flash latest CM nightlies (optional)
3. Factory reset
4. Flash PA rom and Bank's Gapps
5. Reboot into system
6. Setup your devices
7. Reboot into recovery
8. Flash SuperSu
9. Wipe Cache and Dalvik
10. Reboot into system
11. Done
Only PA rom and Bank's Gapps can be flash together....if you're planning to flash SuperSu or Custom Kernel you need to reboot into system first then boot back to recovery to flash them (wipe cache and dalvik after flashing them)....
Click to expand...
Click to collapse
custom kernel which custom kernel would work here ! ?

#define said:
People who are coming from CyanogenOS 13, check your partitions. They might be formatted to f2fs, which may be why your phones don't go past the bootanimation. Mine were formatted to ext4, and I had absolutely no problems doing a clean flash from SultanXDA's latest CM13 build.
Click to expand...
Click to collapse
Take it you were on the June build of SultanXDA's build @#define? I was on the 26 May version and I got stuck at the OnePlus logo screen.

ch4o5 said:
Take it you were on the June build of SultanXDA's build @#define? I was on the 26 May version and I got stuck at the OnePlus logo screen.
Click to expand...
Click to collapse
Yes I switched from the June 3rd build.

Dhairya said:
custom kernel which custom kernel would work here ! ?
Click to expand...
Click to collapse
i have no idea which custom kernel work for this rom yet as i only tested this rom on stock kernel in PA rom....

iPusak Gaoq™ said:
i have no idea which custom kernel work for this rom yet as i only tested this rom on stock kernel in PA rom....
Click to expand...
Click to collapse
yeah charging sucks in the stock kernel need to know which are the customs one !

wow there's a 6/8 build for the OPO already at PA!

You need to change your filesystems to ext4 before flashing the rom.Otherwise it won't boot.But I cannot see any customization in the rom!

iPusak Gaoq™ said:
How to flash PA rom....
1. Boot into recovery
2. Flash latest CM nightlies (optional)
3. Factory reset
4. Flash PA rom and Bank's Gapps
5. Reboot into system
6. Setup your devices
7. Reboot into recovery
8. Flash SuperSu
9. Wipe Cache and Dalvik
10. Reboot into system
11. Done
Only PA rom and Bank's Gapps can be flash together....if you're planning to flash SuperSu or Custom Kernel you need to reboot into system first then boot back to recovery to flash them (wipe cache and dalvik after flashing them)....
Click to expand...
Click to collapse
can i use open gapps ??