Yesterday I tried sideloading the 30O update manually from Android Police, the sideloading of 30O kept failing so I used the modified version on the XDA forums which skips the errors and installs it anyway. After this being successful I woke up this morning to see another 9MB update, this is apparently a patch for the update.
I went to install this but it has the same error as the 30O install had,
assert failed: apply_patch_check("/system/framework/core.odex","numbers and letters here","numbers and letters here")
E:Error executing update binary un zip '/cache/cm-bacon-numbere-to-numbers-signed.zip'
Then it fails to flash.
Does anyone know how I can fix this? Wiping Cache and Dalvik Cache does not help.
oscarandjo said:
Yesterday I tried sideloading the 30O update manually from Android Police, the sideloading of 30O kept failing so I used the modified version on the XDA forums which skips the errors and installs it anyway. After this being successful I woke up this morning to see another 9MB update, this is apparently a patch for the update.
I went to install this but it has the same error as the 30O install had,
assert failed: apply_patch_check("/system/framework/core.odex","numbers and letters here","numbers and letters here")
E:Error executing update binary un zip '/cache/cm-bacon-numbere-to-numbers-signed.zip'
Then it fails to flash.
Does anyone know how I can fix this? Wiping Cache and Dalvik Cache does not help.
Click to expand...
Click to collapse
You have flashed some mod to your system, which prevents the update from applying.
The only solution is flashing the 25R system.img manually, then sideloading the 30O big update, followed by the small one.
Dzhedaj said:
You have flashed some mod to your system, which prevents the update from applying.
The only solution is flashing the 25R system.img manually, then sideloading the 30O big update, followed by the small one.
Click to expand...
Click to collapse
I don't think I've flashed any mods through recovery, but I have done stuff like installing busybox, xposed, root, I assume this could mess it up too?
One more question, I am currently successfully on 30O, surely flashing 25R would cause a softbrick as you cannot go back to older versions with CyanogenMod?
Should I just flash the system.img from 30O big update and then try to install the small one?
What do you think?
oscarandjo said:
I don't think I've flashed any mods through recovery, but I have done stuff like installing busybox, xposed, root, I assume this could mess it up too?
One more question, I am currently successfully on 30O, surely flashing 25R would cause a softbrick as you cannot go back to older versions with CyanogenMod?
Should I just flash the system.img from 30O big update and then try to install the small one?
What do you think?
Click to expand...
Click to collapse
Where does it say you can't go back to older versions? If you have a previous backup or something you can roll back no problems. You need to remove Xposed and start again.
Transmitted via Bacon
timmaaa said:
Where does it say you can't go back to older versions? If you have a previous backup or something you can roll back no problems. You need to remove Xposed and start again.
Transmitted via Bacon
Click to expand...
Click to collapse
I don't have any backups from that version. I was under this impression because in the CM nightlies if you ever flashed a nightly from before your current nightly it caused a softbrick.
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
oscarandjo said:
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
Click to expand...
Click to collapse
It's probably something you installed from xposed. But your solution should work.
apristel said:
It's probably something you installed from xposed. But your solution should work.
Click to expand...
Click to collapse
I'm going to try uninstalling xposed and my modules before reflashing all of that.
oscarandjo said:
I'm going to try uninstalling xposed and my modules before reflashing all of that.
Click to expand...
Click to collapse
Removed Xposed and uninstalled all of my modules and I'm getting the same error as the beginning, I'm gonna try the flashing solution now.
oscarandjo said:
Removed Xposed and uninstalled all of my modules and I'm getting the same error as the beginning, I'm gonna try the flashing solution now.
Click to expand...
Click to collapse
You should always have a backup on your phone. Especially the original setup at least. when properly rooted or not you can go from 4.4.4 to 4.4.2 or whatever if you like. Let us know how the flashing goes and do yourself a favor and do more reading and less flashing at least till you fully know all you can and can't do.
playya said:
You should always have a backup on your phone. Especially the original setup at least. when properly rooted or not you can go from 4.4.4 to 4.4.2 or whatever if you like. Let us know how the flashing goes and do yourself a favor and do more reading and less flashing at least till you fully know all you can and can't do.
Click to expand...
Click to collapse
I haven't actually been flashing anything though, I just had Xposed and some minor modules like TabletMetrics and the Greenify module installed.
Anyway, I'll make sure to do backups through recovery every so often. I've got a lot of stuff backed up with TitaniumBackup
oscarandjo said:
I haven't actually been flashing anything though, I just had Xposed and some minor modules like TabletMetrics and the Greenify module installed.
Anyway, I'll make sure to do backups through recovery every so often. I've got a lot of stuff backed up with TitaniumBackup
Click to expand...
Click to collapse
nandroids are good for a lot of different reasons. TB are fine but there may be times where simply restoring your phone to a time when all worked fine may be highly necessary. Unstoppable FC's and unknown basebands have been times where a nandroid has helped out for some users
playya said:
nandroids are good for a lot of different reasons. TB are fine but there may be times where simply restoring your phone to a time when all worked fine may be highly necessary. Unstoppable FC's and unknown basebands have been times where a nandroid has helped out for some users
Click to expand...
Click to collapse
I see, thanks.
oscarandjo said:
I don't have any backups from that version. I was under this impression because in the CM nightlies if you ever flashed a nightly from before your current nightly it caused a softbrick.
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
Click to expand...
Click to collapse
Flashing backwards may only cause problems if you're dirty flashing. So if you're ever moving backwards you must go clean. Anyway, it looks like you're all set judging by the other posts here now :good:
Transmitted via Bacon
Does anyone have a 25R mirror? Mega.co.nz would be best. Cyanogen's servers are being awfully slow.
timmaaa said:
Flashing backwards may only cause problems if you're dirty flashing. So if you're ever moving backwards you must go clean. Anyway, it looks like you're all set judging by the other posts here now :good:
Transmitted via Bacon
Click to expand...
Click to collapse
Oh. I didn't want to lose any data though...
Does this apply even if I'm just flashing 25R's system.img and will update to 30O again straight after?
oscarandjo said:
Oh. I didn't want to lose any data though...
Does this apply even if I'm just flashing 25R's system.img and will update to 30O again straight after?
Click to expand...
Click to collapse
Can I ask a question and anyone can answer this - Whats the big deal about setting your phone up from scratch knowing that doing it this way will have it bug free. Its about a half hour to reset a phone up lets say.
I will let you know of a program called APP2Zip its old but you can back all your stuff up in a flashable zip file. Its dirty and any issues like FC's you have to handle but it does work.
I prefer doing it all from scratch but at least I know I have a clean canvas
playya said:
Can I ask a question and anyone can answer this - Whats the big deal about setting your phone up from scratch knowing that doing it this way will have it bug free. Its about a half hour to reset a phone up lets say.
I will let you know of a program called APP2Zip its old but you can back all your stuff up in a flashable zip file. Its dirty and any issues like FC's you have to handle but it does work.
I prefer doing it all from scratch but at least I know I have a clean canvas
Click to expand...
Click to collapse
Because I've already had to do this before now, it's annoying to have to wipe it all over again after just setting it up.
I guess I'll have to do this...
Flash system.img of 25R, update to 30O and then the mini 30O patch. Then re-root using TWRP, then restore my stuff using Titanium Backup and set everything up as it was, wasting an hour or two. :/
Anyway, I understand this is the best way to do it, thanks for the help.
oscarandjo said:
Because I've already had to do this before now, it's annoying to have to wipe it all over again after just setting it up.
Click to expand...
Click to collapse
Ok, I guess doing it right is not so annoying to me... Enjoy and hope you find a suitable workaround to save your data :good:
playya said:
Ok, I guess doing it right is not so annoying to me... Enjoy and hope you find a suitable workaround to save your data :good:
Click to expand...
Click to collapse
Yeah, does Titanium Backup backup large sideloaded apps?
oscarandjo said:
Yeah, does Titanium Backup backup large sideloaded apps?
Click to expand...
Click to collapse
Pro version will restore all at one time. That's not recommended especially if you are restoring from a different version of android. Its all at your own risk. I been there and for me shortcuts were not worth it always for me at least...
1+1 Homie......
Related
Hi everyone,
Las week the OTA update appeared in my phone. I tried to use the google-automatic procedure, but as I have my Nexus 5 rooted, the install was aborted as soon as the device was restarted.
I read the helpdesk thread, trying to update the device manually, but I can't be able to.
I have the 4.4 to 4.4.2 .zip file inside the downloads folder, I restart the device to recovery mode (I've installed TWRP), and after writing the decrypt password and mount the volume, When I try to apply the zip file
"/system/app/EmailGoogle.apk" has unexpected co
E: Error executing update binary in zip '/sdcar
Error flashing zip '/sdcard/Download/b3d1f30762
Updating partition details..
Note that the senteces is cut due to the lenght of the screen.
Before flashing, I go to mount option, and mount all the folder (system, firmware, sdcard)
Any ideas?
Now I'm thinking that when I rooted the device, I used ES File Explorer to delete some apps directly from /sys/apps, maybe is that the error, that some GApps has been removed from the device.
Thank you!
Yes Google has nicely written in app checks. If these apps are not present on check the update is aborted
Sent from my Nexus 5 using Tapatalk
So I have to reinstall the GApps package, and try to apply de update?
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Ben36 said:
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Link not valid, but thank you, I will install GApps
Zepius said:
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Click to expand...
Click to collapse
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Deiwor said:
Link not valid, but thank you, I will install GApps
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Click to expand...
Click to collapse
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
jd1639 said:
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
Click to expand...
Click to collapse
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Deiwor said:
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Click to expand...
Click to collapse
Flashing the system and boot images isn't starting from scratch... you can keep your userdata as long as you aren't using a custom ROM. Flashing those just gives you back a clean stock OS without any of your mods. No need to start from scratch. Should only take a couple minutes.
Also, your mods are the reason it failed in the first place, not because you were rooted. Rooting itself does not prevent OTA updates.
Hi all,
I have searched the web, but haven't found an exact answer to my question.
I have a Nexus 5, currently on 4.4.2 (KOT49H). I am unlocked, rooted + Xposed and have TWRP. I want to update to 4.4.4 preferably OTA, officially. I would like to be able to use OTA updates from now on if possible.
Currently, if I disable Xposed, and use Suvival Mode in SuperSU and try to install the OTA update, TWRP intervenes and doesn't let me.
I would like to replace TWRP with the stock recovery so I can update OTA in the future. I don't want to wipe the phone to achieve this if possible. If this isn't possible, could someone step through how to update to 4.4.4 with TWRP installed — I'm on a mac also.
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
providedbike said:
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes, extract the image and then the zip file
Sent from my Nexus 5 using XDA Free mobile app
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
rootSU said:
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
Click to expand...
Click to collapse
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
providedbike said:
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
Click to expand...
Click to collapse
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
rootSU said:
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
Click to expand...
Click to collapse
Does this apply for the stock rom? I'm rooted, but still stock...
providedbike said:
Does this apply for the stock rom? I'm rooted, but still stock...
Click to expand...
Click to collapse
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
rootSU said:
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
Click to expand...
Click to collapse
Ok great that's very helpful, thanks!
providedbike said:
Ok great that's very helpful, thanks!
Click to expand...
Click to collapse
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
rootSU said:
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
Click to expand...
Click to collapse
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
providedbike said:
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
Click to expand...
Click to collapse
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
rootSU said:
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
Click to expand...
Click to collapse
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
providedbike said:
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
Click to expand...
Click to collapse
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
rootSU said:
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
Click to expand...
Click to collapse
Great I'll do it tonight
Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon
EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)
Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Have you tried using CyanDelta?
https://play.google.com/store/apps/details?id=com.cyandelta
Transmitted via Bacon
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
timmaaa said:
Have you tried using CyanDelta?
Transmitted via Bacon
Click to expand...
Click to collapse
Tried that earlier today, didn't help anything.
gmac1990 said:
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think that might be my best bet. I guess it's better than nothing, haha. Thanks for you answers guys.
It probably is due to not having updated firmware. Which nightly? Wipe everything and flash the most recent nightly or go to blisspop thread and find the updated firmware zip it's around 30mb and flash that. It should fix your boot loop issues
Sent From Lollipopified Bacon Goodness!
The firmware can be found here:
http://www.vanir-exodus.net/exodus/bacon/
Transmitted via Bacon
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Skizwack said:
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Click to expand...
Click to collapse
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
I suppose that may have been my problem all along. The main problems I was having were just little bugs (system UI very rarely crashing, and a couple other minor annoyances), but I guess those could have been caused by having the wrong firmware. Maybe I'll give it another go soon. Now that I'm all settled in to CM11S, haha. Thanks again!
Has anyone else had any issues with the automated download and install feature in the CM12 settings? Mine will download the night lies and even automatically boot into TWRP but it doesn't flash?
timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Skizwack said:
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Click to expand...
Click to collapse
which recovery and version are you using?
playya said:
which recovery and version are you using?
Click to expand...
Click to collapse
TWRP 2.8.4.1
Skizwack said:
TWRP 2.8.4.1
Click to expand...
Click to collapse
What's the name of the firmware file you flashed?
Transmitted via Bacon
timmaaa said:
What's the name of the firmware file you flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Skizwack said:
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Click to expand...
Click to collapse
have tried different version TWRP?
Skizwack said:
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Click to expand...
Click to collapse
What about when you download the whole ROM zip from the CM site?
geowolf1000 said:
have tried different version TWRP?
Click to expand...
Click to collapse
The version he's on is fine.
timmaaa said:
What about when you download the whole ROM zip from the CM site?
Click to expand...
Click to collapse
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Skizwack said:
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Click to expand...
Click to collapse
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
timmaaa said:
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
Click to expand...
Click to collapse
If I remember right, I do. I'm on the latest version now though, so I can't really test it. When a new one comes out tomorrow I'll give it a go and see what happens.
Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Speeder12321 said:
Hello, I got Samsung J-7108 and I got stuck in bootloop after flashing Xposed Framework with flashfire... I am sure I downloaded the right version for my CPU, the latest one. I flashed the original firmware, but it doesn't work. I don't have a custom recovery, what can I do? Help, please.
Click to expand...
Click to collapse
Did you ever figure out how to fix this issue? Was very curious about this Flashfire.
Paul R
try to flash boot.bin for your phone ,, extract it from stock room and convert ti from bin to tar and flash it
Thank you for your replies. I had to do a factory reset, nothing else helped. So I tried it again, I flashed the Xposed V86 with flashfire, worked fine for two days, than the phone went to bootloop again. I guess I will not deal with xposed anymore, it is a good thing, but doesn't really work as it should.
Okay, so I have a update: Phone works fine for two days. I turn it on and everything seems fine, but... after two days of using it goes to bootloop again no matter what I do. I tried flashing original firmware, works fine for two days, than bootloop again, tried factory resetting, wiping cache and so on, still the same, works, but goes to bootloop every two days when I try to turn it on. Help, please.
Any ideas?
Try to flash the xposed uninstaller zip
messi2050 said:
Try to flash the xposed uninstaller zip
Click to expand...
Click to collapse
I did many times, never helped
Speeder12321 said:
I did many times, never helped
Click to expand...
Click to collapse
I think that u will need to flash twrp then wipe the system/data partitions and reflash stock rom ( note that this may break your phone )
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Speeder12321 said:
I found out, that stock firmware works fine, but whenever I give it a root access, it stucks in bootloop after 2 days of using the phone... is there anything else I can try before wiping data partitions?
Click to expand...
Click to collapse
which root method u are using
messi2050 said:
which root method u are using
Click to expand...
Click to collapse
I am using a pre-rooted firmware.
I guess that XPosed changed the values of some System files and uninstaller does no job in changing them back to how they were before. Question is: There's no custom recovery availible for Chinese model of J7, so is there a possibility to delete System using a Root file explorer? Which has access to System partition?
messi2050 said:
which root method u are using
Click to expand...
Click to collapse
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Speeder12321 said:
When I do factory reset in recovery on rooted firmware, it works again, but like I said, just for two days? How is that even possible? Factory reset should delete everything including changes that xposed made, shouldn't it?
Click to expand...
Click to collapse
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Speeder12321 said:
I don't think so, I used prerooted firmware for months and never had a single problem... everything started to go wrong after flashing xposed.. So how can be SuperSU a problem if it used to work fine before?
EDIT: And no, I didn't receive security policy update.
EDIT2: But thanks a lot for your advice, I will try to update SuperSU... Is it okay if I flash newer superSU with flashfire, when my current one is installed as a system app or do I need to do something before flashing the new one?
Click to expand...
Click to collapse
Use the uninstaller in SuperSU settings.
ashyx said:
Use the uninstaller in SuperSU settings.
Click to expand...
Click to collapse
It is installed as a system app, so I will need to do a full unroot. And if I do full unroot, I won't be able to flash the new one with flashfire, because it needs root access, what now ?
EDIT: Okay, I managed to update SuperSU to version 2.78 SR1, I will post an update if it fixed my issue, thanks
ashyx said:
Xposed modifies System, Factory reset does not affect system only Data.
Your issue isn't xposed.
You are probably receiving a security policy update. The policy update breaks earlier versions of supersu causing bootloops.
You need to flash supersu v2.78 SR1 with Flashfire then the correct Xposed version.
Supersu v2.78 will block the policy up date.
Click to expand...
Click to collapse
Thank you sooooooo so much, it fixed my issue