Develop Bugs

New HTC One M9 Verizon Update?

Anyone know what this is for?

Jrocker23 said:
Anyone know what this is for?
Click to expand...
Click to collapse
Hm. 612 megs. That could be....well let's see.
Sent from my Nexus 6 using Tapatalk

Installed and currently on the Android is upgrading/Optimizing apps screen...... Hopefully won't take too much longer.

software repair patch for 5.1 as told by vzw customer service. what it is repairing i dont know
3.10.605.7 / Base: 2.12.C1144073

Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/

SnoStorm said:
Nothing different.... Seems just like a security patch.
http://www.verizonwireless.com/support/htc-one-m9-update/
Click to expand...
Click to collapse
One can only wonder what the heck verizon does to their software such that it requires a 612meg security patch huh?
Anyhow.. Time to use that nandroid i posed in the dev section to accept the OTA.. -or- I will post an updated one later this evening.

Probably 600mb of updated NFL bloatware included and the rest just the security update.

Any word yet on whether this is really just a 612Meg security patch?

jtommyj said:
Any word yet on whether this is really just a 612Meg security patch?
Click to expand...
Click to collapse
yup, nothing special

Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.

baune7 said:
Anyone know if letting this thing run and update will break root? I'm stock, rooted. Don't want to lose that and not be able to get it back myself.
Click to expand...
Click to collapse
are you SOFF? if so, you will be fine

Yes.. I'm s-off and unlocked. So after it updates, will it still be rooted? Or would I havery to re-root it? I'm just worried because my cable Internet isn't working for a few days and I need my wifi tether. Thanks

Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=sharing
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=sharing

gumbyx84 said:
Ran into an issue with this update. It failed to install on 11/3 with a error code 409, but when I try to download it again by selecting "Check for new system updates" it says I have the latest update. I've rebooted a number of times and it shows up every time. From what little information I can find online, I have to reset my phone to factory then attempt to update again. I want to avoid this so here I am.
I'm on my phone so I can't properly upload the screenshots. I posted Google Drive links for now
https://drive.google.com/file/d/0B__V8WYcxeW8YWdsU1kyMmZOcFk/view?usp=docslist_api
https://drive.google.com/file/d/0B__V8WYcxeW8dkVxOXktZXZHcVU/view?usp=docslist_api
Click to expand...
Click to collapse
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk

dottat said:
Flash the custom firmware zip and restore the nandroid I posted of the update. Then wipe data for the app htcdm. Flash supersu.zip and you're done.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted.
Update: I decided to just to a factory reset. Thankfully it worked and I am at the latest firmware.

So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.

baune7 said:
So I've tried letting this update run a couple times. Downloading for the third time as I write this. When it tries to install, it just reboots into TWRP recovery and does nothing. Then I restart the phone and basically start the process all over again. Any guidance on how to get this squared away?? I met one of the members here with a card who S-offed, unlocked, rooted, my phone which I'm thankful for. Just want to be stock rooted is all. Don't really do much with custom roms on this phone. Thanks.
Click to expand...
Click to collapse
I'm pretty sure you need stock recovery to take an OTA.

SigLover21 said:
I'm pretty sure you need stock recovery to take an OTA.
Click to expand...
Click to collapse
Ok.. Thanks.. I'll have to check into that

Latest update MHC19J how to flash twrp

So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).

What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.

HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.

You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492

Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]

HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.

HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe

wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!

Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.

HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.

Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!

Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.

so unlocked my bootloader on my verizon PixelXl, and adb'ed Root-marlin-pixelxl but..

i mean its been 10 minutes, but still stuck on bootloop any ideas?

iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
Out of date ADB can cause this. I have seen it a few times reported by other people.
Try rebooting PC then reboot phone back to boot loader and use THESE adb and fastboot apps. I copied the from the latest SDK Manager
If that does not resolve then post back

iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
You should probably include a screenshot of everything you did in the command prompt... boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk

david.degraw54 said:
boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Good point!

Scott said:
Good point!
Click to expand...
Click to collapse
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk

