Related
For people looking for the latest YP2 firmware release: Today Yota officially released the 1.87 firmware. It's still Lollipop 5.0, and Russian region only at the time of writing. It should however be pretty usable for e.g. EU too if you're eager, english UI language is included in the RU ROM too). I haven't tried this firmware yet, but I intend to.
If you're currently on RU firmware, check for a FOTA update (about phone->system updates).
If you're on another region firmware and are patient, just wait till it shows up as a FOTA update anytime soon.
If you're on another region firmware and a bit less patient and a bit more daring, you can download RU1.1.87 here, and flash it with yotaflasher. Backup first, own risk etc.
Thanks!
YotaReader's been beautiful! :good:
Have successfully updated to 1.87 and then booted twrp recovery to flash superSU. Can confirm root is successful and the updated room works well in the UK
MAX_G said:
Have successfully updated to 1.87 and then booted twrp recovery to flash superSU. Can confirm root is successful and the updated room works well in the UK
Click to expand...
Click to collapse
Any noticeable improvements...?
Ta
Battery life now stems fine with yota energy showing five days per charge, there are some new yota apps and double click features on the screens, even android auto now works
Is German also as UI language available?
MAX_G said:
Have successfully updated to 1.87 and then booted twrp recovery to flash superSU. Can confirm root is successful and the updated room works well in the UK
Click to expand...
Click to collapse
Did you get an OTA or flash the rom from twrp?
First I loaded the usb ADB drivers then unlocked the Bootloader from the command line after that I used yotaflasher tool to load the new ROM that I downloaded from their website and then sideloaded the TWRP recovery partition to help flash the superuser zip.
I'm wondering how to update using yotaflasher exactly and where to put my downloaded file? because when i tried that my phone just got stuck on Android logo, I fixed that but I want to know and understand what i did wrong
you need to move the firmware files to the same location as the Flasher tool
Mine is C:\Program Files (x86)\yotaphone_flasher ( your directory may be different )
if you got stuck on android it could be a bad download or it could be just doing the update.
IIRC mine was stuck on android initially but after a rebbot it started updating all the android apk files and then booted and ran fine.
Max
All up and running and all good.
I can confirm the procedure is the same as the last one (for those having used Yotaflasher. I hadn't but it's pretty straightforward).
Backup > unroot > flash stock recovery > yotaflasher (with firmware in right directory) > boot > flash su > ....... > profit!
Thanks again SteadyQuad
MAX_G said:
you need to move the firmware files to the same location as the Flasher tool
Mine is C:\Program Files (x86)\yotaphone_flasher ( your directory may be different )
if you got stuck on android it could be a bad download or it could be just doing the update.
IIRC mine was stuck on android initially but after a rebbot it started updating all the android apk files and then booted and ran fine.
Max
Click to expand...
Click to collapse
I personally didn't have to unlock or root the phone. I just downloaded yotaflasher and looked on the net for the right usb drivers. Then downloaded the rom with yotaflasher (4.4.3 EU) and flashed it. Didn't have any issue with file download or location it cause Yotaflasher did everything for me. After reboot it started to upgrade and now I am downloading via OTA 1.60 EU. Think will stop with it , waiting for the next EU rom. Will report in the next days any bug if I find.
Cheers
PS: Max I looked at your signature and saw that you own G. Glass too, if I am not wrong. Maybe I will ask you a couple of questions if you do not mind in the future cause mine went crazy in the last period and cannot understand what is the problem. Anyway I will try to read a bit over the net before bothering you. Cheers
Seem that 1.87a EU has been made available on Yota official ftp site. Anyone has tried it yet? I checked OTA update with the 1.60 EU installed, but as for now, I do not see any update available. Just would prefer not to use yotaflasher , cause I prefer OTA due to the fact it seems to me safer
lexman941 said:
Seem that 1.87a EU has been made available on Yota official ftp site. Anyone has tried it yet? I checked OTA update with the 1.60 EU installed, but as for now, I do not see any update available. Just would prefer not to use yotaflasher , cause I prefer OTA due to the fact it seems to me safer
Click to expand...
Click to collapse
Just got EU 1.87 OTA Update!!! Installing now!!
Rarelyamson said:
Just got EU 1.87 OTA Update!!! Installing now!!
Click to expand...
Click to collapse
Just got the update as well - attached some screenshots!
Looks like the russian firmware are now another few versions ahead ;-( ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
irl_x10_user said:
Just got the update as well - attached some screenshots!
Looks like the russian firmware are now another few versions ahead ;-( ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Click to expand...
Click to collapse
Like the double tap to wake, although not sure how my pocket will handle it!?
Hopefully it will also improve my battery!
Can anyone share it with me please? I see no one has uploaded it yet.
ahrion said:
I see no one has uploaded it yet.
Click to expand...
Click to collapse
Because the phone is not out yet! (In the west)
ahrion said:
Can anyone share it with me please? I see no one has uploaded it yet.
Click to expand...
Click to collapse
I'm no dev but I have to wonder, would the software have files written/coded in English inside of it. is it a convention ?
I would like to know if there is the possibility of installing the original firmware international version of axon7 Chinese model without root?
Unless the software checks at the start of the flashing process fail to match ROM with phone (so you don't try to flash a ROM for a different phone, which would brick it) it should work. As an aside, root/no root does not affect flashing, locked/unlocked boot-loader does but for ROMs signed by the manufacturer this isn't an issue either
ahrion said:
Can anyone share it with me please? I see no one has uploaded it yet.
Click to expand...
Click to collapse
i have the 4GB modle ...can you tell me how i can i do it
am rely to help if you can root the device and get it clean without chines apps and am facing not compatible apps from google play and that rely frustrating in addition i can even install some apps related to my google plus or banks app it refuse to install ( not compatable )
abunhyan said:
i have the 4GB modle ...can you tell me how i can i do it
am rely to help if you can root the device and get it clean without chines apps and am facing not compatible apps from google play and that rely frustrating in addition i can even install some apps related to my google plus or banks app it refuse to install ( not compatable )
Click to expand...
Click to collapse
expect ZTE releases the International firmware, then let's install on the Chinese model
I hope so......
how can i flash Stock ROM with twrp, when i make install from Zip, it died with this Error Message:
" Updater process ended with Error: 8
Error installing zip file'external_sd/update.zip"
and when i flash as Image, i have many Images like boot, echarge, mdtp, recovery and splash.img... whichs the right that after reboot my phone is boot and install the rom?
Or anyone can say me why starts my wifi(has no mac adress) and the fingerprint(can not add fingerprint) not on my Phone A2017G B03?
Schattenklinge said:
how can i flash Stock ROM with twrp, when i make install from Zip, it died with this Error Message:
" Updater process ended with Error: 8
Error installing zip file'external_sd/update.zip"
and when i flash as Image, i have many Images like boot, echarge, mdtp, recovery and splash.img... whichs the right that after reboot my phone is boot and install the rom?
Or anyone can say me why starts my wifi(has no mac adress) and the fingerprint(can not add fingerprint) not on my Phone A2017G B03?
Click to expand...
Click to collapse
It seems that a mismatch between the system and boot causes issues with WiFi.
thx i know, but with the 2 adb calls to modemst has not worked...
and i am not shure we i can flash the boot and the /system with the right img.
Marshmallow factory images never a problem flashing. Ever sense Nougat came along I can not flash the system.img in fastboot without getting the dreaded "error: cannot load 'system.img' ". I've tried the trick by adding the extension to flash smaller chucks of data with the command line.
I used flashfire to update with no problem but this takes all the joy of doing it manually.
I know other users have had this problem also. Did anyone come up with a solution for this problem yet? Thanks.
Solved:
Seems that my Platform-Tools program was not updated as I had thought. I had thought it was a "One Button" update type of program but apparently certain parts or updates need to be updated first then other parts can be updated. So long story short for anyone else having this problem make sure the all updates are applied to Platform-Tools.
Thanks for all the help!
Yes this has happened to me and I was stuck almost. I had to load the system image to a otg and flash it in twrp and that's when it would go.
Have you tried flashing using LxMultiTool
Leeum said:
Have you tried flashing using LxMultiTool
Click to expand...
Click to collapse
I have not tried. I will on next update if I can't find any other fix. I also forgot to mention that I updated all the libs and what not in the Google adb program installed on my PC. Also I used Winrar to decompress the factory image if that makes a difference, it hasn't been a issue in the past with marshmallow.
I suspect you are not running the latest version of platform tools/adb/fastboot. Find the latest version of platform tools and you should be good.
Pig Vomit said:
I suspect you are not running the latest version of platform tools/adb/fastboot. Find the latest version of platform tools and you should be good.
Click to expand...
Click to collapse
Thanks for the info. I did update to platform tools when nougat was released last month, but will check again. I had the same issue then also. I even installed the 7.0 files. Maybe I'm missing something.
As i said, Download LxMultiTool. It has adb and everything. I flashed latest NRD90U 7.0.0 Stock rom without issues. It also lets you lock/unlock bootloader, sideload files, install recovery
How do you load the system image to otg.?
Sent from my HUAWEI MT7-TL10 using XDA Free mobile app
Solved, thanks guys.
After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.
since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.
HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset
medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:
MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?
Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097