It's available via OTA
JDBarlow said:
It's available via OTA
Click to expand...
Click to collapse
Are you able to use arter kernel with this update?
kountry83 said:
Are you able to use arter kernel with this update?
Click to expand...
Click to collapse
should be able to, I don't see why it wouldn't work
Arter works fine with it. I updated this morning.
Do you have to have stock recovery + locked bootloader to install?
BeardKing said:
Do you have to have stock recovery + locked bootloader to install?
Click to expand...
Click to collapse
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace
chris5s said:
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace
Click to expand...
Click to collapse
What do you mean by flash the system update? Sorry I'm new here, but what exact steps did you do? I am currently on a rooted MR2 with Arter 's kernel.
Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update
finixs said:
Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update
Click to expand...
Click to collapse
compared to MR2, we probably will need to wait for months until razer puts the factory images on their dev-page...
I really can't understand what takes so long for that last step. Just upload that crap and you're done, razer
Can the update be flashed in TWRP without disturbing Magisk or Arter's kernel? I've grabbed the update zip via a link I found by generating a bug report in the developer options and searching for "System_Update". I'm just wondering if it's safe to flash over everything.
Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.
Monopod said:
Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.
Click to expand...
Click to collapse
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace
chris5s said:
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace
Click to expand...
Click to collapse
Arter97 R12 Kernel with Twrp and magisk root.
Monopod said:
Arter97 R12 Kernel with Twrp and magisk root.
Click to expand...
Click to collapse
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?
chris5s said:
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?
Click to expand...
Click to collapse
No mods not even F2fs and Vold, for the stock boot image I simply fastboot flash it.
I flashed f2fs, wondering if that's why I can't flash update even after flashing stock kernel? ?
Peace
https://github.com/RadekBledowski/Razer_Phone_mods/blob/master/magisk_patched.img?raw=true
here's magisk patched version
to flash arter kernel you have to flash it via zip not fastboot so flash it first via fastboot and flash it again but in twrp as zip
So what I see is you can update without reloacking your bootloader by... (I'm asking if this is right)
1. Fastboot flash stock boot.img
2. Update normally
3. Reflash magisk, your custom kernel and what not.
Correct?
I've tried flashing back to stock kernel but it didn't work for me.
I usually perform the "reset to factory" task from the razer images (properly commenting the line that erases userdata)
After that you just are with original stock and you can update via OTA as usual.
Related
I am having some issues with an AOSP 4.3 rom. I would like to stay on 4.3 but with the complete stock rom directly from Google. Is it possible to have root on the ota stock 4.3 rom? I would rather be back on 4.2.2 stock/rooted than rooted 4.3 with too many glitches
Due to some security changes in 4.3 root won't survive an OTA. You'll need the stock recovery to update via OTA. Subsequently, you'll need a custom recovery to flash the latest version of SuperSU and have root again.
What's your current state?
Mercado_Negro said:
Due to some security changes in 4.3 root won't survive an OTA. You'll need the stock recovery to update via OTA. Subsequently, you'll need a custom recovery to flash the latest version of SuperSU and have root again.
What's your current state?
Click to expand...
Click to collapse
I'm on a rooted 4.3 AOSP ROM with TWRP 2.6.0.0. Did a regular wipe while I was 4.2.2 before I flashed. Can you flash a custom recovery on unrooted ota 4.3?
patrickjaden said:
I'm on a rooted 4.3 AOSP ROM with TWRP 2.6.0.0. Did a regular wipe while I was 4.2.2 before I flashed. Can you flash a custom recovery on unrooted ota 4.3?
Click to expand...
Click to collapse
yes. you dont need root for a custom recovery.
patrickjaden said:
I'm on a rooted 4.3 AOSP ROM with TWRP 2.6.0.0. Did a regular wipe while I was 4.2.2 before I flashed. Can you flash a custom recovery on unrooted ota 4.3?
Click to expand...
Click to collapse
Yes, you can.
Did you also flash the latest bootloader and radio? That's important, specially the radio (to avoid compatibilities issues with ROMs).
Mercado_Negro said:
Due to some security changes in 4.3 root won't survive an OTA. You'll need the stock recovery to update via OTA. Subsequently, you'll need a custom recovery to flash the latest version of SuperSU and have root again.
What's your current state?
Click to expand...
Click to collapse
Mercado_Negro said:
Yes, you can.
Did you also flash the latest bootloader and radio? That's important, specially the radio (to avoid compatibilities issues with ROMs).
Click to expand...
Click to collapse
No, that's probably why I'm having so many problems. Where can I find them? and can they be flashed in TWRP
twrp flashable. since youre on tmobile, the hybrid radios are good, thats if you want to use tmobiles lte http://forum.xda-developers.com/showthread.php?t=2087227
patrickjaden said:
No, that's probably why I'm having so many problems. Where can I find them? and can they be flashed in TWRP
Click to expand...
Click to collapse
simms22 said:
yes. you dont need root for a custom recovery.
Click to expand...
Click to collapse
So theoretically if I revert to stock 4.2.2 I can update to the OTA, then flash a custom recovery (I assume I can do that via the toolkit?), then flash the root file, I'll be good? Do I need to relock my bootloader?
patrickjaden said:
No, that's probably why I'm having so many problems. Where can I find them? and can they be flashed in TWRP
Click to expand...
Click to collapse
You can find them here:
http://forum.xda-developers.com/showthread.php?p=43528263
I'm not sure if these zip files are flashable, though.
I'd strongly suggest you to download Google's Factory Images from:
https://developers.google.com/android/nexus/images#occamjwr66v
And extract both from there to be safe (bootloader and radio images).
You won't be able to flash these images from TWRP. In this case, you'll need to use fastboot commands to flash them (but it will be safer, in my opinion).
If you're not familiar with fastboot command lines and don't have the Android ADT Bundle either please let me know, I can walk you through.
[EDIT] I found another link for the radio (a.k.a. baseband) and bootloader. Here it is:
https://www.copy.com/s/JniBu/4.3 files (mako)
I'm 100% sure these are proper versions but since they're images you'll have to flash them via fastboot.
Mercado_Negro said:
You can find them here:
http://forum.xda-developers.com/showthread.php?p=43528263
I'm not sure if these zip files are flashable, though.
I'd strongly suggest you to download Google's Factory Images from:
https://developers.google.com/android/nexus/images#occamjwr66v
And extract both from there to be safe (bootloader and radio images).
You won't be able to flash these images from TWRP. In this case, you'll need to use fastboot commands to flash them (but it will be safer, in my opinion).
If you're not familiar with fastboot command lines and don't have the Android ADT Bundle either please let me know, I can walk you through.
[EDIT] I found another link for the radio (a.k.a. baseband) and bootloader. Here it is:
https://www.copy.com/s/JniBu/4.3 files (mako)
I'm 100% sure these are proper versions but since they're images you'll have to flash them via fastboot.
Click to expand...
Click to collapse
I've never really done fastboot before. Is this way easier than flashing stock 4.2.2 and going from there?
patrickjaden said:
I've never really done fastboot before. Is this way easier than flashing stock 4.2.2 and going from there?
Click to expand...
Click to collapse
No, it's not easier at all but you'll learn a lot in the process which will surely help you a lot in the future if you run into problems.
It's up to you
Mercado_Negro said:
No, it's not easier at all but you'll learn a lot in the process which will surely help you a lot in the future if you run into problems.
It's up to you
Click to expand...
Click to collapse
I kinda wanna revert to 4.2.2 and OTA update to 4.3 so I can be 100% stock. I don't know if I can trust the dev who's making this AOSP ROM. Does my bootloader need to be locked to update?
bootloader will need to be unlocked. thats easy, you dont need a toolkit, you wont learn anything that way. you will need to install fastboot to your computer. you boot into your bootloader, connect to your computer via usb, start fastboot, open a command window, type.. fastboot devices(this is to check if fastboot sees your device), then type.. fastboot oem unlock(then look at your n4 screen to press yes or no). this will unlock your bootloader. download your recovery to your computer, stick it into the same folder as fastboot(do this before you start), then type in the command window.. fastboot flash recovery recoveryname.img(this will flash your custom recovery). then, in the bootloader, press your volume keys to scroll to the word recovery, press your power button to boot into recovery.
patrickjaden said:
I kinda wanna revert to 4.2.2 and OTA update to 4.3 so I can be 100% stock. I don't know if I can trust the dev who's making this AOSP ROM. Does my bootloader need to be locked to update?
Click to expand...
Click to collapse
No, you don't need a locked bootloader to update via OTA.
Out of curiosity, how are you going to revert to 4.2.2 if you've never used fastboot command lines? You're in an AOSP 4.3 ROM right now, with 4.2.2 bootloader and radio. Do you have a flashable 4.2.2? That's the only way I can see it happen (unless I'm missing something which is probable).
Mercado_Negro said:
No, it's not easier at all but you'll learn a lot in the process which will surely help you a lot in the future if you run into problems.
It's up to you
Click to expand...
Click to collapse
Mercado_Negro said:
No, you don't need a locked bootloader to update via OTA.
Out of curiosity, how are you going to revert to 4.2.2 if you've never used fastboot command lines? You're in an AOSP 4.3 ROM right now, with 4.2.2 bootloader and radio. Do you have a flashable 4.2.2? That's the only way I can see it happen (unless I'm missing something which is probable).
Click to expand...
Click to collapse
Could I use the toolkit/is it usable with 4.3? Or is there a way to flash the stock via recovery?
patrickjaden said:
Could I use the toolkit/is it usable with 4.3? Or is there a way to flash the stock via recovery?
Click to expand...
Click to collapse
I'd never suggest any toolkit because you won't learn anything from it. I'm not sure how's current state of toolkits so I can't comment on their proper functioning with 4.3.
Mercado_Negro said:
I'd never suggest any toolkit because you won't learn anything from it. I'm not sure how's current state of toolkits so I can't comment on their proper functioning with 4.3.
Click to expand...
Click to collapse
Okay, is there a 4.2.2 zip I can flash that will let me get the OTA?
patrickjaden said:
Okay, is there a 4.2.2 zip I can flash that will let me get the OTA?
Click to expand...
Click to collapse
Sorry, I don't know if there's one.
is it possible to flash a hybrid radio onto stock 4.3?
patrickjaden said:
is it possible to flash a hybrid radio onto stock 4.3?
Click to expand...
Click to collapse
Yes, it is. You can pretty much flash any baseband on stock or ROMs. The question is, is it worth it? It may work flawlessly but it could also cause issues. I'd do it but I'd keep my eyes on it if something goes wrong all of a sudden.
my phone is bootloader unlock, does it mean I can flash the third part recovery like TWRP, and use it?
MY guess yes..
Sent from my LT30p using Tapatalk
allen_ho said:
my phone is bootloader unlock, does it mean I can flash the third part recovery like TWRP, and use it?
Click to expand...
Click to collapse
TWRP will not work on the OTA, yet. However, there is a working CWM in the HD forum. I flashed it to my M and have zero issues with it.
RikRong said:
TWRP will not work on the OTA, yet. However, there is a working CWM in the HD forum. I flashed it to my M and have zero issues with it.
Click to expand...
Click to collapse
I flashed the CWM recovery too...it does boot to recovery
but it seems to be some problem with CM11 package, the assert check shows my device ID is empty so the recovery just abort the installation.
I want to flash CM11-m6 snapshot....any ideas?
falleny said:
I flashed the CWM recovery too...it does boot to recovery
but it seems to be some problem with CM11 package, the assert check shows my device ID is empty so the recovery just abort the installation.
I want to flash CM11-m6 snapshot....any ideas?
Click to expand...
Click to collapse
CM11 won't work if you've updated. Apparently, the boot loader is updated and the ROMs haven't been updated for it.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
CM11 won't work if you've updated. Apparently, the boot loader is updated and the ROMs haven't been updated for it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Bad news...Looks like i will be stucked in full bloated stock rom for sometime...thank u
falleny said:
Bad news...Looks like i will be stucked in full bloated stock rom for sometime...thank u
Click to expand...
Click to collapse
You have an unlocked BL, just flash SU to get root, and delete/freeze apps. That's pretty much what I did and used Xposed on top of that.
I haven't tried it yet, buy couldn't you just rsd back to an earlier build then flash your custom ROM?
Sent from my XT907 using Tapatalk
I fastboot flash the lastest CWM recovery, but it didn't work for the CM 4.4.2 ROM, and twrp, it didn't work again. why? does the VFW rom change something?
allen_ho said:
I fastboot flash the lastest CWM recovery, but it didn't work for the CM 4.4.2 ROM, and twrp, it didn't work again. why? does the VFW rom change something?
Click to expand...
Click to collapse
None of the ROMs have been updated to work with the new recovery. Just give it time.
RikRong said:
None of the ROMs have been updated to work with the new recovery. Just give it time.
Click to expand...
Click to collapse
what's that mean?
do you mean the third part recovery didn't work cause the VFW rom?
allen_ho said:
what's that mean?
do you mean the third part recovery didn't work cause the VFW rom?
Click to expand...
Click to collapse
It means that none of the ROMs out right now will work with the new CWM. Also, quit trying flash TWRP. TWRP is not compatible with the new KK, yet.
Got it, many thanks
Root
My xt907 Has the OTA 4.4 update and an unlocked BL. I don't have a custom recovery installed anymore. Is it possible to flash SU or superuser and get root with fastboot. If so. Please help! Thanks. I'm ok with flashing CWN if need be. I just want root to install a Xposed and remove bloatware.
Ahoalton said:
My xt907 Has the OTA 4.4 update and an unlocked BL. I don't have a custom recovery installed anymore. Is it possible to flash SU or superuser and get root with fastboot. If so. Please help! Thanks. I'm ok with flashing CWN if need be. I just want root to install a Xposed and remove bloatware.
Click to expand...
Click to collapse
I'm pretty sure you can use fastboot/ADB to sideload zips, though I'm not super familiar with the commands so I wouldn't know how to explain it to you.
I am familiar enough with the commands, but I am unable to find the zips to flash. any help would be great.
Thanks,
Egg all over the face
I was one of the people who thought it would be cool to update to the OTA immediately without waiting and reading... I got the CWM recovery going and rooted stock 4.2.2 , but I really cant wait for TWRP to get updated so I can get back to my Rom, or really any supported Rom would be better then stock. I have only myself to blame.
Eclipse00 said:
I was one of the people who thought it would be cool to update to the OTA immediately without waiting and reading... I got the CWM recovery going and rooted stock 4.2.2 , but I really cant wait for TWRP to get updated so I can get back to my Rom, or really any supported Rom would be better then stock. I have only myself to blame.
Click to expand...
Click to collapse
Looks like the new TWRP is here, but still needs one tweak. Please follow this thread for updates.
http://forum.xda-developers.com/showthread.php?p=53189684
TWRP for KitKat Bootloader
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
It's out. Download factory images on the official site. Yay!
Link : https://developers.google.com/android/ota#top_of_page
changelog? does it fix the battery loss over night?
i have a question.
i'm on N5D91L with twrp installed. do i have to flash NRD91P and then NMF26F or can i skip the NRD91P?
thanks for the help!
Turtl3z said:
i have a question.
i'm on N5D91L with twrp installed. do i have to flash NRD91P and then NMF26F or can i skip the NRD91P?
thanks for the help!
Click to expand...
Click to collapse
You don't have to flash NRD91P. Android updates are always cumulative; you never have to flash versions other than the latest.
I am on official 7.0 right now. Is it possible to go the easy route and just flash Cache, System and Vendor img? Don't wanna reflash TWRP/root.
chinesecooler said:
I am on official 7.0 right now. Is it possible to go the easy route and just flash Cache, System and Vendor img? Don't wanna reflash TWRP/root.
Click to expand...
Click to collapse
don't need to flash cache. just flash boot, system and vendor and you should be good to go.
metpage said:
don't need to flash cache. just flash boot, system and vendor and you should be good to go.
Click to expand...
Click to collapse
Thanks but I am trying to avoid flashing boot.img as it means I will have to flash recovery and root again.
chinesecooler said:
Thanks but I am trying to avoid flashing boot.img as it means I will have to flash recovery and root again.
Click to expand...
Click to collapse
You can use flashfire to save root
sideloading now
EDIT: done and running.
chinesecooler said:
Thanks but I am trying to avoid flashing boot.img as it means I will have to flash recovery and root again.
Click to expand...
Click to collapse
You wouldn't have a working camera if you skip out on flashing the 7.1.1 boot.img.
Sent from my Nexus 5X using Tapatalk
Same radio same bootloader as previous versions or need to upgrade ?
Thanks all. I was stuck at the boot animation after only doing Cache, System & Vendor.
Had to reflash the whole set (except userdata), TWRP and SU.
For anyone worried about re-rooting and all... Download the Full Firmware package and flash it with FlashFire, just did it and it works perfectly, if you have any mods like the google assistant or "surround sound" mod, you will need to re-flash them but thats all.... easy as pie....
EDIT.... You will also need to re-do your build.prop edits if you did any....
So I tried the chainfire flashfire to flash the feb ota but nothing happened. im on rooted 8.1 but flashfire just stayed black screen for 15 minutes. how do i flash the Ota correctly?
xterminater07 said:
So I tried the chainfire flashfire to flash the feb ota but nothing happened. im on rooted 8.1 but flashfire just stayed black screen for 15 minutes. how do i flash the Ota correctly?
Click to expand...
Click to collapse
Download factory image...unzip it and fastboot radio, bootloader, vendor, boot and image, it wont erase your data,...easy and simple
You should use SuperXe its basically a twrp flashable stock image. It has amazing aroma installer when installing so you can choose things like pixelmod and charging led. As well as remove any Google apps you don't want.
scrin378 said:
Download factory image...unzip it and fastboot radio, bootloader, vendor, boot and image, it wont erase your data,...easy and simple
Click to expand...
Click to collapse
I saw this as one of the alternatives to flashfire, but I just thought I did something wrong with flashfire that is why it didn't work. So there is no other way to flash Ota besides this that you mentioned?
Exodusche said:
You should use SuperXe its basically a twrp flashable stock image. It has amazing aroma installer when installing so you can choose things like pixelmod and charging led. As well as remove any Google apps you don't want.
Click to expand...
Click to collapse
so if I flash this, and when the dev released the next monthly ota patch, do I just dirty flash over?
xterminater07 said:
so if I flash this, and when the dev released the next monthly ota patch, do I just dirty flash over?
Click to expand...
Click to collapse
Yes I don't see why not.