So I installed the last Power JB rom on my Go and restored apps+data using Mybackup Pro. Now I get an error message saying something about google play services not supported by my device. I get this when trying to opoen Google+ and Hangouts.
Two questions:
1) I've tried factory reset, but the problem persists. Is this equivalent to reinstalling the rom?
2) For some reason I don't have CWM recovery after installing Power JB. I also can't seem to install the recover over again. I've tried CWM Recovery 6.0.1.2 for Locked Bootloader by @atis112. Do I have to flash stock rom first?
Cheers for any help!
I found a solution:
I downloaded gapps from April 2013 and followed this procedure:
http://forum.xda-developers.com/showthread.php?t=2174013
longballs said:
I found a solution:
I downloaded gapps from April 2013 and followed this procedure:
http://forum.xda-developers.com/showthread.php?t=2174013
Click to expand...
Click to collapse
This doesn't work for me. It says that the app is not installed with no other explanation.
Hello everyone ! i have a oneplus X that was rooted and installed TWRP but because i was banned of an application because it doesnt allow root so i deleted root partially . Anyway i tried to install CM13 through recovery it succeeded but the problem is that it didnt have the store and google play services installed so i installed them from the net and then it poped Unfortunatley Google play services stopped and i need to upgrade it also installed latest Version and tried to clear cache but nothing solved . i also installed the official rom and tried to flash it using recovery and i get "error executing binary in zip " and searched the net forresults and nothing worked or both problems so i am currently stuck in CM13 and the ability to not install anything or wiping the phone and OS when trying to flash official rom
P.S : all apks and roms are latest versions . any help please because i am currently using samsung grand prime and its so slow :crying:
Flash Open Gapps from here instead of whatever it is you happened to have found. You want, ARM, 6.0, NANO. Where did you download the official CM13 from?
Currently I'm on Global rom 8.1.2.0 ROOTED with SuperSU and Xposed Framework ..
Lately, update of 8.1.3.0 has been rolled out,
so I would like to update my device..
Since ROOTED device does not receive OTA update, I like to UNROOT first and then root it again after update..
Anyone cares to help me in this case?
I need a guide to fully unroot and remove the xposed framework so OTA update can be achieve..
Thanks all
I think just Reflash your MIUI room . then dont root it .
Or if you have SuperSU . i think it have option to "Full Unroot" .
You can't manually download it and update through updater app? It should restart with twrp instead of stock recovery and install the new version i guess
mysa50 said:
You can't manually download it and update through updater app? It should restart with twrp instead of stock recovery and install the new version i guess
Click to expand...
Click to collapse
I dont see anyone uploaded the OTA file for 8.1.3.0 from 8.1.2.0 around 200MB..
moreover, I heard people said the OTA file only can be flashed using stock recovery & non-rooted device. if rooted you will fail .
OTA Update
izzurin said:
I dont see anyone uploaded the OTA file for 8.1.3.0 from 8.1.2.0 around 200MB..
moreover, I heard people said the OTA file only can be flashed using stock recovery & non-rooted device. if rooted you will fail .
Click to expand...
Click to collapse
Absolutely correct, you must never update OTA with Custom recovery. This will lead to a bricked phone and you'll then have to clean flash the stock rom(Erases Internal Storage). Unfortunately, I learned the hard-way and landed-up losing all the data in my Internal Storage.
izzurin said:
Currently I'm on Global rom 8.1.2.0 ROOTED with SuperSU and Xposed Framework ..
Lately, update of 8.1.3.0 has been rolled out,
so I would like to update my device..
Since ROOTED device does not receive OTA update, I like to UNROOT first and then root it again after update..
Anyone cares to help me in this case?
I need a guide to fully unroot and remove the xposed framework so OTA update can be achieve..
Thanks all
Click to expand...
Click to collapse
You can very well uninstall Xposed and full-unroot SuperSU, however, I'm not sure whether it will be needed.
I would suggest taking a FULL NANDROID backup including Internal Storage and then performing the following steps (at your own risk):
Perform full-unroot from SuperSU app
Uninstall Xposed from TWRP
Flash stock recovery from TWRP
Update OTA from Updater App
Flash TWRP
Flash Xposed & SuperSU from TWRP
Btw, how did you get OTA update for 8.1.3.0 when its still not listed in the website?
Even if the ota is downloaded in .zip format? I remember a xiaomi forum where the op explained that he updated his Rom with twrp using updater app without issue. I must say he didn't downloaded via updater app but on a dedicated thread and then selected the Rom in the updater app menu.
Sorry if my guess was a Bad Idea and can lead to soft brick !!
i have just used the twrp recovery to get the full root
I'm on v11.0.10.0.QFQEUXM, can't install the next update, every time I try it just reboots and tells me the update failed. Anyone have a solution?
bootloader is locked and I'm not using any custom rom if that matters.
In case anyone has a similar issue I fixed it by clearing data for google mobile services and google play. I guess a corrupt update file got stored somewhere.
The update can be installed via recovery, also if you are in stock. Reboot into recovery and select install update from sd. You can download the stock recovery latest firmware from many sites on Internet
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
I you have backup of efs partation of just restore that via twrp
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try?
characterdivide said:
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try
Click to expand...
Click to collapse
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Try to flash this
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
characterdivide said:
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
Click to expand...
Click to collapse
Yes
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
Can you tell me what happened actually while updating? Did you successfully flashed new update in twrp or some else
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
So
characterdivide said:
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
Click to expand...
Click to collapse
Someone told me that after downloading incremental update package ROM Boots to twrp but failed to flash update and nothing happened he booted to old OS
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
characterdivide said:
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
Click to expand...
Click to collapse
So you have to flash old roms boot.img it will. Help to back everything
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Give me V10 stock image FOR DN 2101
And after flashing this will our TWRP avilable or Not agian?
Done
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Im having same issues as you could help me out what image did you use and how. Thanks in advance.