david.degraw54 said:
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.

Scott said:
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Click to expand...
Click to collapse
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk

david.degraw54 said:
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Agreed! But on the same note, in the OP's defense there is not a very clear Q/A thread that tells you what you need to do. Everything is scattered. However, that is not anyones fault. This device is new to "ALL" of us. The whole SLOT thing, etc. Its all new unless you had a Google Chromebook. So I cant much blame people with issues. The good thing... 99.99% of the issues posted can be fixed with some patients. :good:

i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?

iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Just ignore it, it's due to the unlocked bootloader
Sent from my Pixel XL using Tapatalk

anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .

iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Nothing you can do about that at this time. I am sure someone will hack the aboot or hboot, which ever on an HTC device to remove it. For now wear it as a badge of pride :highfive:
iKenta said:
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
Click to expand...
Click to collapse
Could have been. I would recommend you not install TWRP at this time. Its finicky but being worked on. I know for fact it will be great soon.
I hope @Chainfire updates his Flash Fire. Easier to use than TWRP!

[DOWNGRADE] Android 8.1 to 8.0

Hello Guys,
First sry for my bad English im from Germany
Today i have downgraded my Google Pixel 2 XL 8.1 (DEZ. PATCH) to 8.0 (SEP. PATCH)
I know this isnt possible but i do it.
Here is what i do:
First i search here in the Forums a fix for the multitouch Bug since 8.1, i try all methods but nothing have work for me...
So i try to downgrade my Pixel 2 xl from 8.1 to 8.0 with the official Factory Image Files from Google but it isnt work for me because my Phone say (after i try the OTA Update via sideload) that i have already an newer Version of Android installed.
So what to do?
I Install the latest Factory Image from Google (8.1 Jan.Patch)
After the Install i stoped the First Start of my Phone and Go Back to bootloader, than i try to Lock my bootloader via ADB. After the Lock i See an Message in my Phone Like "there is noch System installed on your device, device cant Start" Or something Like that.
Now i Boot Back to bootloader and unlock my Phone again but that error stay there and my Phone will not Boot.
I think OK there noch System installed on my Phone now and maybe i can flash the factory Image from the Google Developer Site.
I downloaded the First Image File "8.0.0 (OPD1.170816.010, Sep. 2017)
Booted my Phone to bootloader and run the Script "flash-all.bat"
The installation finished without any errors and my Phone booted without any Problems.
I think "OK cant be" but i Go to settings and Check the Android Version i have installed, and i See im Back to Android 8.0.0

Ok

blaze9090 said:
Ok
Click to expand...
Click to collapse
I have a Question:
After the downgrade to 8.0 i checked the System Update in the settings, but it says that im on the latest Version of Android
Any Fix for that?

Flash latest factory images...

imex1 said:
... I think "OK cant be" but i Go to settings and Check the Android Version i have installed, and i See im Back to Android 8.0.0
Click to expand...
Click to collapse
What a very long post for nothing. Go to the Google developer website, download the latest full January build and flash it with the script according to the instructions given on the same page. Then drink a beer. Prost. :good:

alia5 said:
Flash latest factory images...
Click to expand...
Click to collapse
I dont wanna Go to 8.1 yet because of the Multitouch Bug in Games, waiting for an official fix by Google
I try to Upgrade Googles OTA Image via sideloade after the fix, Thanksgiving you

v12xke said:
What a very long post for nothing. Go to the Google developer website, download the latest full January build and flash it with the script according to the instructions given on the same page. Then drink a beer. Prost. :good:
Click to expand...
Click to collapse
Ehm thanks for the Info but i Post my way to DOWNGRADE from 8.1 to 8.0, because its NOT official possible...
But thx

imex1 said:
Ehm thanks for the Info but i Post my way to DOWNGRADE from 8.1 to 8.0, because its NOT official possible...
But thx
Click to expand...
Click to collapse
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:

