Hi Everybody,
I have successfully updated to 4.4.1 on my Nexus 5 (unlocked bootlader, rooted, stock and Xposed). Here are the steps:
Before update I was on stock, rooted, xposed.
Flashed update.zip after unintsalling xposed. Lost recovery so adb pushed then flashed SuperSU, wiped delvik cache. All seems ok now except:
"Unfortunately google play has stopped working" tried everything (except factory reset)....
any advise will be greatly appreciated
PS: I posted this on OTA Help Desk too, but doing this here too.
Thanks again guys.
Edit: Keeping this in case any one has the same issue
Fix: Flash back to stock (if you dont want to lose data then only flash boot and system). Then use the Nexus 5 OTA helpdesk Scenario #2 (flash ota.zip and supersu) to gain 4.4.1. All working great now.
Woohoo
Related
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
[UPDATE]: I have included my stock SystemUI.apk and .odex. Copy into /system/priv-app, overwrite existing files and set permissions to rw-r--r--.
All Xposed tweaks can be undone by unselecting the modules in the Xposed framework and rebooting.....before rebooting again into recovery..
UPDATE: Added the version of Philz recovery I use, for those with the "this package is for falcon_umts devices : this is a xt1034" error.
Extract into your fastboot folder and issue command:
fastboot flash recovery PhilZ.img
That should set all that straight...
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
draco259 said:
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
Click to expand...
Click to collapse
It will return the system folder to default. All changes should be reset, as far as I can tell...
secretkloud said:
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
Click to expand...
Click to collapse
Hi can you include your original systemui.apk i lost mines >.<
serophia said:
Hi can you include your original systemui.apk i lost mines >.<
Click to expand...
Click to collapse
Added to first post...
secretkloud said:
Added to first post...
Click to expand...
Click to collapse
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Error when in recovery
I downloaded the zip but when I go to CWM recovery and try to install it from the SD it shows me an error.
it says; This package is for "falcon_umts" devices; this is a xt1032.
any help?
Maybe you'll find the solution to your problem here.
thanks!!
mokkami said:
Maybe you'll find the solution to your problem here.
Click to expand...
Click to collapse
thanks dude, now I just gotta know how to change the recovery haha
Thanks
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Same thing for me!
Is this gonna be worked with the last update 176...
i have used ur system ui but i still get the error
serophia said:
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Click to expand...
Click to collapse
Adaway modifies the "system/etc/hosts" file. It should also be disabled before updating.
irishpancake said:
QUOTE=mdentener;50672956]Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk[/QUOTE]
I kept my root also after the update. Those mods were installed before the OTA and remained installed after. I only disabled xposed modules temporarily and changed CWM to Phil's CWM to install the OTA.
Sent from my Moto G using Tapatalk
Hey, I' ve got my Oneplus One now with CM12 (20150415 nightly), and rooted months ago with zedomax tutorial (can't post link).
With the tutorial, I unlocked the bootloader, flashed SuperSu binaries, installed TWRP recovery and then flashed CM11.
I've some issues with the root. When I try apps requiring root permissions it says they're not enabled. I've also messed flashing CM12.1 yesterday, because I forgot the 5.1 gapps, and had to go back to CM12. Of course now there are a lot of problems with several apps and processes.
I have backups of everything and I don't mind losing data, and my question is: can I follow an xda tutorial to do all the process again? I mean, even my phone is not stock, can I reunlock the bootloader (to erase everything) and do everything well?
I have also another doubt: do I need to flash SuperSu binaries, or CM is prerooted?
Thank you and sorry for my inexperience (I try to progress )
sdert said:
Hey, I' ve got my Oneplus One now with CM12 (20150415 nightly), and rooted months ago with zedomax tutorial (can't post link).
With the tutorial, I unlocked the bootloader, flashed SuperSu binaries, installed TWRP recovery and then flashed CM11.
I've some issues with the root. When I try apps requiring root permissions it says they're not enabled. I've also messed flashing CM12.1 yesterday, because I forgot the 5.1 gapps, and had to go back to CM12. Of course now there are a lot of problems with several apps and processes.
I have backups of everything and I don't mind losing data, and my question is: can I follow an xda tutorial to do all the process again? I mean, even my phone is not stock, can I reunlock the bootloader (to erase everything) and do everything well?
I have also another doubt: do I need to flash SuperSu binaries, or CM is prerooted?
Thank you and sorry for my inexperience (I try to progress )
Click to expand...
Click to collapse
try to flash the stock images with ADB (there are lots of tutorials on the forum here), it will wipe everything and you can have a clean start, then if you want to update to 5.0.2/5.1.1 just download the firmware update, the rom and Gapps. Most of the rooms as for now have a built in root, but maybe it disabled so you have to enabled it through developer settings.
sdert said:
Hey, I' ve got my Oneplus One now with CM12 (20150415 nightly), and rooted months ago with zedomax tutorial (can't post link).
With the tutorial, I unlocked the bootloader, flashed SuperSu binaries, installed TWRP recovery and then flashed CM11.
I've some issues with the root. When I try apps requiring root permissions it says they're not enabled. I've also messed flashing CM12.1 yesterday, because I forgot the 5.1 gapps, and had to go back to CM12. Of course now there are a lot of problems with several apps and processes.
I have backups of everything and I don't mind losing data, and my question is: can I follow an xda tutorial to do all the process again? I mean, even my phone is not stock, can I reunlock the bootloader (to erase everything) and do everything well?
I have also another doubt: do I need to flash SuperSu binaries, or CM is prerooted?
Thank you and sorry for my inexperience (I try to progress )
Click to expand...
Click to collapse
Hi, please follow the below link...
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Hey Guys,
My N5 is currently running android 5.1 and I want to upgrade to 5.1.1. My phone also shows that the OTA update is available but I am currently rooted and running TWRP. A quick google research showed me that I can´t install an OTA update while being on TWRP. Is there any other way to update my phone to 5.1.1 without losing my data?
Greets
I have this exact same question. I was going to try and use fastboot with the system image and recovery and then take the ota update. Not sure if that will work.
I got impatient, so i downloaded the factory image from the web for the version of my phone (lmy47d). I extracted the system.img and recovery.img and flashed them with fastboot as stated here -> http://forum.xda-developers.com/goo...orial-applying-ota-update-stock-root-t2976556
Rebooted the phone and then applied the OTA update. Phone is updating the apps after boot. So far seems ok.
Thank you I will try it out later
You don't lose data by default? At least not for me
Hello
I have a problem with my Mate. I will try and list the things i did to get to this problem and I hope the information helps solve it.
I wanted to install xposed (first thing I did wrong) so I rooted using King Root (ver 4.8.2) successfully
then unlocked the bootloader using Huawei website
Using Flashy, I flashed TWRP recovery to install xposed (regrets).
After creating back up on TWRP, I tried to flash xposed, didnt work.
I gave up and rebooted phone to android, and i saw i had lost Nav buttons and Notification bar.
Booted back into TWRP and tried to restore my backup. It kept failing at 33% (would post logs but I lost them), I then thought a factory reset would help and it did.
I got the navigation and notification bar, but I soon realised I cannot install apps. I couldn’t install from my SD (apk’s) or from the Play Store.
I can’t install anything on it now. I’ve learnt my lesson not to mess with the inner workings of my device but now I am stuck with EMUI (no Nova or other 3rd party launcher).
Is there any way I can get it back to installing apps as usual? I saw another thread with similar problem (can’t install apps) but I wasn’t sure if I should post there (its old and unattended thread). If I should post this in another thread please point me in the right direction and thank you in advance.
:crying:
I would clear cache and Dalvik cache in recovery then flash back to a stock kitkat recovery, put the correct stock complete kitkat ROM in the dload folder in SD card and do a force update from stock recovery. Once it runs properly again, update to the right ROM you want to run, in the correct order of updates, make sure bootloader is unlocked, root the correct way (not kingroot, use ADB) then seek guidance on what mods work with what ROM. Do not try to root without unlocked bootloader! That ruined it I think.
If you want Xposed, it only partially works in Kitkat, not at all in Lollipop. What do you need with Xposed? I'm running B331 Lollipop now, no Xposed and no real need for it. I do have unlocked bootloader, root and Viper4android and it runs great. I use Smart Launcher Pro but kept Huawei Home (launcher) and theming apps installed so the system is happy but it looks how I want and is good to use.
Thanks for your quick response RobboW, will try that method and let you know if I make any improvement to my situation.
So I have to get a stock KitKat recovery and stock KitKat ROM for that recovery. Do I force an update from TWRP or what? I'll read up on recovering stock Roms and let you know if I make any progress. Thank you for the response though.
Force update with a stock ROM needs to be done from stock recovery. TWRP stops the phone from updating the stock way. The bootloader can stay unlocked if it already is.
It worked exactly like you said. I'm back on Lollipop B324. I can install apps and got the motion control settings back.
Thank you so much RobboW!
You're welcome
OS faults are not so bad if you have access to recovery. It's the ones that make using recovery and ADB difficult that cause the big dramas.
Sorry for the newbie question.
I'm on YOG7DAS2K1, rooted, with TWRP recovery. I want to upgrade to the newest COS13 without doing a data wipe.
OTA does not work, obviously.
Tried cm-bacon-cee4e8702d-to-64003595ee-signed.zip (From this page: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746, listed as the YOG7DAS2K1 -> ZNH0EAS2JK OTA update. It flashed fine, but I was missing google play services and couldn't figure out where to get the correct file (tried several, they all didn't work).
So went back to YOG7DAS2K1 and I flashed the stock recovery through fastboot and tried to apply the OTA update through system-> about phone. No go.
I unrooted the phone and tried again. No go.
Now I'm back on YOG7DAS2K1 and trying to figure out how to get this done.
Anyone?
Thanks in advance.
No one replied on this thread, but I ended up following this track: http://forum.xda-developers.com/oneplus-one/help/how-upgraded-to-cm-cos-13-loosing-data-t3370965