hi
all, i have nexus 6 device with 6.0 MRA58R and open bootloader and it was update by the device from google,still before that i try to do root and didn't succeedwith 5.1, so i go back to 5.1 and it was update as i said but the device is stuck by the start or just by regular use...something is wrong and i don't know what, there is also sound when it stuck like A screech sound and it stuck
what to do next?
thanks
If your bootloader is unlocked, as mentioned in your other thread, download a stock image from Google and flash its components (except userdata.img) using ADB. As a result of your tinkering, something got messed up on the device, and flashing the stock image should resolve that.
tried these ...didn't help,it stuckes even after good flash with adb cause with OTA it stucks at the middle
You flashed MMB29Q from the shamu section of the page here? That is the absolute latest factory image available. There should be NO OTA update available.
first of all i tried to download the OTA cause i was with root and did unroot and i want to saw thet it get's the OTA's correct ,then i installed the version as you write, but still when i start the wifi or in regular use the device can be stuck and restart.
any idea to solve it? even in safe mode it stucks
No, not really. Like you mention in your other thread, it appears to be a hardware problem.
For the record, downloading the OTA updates is a waste of time when the latest factory image is available. When you get your replacement device, assuming it's not already on 6.0.1, install the image from the link I gave you, as it already includes in the image all the updates Google has released for Android 6.0.1.
Related
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.
RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged
Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.
I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
AbhiM7 said:
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
Click to expand...
Click to collapse
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
hellcat50 said:
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
Click to expand...
Click to collapse
Hi, I've already downloaded this very stable file and tried flashing using TWRP
AbhiM7 said:
Hi, I've already downloaded this very stable file and tried flashing using TWRP
Click to expand...
Click to collapse
I read something about wrong batteries causing this problem. Do you use the original battery?
hellcat50 said:
I read something about wrong batteries causing this problem. Do you use the original battery?
Click to expand...
Click to collapse
I though of running a diagnosis check by dialing *#808# and looked up Charger option, it shows the battery as "itech_3000mah"
is that original?
I had given the phone to repair for water damage to a professional service chain (Not OnePlus, some company here called Yaantra). I've heard from talking to an official repair person of OnePlus that fake batteries are not possible for OnePlus.
The battery works absolutely alright, charges up nicely and I get decent SOT. Can't complain at all.
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Maybe Oxygen Updater has full download link?
BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.
Did you flash stock recovery to both slots the last time?
g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?
BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.