v12xke said:
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
Click to expand...
Click to collapse
Ah okay, thx for the Info, all i knew ist that its NOT possible to downgrade from 8.1 to 8.0
But seems im wrong, but hey thx to know
Now i can deleat my Post, thx Guys for Help.. good Community in XDA! Cheers

No worries mate! Ayinger Oktober Fest-Märzen | Privatbrauerei. Prost. My favorite. Still have one full case / 20 L. In Texas!

v12xke said:
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
Click to expand...
Click to collapse
So, tell us how you're supposed to downgrade from 8.1 to 8.0? Especially since Google added safeguards to prevent this. Maybe I'm missing something, but to my knowledge it's not 'supposed' to be possible.

stumpy352 said:
So, tell us how you're supposed to downgrade from 8.1 to 8.0? Especially since Google added safeguards to prevent this. Maybe I'm missing something, but to my knowledge it's not 'supposed' to be possible.
Click to expand...
Click to collapse
Unlock bootloader, unlock critical, flash 8.0 image

TheSt33v said:
Unlock bootloader, unlock critical, flash 8.0 image
Click to expand...
Click to collapse
Is that all that's needed? Unlocking the critical partition?
Does that circumvent Google's anti roll back?

stumpy352 said:
Is that all that's needed? Unlocking the critical partition?
Does that circumvent Google's anti roll back?
Click to expand...
Click to collapse
Yes. I don't know the details of Google's anti rollback measures, but I don't think they were meant to apply to unlocked bootloaders. Google allows bootloader unlock to be friendly to developers who probably want to test their apps on different firmware versions. What would be the point of locking them out of various firmwares? In fact, what's the point of an unlockable bootloader at all if you're going to still put restrictions on flashing?
The reason why the OP thought he needed to find out a clever downgrade method was because he was trying to use an OTA to downgrade. OTAs never allow downgrading, and I don't think they ever have. This is nothing new. The factory images, however, will always work as long as both "fastboot flashing unlock" and "fastboot flashing unlock_critical" have been performed beforehand with the latest version of fastboot.

TheSt33v said:
Yes. I don't know the details of Google's anti rollback measures, but I don't think they were meant to apply to unlocked bootloaders. Google allows bootloader unlock to be friendly to developers who probably want to test their apps on different firmware versions. What would be the point of locking them out of various firmwares? In fact, what's the point of an unlockable bootloader at all if you're going to still put restrictions on flashing?
The reason why the OP thought he needed to find out a clever downgrade method was because he was trying to use an OTA to downgrade. OTAs never allow downgrading, and I don't think they ever have. This is nothing new. The factory images, however, will always work as long as both "fastboot flashing unlock" and "fastboot flashing unlock_critical" have been performed beforehand with the latest version of fastboot.
Click to expand...
Click to collapse
The only reason why i open this thread is, that after i try to downgrade to 8.0 my devise go to bootloop, after i flash back to 8.1 it works fine...so with my post i downgraded to 8.0 and its still work fine, im now on 8.0 with nov patch, the only reason why i downgrade is the stupid Multitouch Bug in games, so im waiting for official fix by google

when is the new security update for August out guys?

Just wondering when the new security update will be out as I feel the last one is making my battery drain quite a lot. Tried all the normal routine stuff and still nothing specially after two factory resets. Here is hoping that with the new software it will be fixed

Hey Goku80, judging solely by past-trends, it should most certainly be out today.

It's live guys! https://dl.google.com/dl/android/aosp/crosshatch-pq3a.190801.002-factory-15db810d.zip

Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?

BoboBrazil said:
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
Click to expand...
Click to collapse
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually

ota is not here yet

Goku80 said:
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
Click to expand...
Click to collapse
The OTA can be flashed using stock recovery. No wipe.

spotmark said:
The OTA can be flashed using stock recovery. No wipe.
Click to expand...
Click to collapse
True but means I need to use ADB which I don't have a pc

Goku80 said:
True but means I need to use ADB which I don't have a pc
Click to expand...
Click to collapse
You can flash it as long as your BL is unlocked. It has nothing to do with root. You still need to use the flash-all batch file though, so a computer is still necessary.