Just recently the CM14 nightlies have been put up for this phone. I'm currently running CM13 and was wondering if it's possible to "dirty flash" CM14 or alternatively wipe everything and flash a backup of my data?
Do a full backup with cm
13 in twrp then try a dirty flash up to cm14.1 if it doesn't work do a full wipe and Flash cm14.1 then do a restore of data from cm13 backup
Sent from my iPhone 4s using Tapatalk I also own a g900v
[email protected] said:
Do a full backup with cm
13 in twrp then try a dirty flash up to cm14.1 if it doesn't work do a full wipe and Flash cm14.1 then do a restore of data from cm13 backup
Click to expand...
Click to collapse
Okay, thanks!
The guide Says To Flash Gapps At The same time.It's a little buggy though. I'm having screen rotation issues.
It is in nightly status right now it won't be stable till a snapshot build comes out
Sent from my iPhone 4s using Tapatalk I also own a g900v
I can't enable wifi after Updated to CM14, clean install (cm13 to cm14.1).. Flash CM14.1 rom and then reboot to recovery mode again and installed GAPS, but wifi couldn't be enabled by any trial.. I went to back to CM 13.... Will wait some more time...:crying:
You did it wrong you flash ROM then immediately nougat gapps in custom recovery do not reboot in between
Sent from my Nexus 4 using Tapatalk
Win0416 said:
I can't enable wifi after Updated to CM14, clean install (cm13 to cm14.1).. Flash CM14.1 rom and then reboot to recovery mode again and installed GAPS, but wifi couldn't be enabled by any trial.. I went to back to CM 13.... Will wait some more time...:crying:
Click to expand...
Click to collapse
There's a new nightly and wifi "works", but if you reboot after the initial boot after installing the zip it doesn't work anymore. Using cm-14.1-20161130-NIGHTLY-kltevzw.zip
Related
I'm currently running cm 13 20151211 nightly on my D802. When i try to flash a new nightly in twrp it's stuck on the flashing screen. I've let it flash overnight and it was still flashing in the morning. When i reboot the device using the button combination it boots back into cm 13 20151211 nightly with xposed still installed so it hasn't even touched the system files. I'm using the latest blastagator twrp.
MrJodroid said:
I'm currently running cm 13 20151211 nightly on my D802. When i try to flash a new nightly in twrp it's stuck on the flashing screen. I've let it flash overnight and it was still flashing in the morning. When i reboot the device using the button combination it boots back into cm 13 20151211 nightly with xposed still installed so it hasn't even touched the system files. I'm using the latest blastagator twrp.
Click to expand...
Click to collapse
Maybe bad download redownload
I've already downloaded the nightly multiple times, using the cm updater and using chrome. I also tried downloading using a pc. Nothing worked.
Sent from my LG-D802 using Tapatalk
MrJodroid said:
I've already downloaded the nightly multiple times, using the cm updater and using chrome. I also tried downloading using a pc. Nothing worked.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
it shouldnt take more than 5 min to flash maybe even less then 5 min..
are dirty flashing?? if so why not try a clean install. deleting all.... or maybe go back to stock lollipop and start from scratch..
raptorddd said:
it shouldnt take more than 5 min to flash maybe even less then 5 min..
are dirty flashing?? if so why not try a clean install. deleting all.... or maybe go back to stock lollipop and start from scratch..
Click to expand...
Click to collapse
I made a twrp backup of my rom, wiped data, system, cache and dalvik cache. Then I tried to flash the new nightly and succeeded. Then I flashed the gapps and did a restore of my data. The rom booted perfectly and is running smootly now. Thank you for your help!
Hiiii
MrJodroid said:
I made a twrp backup of my rom, wiped data, system, cache and dalvik cache. Then I tried to flash the new nightly and succeeded. Then I flashed the gapps and did a restore of my data. The rom booted perfectly and is running smootly now. Thank you for your help!
Click to expand...
Click to collapse
glad you got it back working.. youre welcomed.
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Chikyu Tenshi said:
So today I went from stock 5.0.1 to CM 12.1 Nightly (20160110) but gapps keeps crashing which makes my phone semi useless
First Things first
1. Flashed TWRP using Odin
2. Went into recovery and wiped Data and System
3. Installed CM 12.1
4. Installed GApps
5. Wiped Cache/Dalvik and rebooted
Phone boots up normally, And after unlocking the screen a stream of errors emerges, Not sure if i'm using the right gapps or not
Any help is much appreciated
~Chik
Click to expand...
Click to collapse
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
Try these gapps:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
You need to perform a full wipe though.
Lennyz1988 said:
Did you by any chance use Opengapps? Opengapps is like a hit or miss. Some days they work and some days then don't.
You need to perform a full wipe though.
Click to expand...
Click to collapse
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
You need 5.1 gapps then.
Chikyu Tenshi said:
Yes I did try Opengapps which also didn't work
Edit: The gapps is 6.x.x while my phone is 5.1.1, That won't break my phone will it?
~Chik
Click to expand...
Click to collapse
My bad. Here is also another gapps
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Lennyz1988 said:
My bad. Here is also another gapps
Click to expand...
Click to collapse
Still :c I only flashed the base tho, Am I supposed to flash the add ons too?
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
CHIN3S3_N00B said:
I think you can try a complete boot before flashing Gapps. And try other builds of Opengapps like mini or micro(well or even smaller depending your "Google apps" usage)
Click to expand...
Click to collapse
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Could you try GearCM? Official CM for i9500 had lots of issues.
Sent from my GT-I9500
Chikyu Tenshi said:
Thanks for the reply, I'm downloading micro right now. Gonna fresh install CM 12.1 using TWRP then boot my phone fully before going back to recovery and flashing Gapps
Will edit my post within 30 mins with the result
Edit: No luck, And now for some reason my phone does not recognise my sim card
Click to expand...
Click to collapse
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
CHIN3S3_N00B said:
Strange... because the symptoms shows like a mismatched gapps to cm... btw are you using the lastest TWRP?
If Yes try other recoveries. I used to use Philz until I bricked mine and had to flash back to stock and now I'm using a modified TWRP to enable dual boot.
If No then try update it and give it another try?
Click to expand...
Click to collapse
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Lennyz1988 said:
I recommend against doing this. The other recoveries are outdated and will give you problems. Stick with the latest TWRP.
Click to expand...
Click to collapse
I think that i didn't express myself very well. Yes it's advisable and strongly recommended to use lastest builds of any recovery available as stable build.
But once i had to use Philz to flash a MIUI ROM because TWRP 2.8.6.0 was unable to execute the installation script didn't know why and that's why i said about different recoveries, and oh.... I forgot to say that after successful install rollback to TWRP because it's pretty new , stable and more user friendly than others.(CMW and the rainbow Easter egg was fine but having to use vol and power keys..... NO THANKS!)
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 ??
I had CM 14.1 working properly on my Nexus 4 with one of the early nightlys. Not leaving well enough alone I let it do a cm update to a newer 14.1 nightly. I didn't see any issue, but when it went to reboot from TWRP it just reboots to TWRP not the system.
Any ideas how to recover from this?
kmandel said:
I had CM 14.1 working properly on my Nexus 4 with one of the early nightlys. Not leaving well enough alone I let it do a cm update to a newer 14.1 nightly. I didn't see any issue, but when it went to reboot from TWRP it just reboots to TWRP not the system.
Any ideas how to recover from this?
Click to expand...
Click to collapse
Had the same problem. Solution: Had to flash back to original stock Android, then TWRP let me flash the latest CM nightlies and Gapps pico. Will not try to use CM updater again.. Grrr.
imperator1967 said:
Had the same problem. Solution: Had to flash back to original stock Android, then TWRP let me flash the latest CM nightlies and Gapps pico. Will not try to use CM updater again.. Grrr.
Click to expand...
Click to collapse
I have this problem. Does following your process erase data?
flash cm stock recovery solve this problem
I am running resurrection remix mm 5.7.4 with twrp 3.0.2 by kumajaya on my redmi 2 prime with lollipop bootloader( 2014818 Indian 2 gb ram variant )
I lost my miui twrp backups and now my pc is not working too.
I want to install miui on my phone back preferably lollipop miui 7.
Is there any way to do so without a pc recovery itself?
Download the recovery zip file of MIUI by googling it. (Version you required)
If you want latest version.
Then Google 'MIUI downloads' and search your device and download the ROM.
Then head over to TWRP and flash the zip.
It will give error for the first time.
Flash it again.
It will get flashed.
Then hit reboot, and reboot your device.
Voila! Now you have MIUI on your device.
I have successfully installed miui lollipop base on my redmi 2 prime without any errors.
Also I have confirmed from external app and settings the information of the device that it shows the correct device info.( provided my custom showed correct device info ).
I tried installing the miui ROM as sethidheeraj said. I started wiping system artcache cache and data but was not able to install miui after repeated tries
Then I restored my custom ROM backup
Then by following these steps I got miui back :
1 install your custom ROM( I had rr 5.7.4 mm) or restore your custom ROM backup
2 boot to recovery and flash the miui ROM without wiping system partition
3 it will take real good amount of time and the logs displayed on twrp also aren't very long, don't worry it is still being installed
4 just for your surity wipe data and caches and again flash the miui ROM
5 reboot to system and take a drink for a while coz it is the first boot
Tadaaaa
You have your stock miui back
Also no damages to your recovery or anything.
Download twrp 3.0.2.0 of kumajaya twrp because its device model no will be in wt88047etc...not hm2014818...use flashify app tp flash recovery. Img on using ur rooted custom rr remix...boot to recovery... Wipe cache, dalvil, system,data....then make sure Miui lp rom is in internal memory.... Then install it...it will give some error on start....then install again...it will take around 20min for install plus full boot up.
Riyanx55tu said:
Download twrp 3.0.2.0 of kumajaya twrp because its device model no will be in wt88047etc...not hm2014818...use flashify app tp flash recovery. Img on using ur rooted custom rr remix...boot to recovery... Wipe cache, dalvil, system,data....then make sure Miui lp rom is in internal memory.... .
Click to expand...
Click to collapse
I already installed MIUI and I have posted it's method above your post in my post.
Jamie446677 said:
I already installed MIUI and I have posted it's method above your post in my post.
Click to expand...
Click to collapse
Great ?
Jamie446677 said:
I have successfully installed miui lollipop base on my redmi 2 prime without any errors.
Also I have confirmed from external app and settings the information of the device that it shows the correct device info.( provided my custom showed correct device info ).
I tried installing the miui ROM as sethidheeraj said. I started wiping system artcache cache and data but was not able to install miui after repeated tries
Then I restored my custom ROM backup
Then by following these steps I got miui back :
1 install your custom ROM( I had rr 5.7.4 mm) or restore your custom ROM backup
2 boot to recovery and flash the miui ROM without wiping system partition
3 it will take real good amount of time and the logs displayed on twrp also aren't very long, don't worry it is still being installed
4 just for your surity wipe data and caches and again flash the miui ROM
5 reboot to system and take a drink for a while coz it is the first boot
Tadaaaa
You have your stock miui back
Also no damages to your recovery or anything.
Click to expand...
Click to collapse
Can you give me a video of that i didn't understand that without wiping system partition it was giving the error 7
Sent from my Xiaomi Redmi 2 using XDA Labs
Bhavesh Tak said:
Can you give me a video of that i didn't understand that without wiping system partition it was giving the error 7
Click to expand...
Click to collapse
I don't have a video tho but I meant that you should only wipe data and caches but leave system as it is. ( My phone had rr marshmallow installed before.) After rr I haven't tried any custom roms so I don't know whether it will work on others. So just flash miui 7.5 like you would for an OTA but do wipe your data and caches