My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
kevinga said:
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
Click to expand...
Click to collapse
So just to make sure I understand this correctly you just want to know why you cant dirty flash CM11s rom over itself. First off you can dirty flash all you want but the issues you may or may not get are on you. Now may I suggest your wipe system when dirty flashing with TWRP. I check off dalvilk, cache and system whenever I upgrade or dirty flash.
Also this is still android and most if not all of the flashing rules still apply
The problem I have is with wifi. This developed a couple of days ago where I have to toggle airplane mode on/off before wifi will reconnect. I actually did a factory reset last night and it did not fix it. I am now thinking that I will need to do more. I suppose the wifi is monitored by the kernel? baseband? I am not sure that a factory reset would reset those things. I could be wrong.
Related
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
Like everyone else I got the 5Q update the other day. Something in the update was causing my battery to drain much faster than before and since there are no new features in 5Q that I care about I tried rolling back to 44s.
I used the flash-able version of 44s from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Now I am basically stuck in a boot loop. Android boots up but I keep getting com.android. phone has stopped working over and over.
Anyone know how to fix this?
I didn't back anything up thinking this would be a quick roll back to 44S so I want to avoid having to do a full factory reset.
If worst comes to worst, can I use fastboot to reflash 44S without losing pics/texts/files ect?
Edit: I jumped back to 5Q and I no longer get the continuous errors. So I guess the question becomes now how should I go about rolling back to 44S and avoid getting the errors I was getting?
Thanks!
skyliner99 said:
Like everyone else I got the 5Q update the other day. Something in the update was causing my battery to drain much faster than before and since there are no new features in 5Q that I care about I tried rolling back to 44s.
I used the flash-able version of 44s from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Now I am basically stuck in a boot loop. Android boots up but I keep getting com.android. phone has stopped working over and over.
Anyone know how to fix this?
I didn't back anything up thinking this would be a quick roll back to 44S so I want to avoid having to do a full factory reset.
If worst comes to worst, can I use fastboot to reflash 44S without losing pics/texts/files ect?
Edit: I jumped back to 5Q and I no longer get the continuous errors. So I guess the question becomes now how should I go about rolling back to 44S and avoid getting the errors I was getting?
Thanks!
Click to expand...
Click to collapse
When you went back to 44S did you clean flash or dirty flash? The errors suggest that you dirty flashed, which you shouldn't do when going backwards. So what you need to do is perform a full wipe (system/data/cache/dalvik cache) and then flash 44S. Backup your user apps (not system apps or settings though) with Titanium Backup first, then you can restore them after 44S boots up again.
Transmitted via Bacon
The easiest method to go back would be to back up using Titanium Backup (And nandroid if you want to revert to old ROM if any problems occur) and then Wipe data/cache and flash the signed zip you downloaded. The issues must be with additions to dialer app I guess.
But just one question, have you checked why there is battery drain in 5Q? I would suggest you to install 'Better Battery Stats' or WakeLock Detector and find out what is draining your battery.
Usually this is the main culprit,http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525/page3 .
You can also rely on Calkulin's Stock ROM's to enjoy stock+root. http://forum.xda-developers.com/oneplus-one/development/rom-calkulins-oneplus-one-v1-0-t2810365.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
timmaaa said:
When you went back to 44S did you clean flash or dirty flash? The errors suggest that you dirty flashed, which you shouldn't do when going backwards. So what you need to do is perform a full wipe (system/data/cache/dalvik cache) and then flash 44S. Backup your user apps (not system apps or settings though) with Titanium Backup first, then you can restore them after 44S boots up again.
Transmitted via Bacon
Click to expand...
Click to collapse
@timmaaa, you really are the fastest to help anyone in distress. Thank you. :good::laugh:
tr.supradeep said:
The easiest method to go back would be to back up using Titanium Backup (And nandroid if you want to revert to old ROM if any problems occur) and then Wipe data/cache and flash the signed zip you downloaded. The issues must be with additions to dialer app I guess.
Click to expand...
Click to collapse
System must be wiped too. Otherwise there's really no point in wiping anything.
Transmitted via Bacon
You are right, I missed that part, though I do it always. Always while changing ROMs and Downgrading. Upgrading using dirty flash has never caused me a problem.
I'm having a problem when I flash the CM12 ROM.
While having CM11.x I go to Settings and navigate to "CM Updates" where I can see a list of Nightlys and stable CM releases. When I install the new CM update this way everything seems to go okay, however This may be normal, I get a message from CWM "Possible Root loss, fix?",.. I select yes and it boots up, runs through the whole "Android is upgrading" message and all. When the phone is finally ready for use I get spammed with millions of messages saying "Application has stopped" and they will pop up infinity in less then a second. I have to hold power and tell the phone to reboot into recovery so I can resotre from backup.
I also downloaded the ROM from CM website and flashed it using "ROM manager". I get the exact same issues sadly.
What could be the problem?
Is CWM not compatible with lollipop?
Do I need to run a factory reset and wipe my phone before flashing?
I've been fiddling with this all day now. -Sigh-
EDIT:
Should I flash the latest version of "gapps" ?
You're going to need to do some reading. Installing LP over KK thru a nightly isn't going to work. You'll need LP Gapps for starters and you'll need to go into recovery and do some wiping before you flash. There are some good LP roms here: http://forum.xda-developers.com/lg-g2/development with full installation procedures. Also, most are using TWRP for recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 You may also need to flash a different baseband but you'll find everything you need in the general development section. Also, next time you really should post your questions in the Q&A section. Anyway, do some reading and you'll be good to go! :good:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Traceguy said:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Click to expand...
Click to collapse
First let me apologise, I see that you are in Q&A and I'm the one that doesn't know which forum he's in.
Next, well I've used both CWM and TWRP. Personally I prefer TWRP but as long as you're on the latest and greatest you should have no problems from what I've read. And if you do just flash over to the other and see if it fixes the problem. I've been using the 10D radio for quite some time now and it works for me.
As I go from rom to rom I always do a clean flash, wiping data, system, dalvik and cache. I rarely do a dirty flash but that's just me. As long as you can recover from the occasional boot loop you'll be good. :laugh:
OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.
i need help this problem has been there with me since i bought my opo 2 months back. i received it with cm11s build which was not official. so i had to manually upgrade my opo to cm12s after that i have flashed many lp roms even cm12.1s but never a kk rom. then i felt like going back to kk i flashed @Bobbi lim cm11s mod rom 3.5 and i got no service tried many things still no service i then flashed cm11s 44s factory image but still got no service. then i gave up and continued to stay on lp roms. then till recently i found that it was not the roms but the modem if i flashed lp modem on kk roms i got service but with black screen bug but when i flashed back kk modem again no service.
please help me is there something wrong with my opo hardware. @Heisenberg @Vivek_Neel and anyone else who has solution to this problem.
sorry for making it so long.
vicelord97 said:
i need help this problem has been there with me since i bought my opo 2 months back. i received it with cm11s build which was not official. so i had to manually upgrade my opo to cm12s after that i have flashed many lp roms even cm12.1s but never a kk rom. then i felt like going back to kk i flashed Bobbi lim cm11s mod rom 3.5 and i got no service tried many things still no service i then flashed cm11s 44s factory image but still got no service. then i gave up and continued to stay on lp roms. then till recently i found that it was not the roms but the modem if i flashed lp modem on kk roms i got service but with black screen bug but when i flashed back kk modem again no service.
please help me is there something wrong with my opo hardware. HeisenbergVivek_Neel and anyone else who has solution to this problem.
sorry for making it so long.
Click to expand...
Click to collapse
Did you flash *fastboot images* of CM11S?
If yes and still if you are facing radio problems, please refer http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 and try out KK modems
Otherwise please flash OxygenOS and give it a try.
@Mr hOaX i have flashed fastboot images of cm11s with toolkit and manually too still no service and as i have said i get service on all lp roms including oxygen os. I have tried flashing modems using twrp 2.8.6.0 still got no service whatsoever with kk modems but with lp modems i get service even on lp roms if i flash kk modem i instantly get no service after booting back up.
vicelord97 said:
@Mr hOaX i have flashed fastboot images of cm11s with toolkit and manually too still no service and as i have said i get service on all lp roms including oxygen os. I have tried flashing modems using twrp 2.8.6.0 still got no service whatsoever with kk modems but with lp modems i get service even on lp roms if i flash kk modem i instantly get no service after booting back up.
Click to expand...
Click to collapse
Firstly, make sure your TWRP is 2.8.6.0
Secondly, flash KitKat firmware before flashing any kitkat ROM.
Thirdly, don't use toolkits.
To your problem, here's my suggestion. Do a full wipe in TWRP. Flash KitKat firmware A FEW TIMES - PREFERABLY 5 TIMES. Each time with a cache and dalvik cache in between. After that do a full wipe again and flash the KitKat rom. Not sure if its placebo but that's what I did to get KitKat working after I switch back from 5.x to 4.4 and have the same problem as you.
If it doesn't work, do a full wipe in TWRP. After that flash factory images except recovery and userdata. You should be good to go to flash my ROM.
By full wipe u mean clean flash or including internal storage?
And thanks will try and report back
Didn't help still got no service tried flashing fast boot image too manually still no service.
vicelord97 said:
By full wipe u mean clean flash or including internal storage?
And thanks will try and report back
Click to expand...
Click to collapse
vicelord97 said:
Didn't help still got no service tried flashing fast boot image too manually still no service.
Click to expand...
Click to collapse
Are you flashing fastboot images correctly? Full wipe = wiping system, cache, dalvik cache and data in TWRP