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.
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
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.
Hi, i'm on cm11s 25r, rooted with towelroot and twrp installed. I'd like to install 30o and 33r but the ota is not working with twrp ("error, can't install on top of incompatible package"or something like that)
I prefer not too lose all my data, apps and photos. Is there a way to update ?
Thanks !
What recovery are you on? There are some problems going on with TWRP 2.8.0.0, where you may have to revert back to 2.7.1.1 in order to flash OTAs.
Your steps are to flash 30O OTA and then 33R OTA.
Alternatively, you can start from scratch and flash 30O via fastboot but then you lose all your data.
zephiK said:
What recovery are you on? There are some problems going on with TWRP 2.8.0.0, where you may have to revert back to 2.7.1.1 in order to flash OTAs.
Your steps are to flash 30O OTA and then 33R OTA.
Alternatively, you can start from scratch and flash 30O via fastboot but then you lose all your data.
Click to expand...
Click to collapse
... I just flashed 2.8.0.0 this afternoon it might be related. i think i'll end up backing up all my data, unlocking my bootloader properly and flashing latest rom (i was trying to avoid that because downloading game data and apps takes forever with my "slow" internet )
coc014 said:
... I just flashed 2.8.0.0 this afternoon it might be related. i think i'll end up backing up all my data, unlocking my bootloader properly and flashing latest rom (i was trying to avoid that because downloading game data and apps takes forever with my "slow" internet )
Click to expand...
Click to collapse
Thats understandable, I always recommend people to unlock their bootloaders so when they do decide to tinker with their phones they can flash a custom recovery as well as back up all their data.
When you are fully unlocked and whatnot, get Titanium Backup (Pro recommended) and then you can use that to back up all of your apps/data so they stick on rom changes.
i installed titanium backup, downloaded stock rooted 33r, installed it, restored my apps/data , installed franco kernel r18 and everything is working :good: :good:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
To be correct, you are running a 4.4.3 ROM with 4.4.3 firmware right? Also when you try to enable wifi from the status bar does it simply endlessly show its trying to turn it on?
Perhaps a viable option would be to try a factory reset via TWRP, I sometimes encounter issues when doing that after a firmware update. Actually my 4.4.3 was so messed up because of restoring apps that I was forced to go back to my 4.4.2 ROM. Soo as I said, since you have a backup I'd just at least give factory reset a try and if it doesn't fix it then you can restore your backup again.
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
bighleo114312 said:
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
I'm kinda new to all this flashing/recovery stuff. How exactly do I use another kernel?
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
How did you restore your apps?
jsaxon2 said:
How did you restore your apps?
Click to expand...
Click to collapse
Through TWRP. I put it back on after the update and restored the apps and data (not the system) from the backup I'd made previously.
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
jsaxon2 said:
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
Click to expand...
Click to collapse
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
istrasci said:
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
Click to expand...
Click to collapse
Your posts didn't really make clear what exactly you did: From which rom you took the TWRP nandroid, which rom you restored it back to, what you mean by "you think you ran a RUU", what exactly from the nandroid you restored in TWRP....
Did you restore all of /data? If you did, you restored way more than just your apps and may have compatability issues.
Restoring /data IMHO is not a good idea after doing a firmware upgrade and flashing a corresponding rom.
A better strategy would be to backup just your apps and their data in TiBu and only restore those after you flashed the new firmware and the new rom.
Here's what I would do:
Factory reset in TWRP
Reflash the rom
Reinstall your apps (this time from scratch, next time you'll have a TiBu backup).
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
UPDATE: I was able to make it work, see comment #12
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
timmaaa said:
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
rhaces said:
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
Click to expand...
Click to collapse
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
timmaaa said:
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
Click to expand...
Click to collapse
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
rhaces said:
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
Click to expand...
Click to collapse
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
timmaaa said:
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
Click to expand...
Click to collapse
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
Follow vomer's guide here. It just bring your rom back to stock and leaves user data untouched. http://forum.xda-developers.com/showpost.php?p=55882576&postcount=229
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
There's nothing wrong with Titanium if you know how to use it. Unless you're restoring system data (which you shouldn't be) it's perfectly solid. And the thing is, you're not stock, those modifications you've made mean that you're not stock, so it's completely normal that you'd have issues with updating. You can moan about it all you like but it doesn't change the fact that you need to wipe.
Transmitted via Bacon
What he said.
You can't apply an OTA update if u have a custom kernel installed.
Just go back stock and apply updates until the latest version. If u use titanium properly you will not have any issue, just backup user apps without system settings.
Any other turnaround can cause havoc.
rhaces said:
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
Click to expand...
Click to collapse
Please check http://forum.xda-developers.com/showpost.php?p=55948892&postcount=16
@rhaces, just curious, could you PM me your /data/system/packages.xml file?
Well, It looks like you really don't need to wipe data (see, I told you it was ludicrous), I tried following both this and this, but did not helped (however both gave me ideas), here's what I did:
Fastboot flash boot system and recovery from 33R, boot into system, apply the OTA from the system (I'm now in an unrooted-unmodified stock 33R) and now that worked. Booted into newly installed 38R and everything worked ok, so went back to fastboot, flashed TWRP, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
Just don't complain when you start getting problems. Which you most likely will.
Transmitted via Bacon