Database Info

TF700 bootlooping on twrp splash screen

Hi
After trying to install crombi on tf700 using twrp 2.7 something went wrong and now tablette is bootlooping on twrp screen.
Cpnnected the tablette to laptop and nothing appears in the M'y Computer Windows.
Checked on device manager and found 'transformer' writen there with yellow exclamation Mark.
Tried to update driver with nô success.
Any help Will be greatly appreciated
Thanks

We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.

berndblb said:
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
Click to expand...
Click to collapse
Hi and thanks for the reply.
The tablet was on the latest Cromi-x and bootloader.
Did a full wipe and begun installing crombi
The tablet was stuck a long time on formatting so I had to regoot
After the reboot it was unable to moiunt E,
Tried to do another full wipe and now the tablet is just bootlooping on the TWRP splashscreen.
Any suggestion?

Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.

berndblb said:
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
Click to expand...
Click to collapse
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?

What about fastboot? Boot with Volume Down and Power. Then try
'fastboot devices'
Sent from my DROID4 using Tapatalk

allotesting said:
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
Click to expand...
Click to collapse
Nothing? something must come up. What does it say? Command not found? No devices found?

sbdags said:
Nothing? something must come up. What does it say? Command not found? No devices found?
Click to expand...
Click to collapse
Hi
When I try the fastboot devices command it comes back to the invite with nothing written
When I try the adb devices nothing after list of devices attached
And the tablet keeps on bootlooping on the teamwin splash screen
And as already stated in device manager I find the mention transformer with yellow mark

Hi
Something new after I tried to update driver
Tried the fastboot command and it found something
It gives me s bunch of numbers and letters and recovery at the end
Is it good doctor?

Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:

allotesting said:
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
Click to expand...
Click to collapse
Are you in the boot loader when you issue that command?

By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks

allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Yes that is normal. What happens when you flash twrp with fasboot. What does it report back?

allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Ok, I think we need to clear up some things:
If the tablet is bootlooping it cannot be in the bootloader and fastboot mode (you are in the bootloader menu when you see the 3 icons: RCK, Android, Wipe Data). But if you see the adb interface in Device Manager while it is looping you should have an adb connection and
Code:
adb devices
should return a similar but different string of numbers and letters.
Code:
adb reboot-bootloader
should boot you into the bootloader which is also fastboot mode.
In fastboot you should be able to flash TWRP with the command you posted, minus the typos naturally.
It has to be
Code:
fastboot devices
and it has to return the string of letters and numbers, then:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Try that and report back

Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
C:\>fastboot devices
015d2bbcc413ea10 fastboot
C:\>cd adb
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:49 PM <DIR> .
04/29/2014 11:49 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 openrecovery-twrp-2.7.0.0-tf700t.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,153,600 bytes free
C:\adb>ren openrecovery-twrp-2.7.0.0-tf700t.blob twrp.blob
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:50 PM <DIR> .
04/29/2014 11:50 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 twrp.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,088,064 bytes free
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
OKAY [ 2.459s]
writing 'recovery'...
OKAY [ 7.564s]
finished. total time: 10.023s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.022s
Click to expand...
Click to collapse
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?

BigKenW said:
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
Click to expand...
Click to collapse
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck

berndblb said:
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
Click to expand...
Click to collapse
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
Click to expand...
Click to collapse
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.

I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys

BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
Click to expand...
Click to collapse
To return to stock just download the Asus firmware, unzip it once and flash the resulting zip in recovery.
Your bootloader will stay unlocked. You just have to flash a custom recovery again, reboot and then flash the rom.

allotesting said:
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
Click to expand...
Click to collapse
Hi all
Back from work but all the commands were uselee
In device manager I have ASUS android ADB interface after updating manually the 'transformer' that I had with the yellow matk
When trying adb devices it comes with 0123456789ABCDEF all the hexadecimal digits so seems to me that the machine does not recognize the tablet itself
When trying fastboot devices and hit enter it comes back to the >invite
When trying adb reboot-bootloader it just sits there with even no >invite
Forgot to mention that the word recovery comes after the 0123456789ABCDEF on the adb devices
Anything else to try? Thanks

TWRP screen unresponsive

For some reason my phone wouldn't accept the OTA update to 44S, but I was happy with 38R so stuck with that.
Now I see lollipop is coming, and (as I read it) some of the updates in 44S and the latest update contain updates which are required for lollipop, so I decided to upgrade by flashing it.
Stupid decision to do before my morning coffees, but there you go.
I downloaded the unofficial XNPH44S rom with a plan to install via TWRP.
Here is where I made rookie mistake number one; I wiped the phone before I adb pushed the rom zip across.
A little googling, and I discovered adb sideload so I think all is not lost.
Sideloading the rom seemed to work, so I rebooted back into TWRP (v2.8.1.0) to install the rom, and now my screen is unresponsive. I can't press any of the options, and pressing the volume or power buttons just brings up the swipe to unlock, which of course does nothing because the screen won't respond.
I can't go back to fastboot and install the rom that way (which, with hindsight, I realise was probably my best option in the first place) because I have no OS installed, and I can't do anything with TWRP because the buttons don't work.
Any suggestions, or am I screwed?

When it's connected via adb isn't there a command to reboot into boot loader? Adb reboot-bootloader or something? Google around.
Or turn it off and press vol up + power I think that takes you to bootloader mode. Check the noob guides for commands and steps I can't remember off hand what they are
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
It's weird that twrp is unresponsive though...

ek69 said:
When it's connected via adb isn't there a command to reboot into boot loader? Adb reboot-bootloader or something? Google around.
Or turn it off and press vol up + power I think that takes you to bootloader mode. Check the noob guides for commands and steps I can't remember off hand what they are
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
It's weird that twrp is unresponsive though...
Click to expand...
Click to collapse
I was being a noob and thinking that because 'adb devices' was showing none that fastboot wouldn't work.
Went back to 38R, installed 44S OTA (which made my phone bootloop as it has every other time I tried to install it) then did an adb sideload of the 44s to 05Q update.
Phone fixed, and up to date - now I just have to reinstall everything and remember passwords.

Bricked my AL10, halp [Solved]

I had TWRP and and 1xx KangVip installed.
I wanted to flash an 1xx, then 321 stock rom in order to update to a newer KangVip, but neither fastboot nor adb sideload was working.
I stupidly blindly followed step by step instructions from a random internet user and the first step was to wipe everything.
When rebooting into the bootloader, it would say "connect to the computer and start HiSuite"
When running adb sideload update.zip i got "cannot read update.zip".
I checked everything but couldn't find the problem so I tried pushing the file but when trying to install it with TWRP it failed.
The next thing I did bricked my phone completely, I ran fastboot flash recovery RECOVERY.img while in the fastboot menu where it displayed "connect your phone to the computer and start HiSuite"
That removed TWRP and now when I boot into recovery I get a loading circle that goes to 5% and then stops.
In the circle is a USB logo with an arrow and under the circle are chinese characters commenting the progress.
Is there anything I can do to save my phone?
Edit: Sorry this always happens to me, I tried fixing this for 5 hours and 5 minutes after I post this the problem fixes itself...
I just tried fastboot flash again and now it works.

OK you're saying you can still flash files while it's on "Connect to the computer and start HiSuite" Yes?
If so you should be able to reflash Cust.img, boot. img, system.img and recovery.img form a
1xx Update.app file. Use Huawei Firmware Extractor to get these files.
---------- Post added at 11:07 PM ---------- Previous post was at 10:56 PM ----------
That's good to hear

Phone issues after unlocking bootloader?

So I recently unlocked the bootloader on my Honor 6x and it is now stuck on the screen saying "Your device has been unlocked and can't be trusted" and the pesky "Your device is booting now message....". I am unable to get into fastboot mode, and so far no chances of booting into eRecovery. Any known fixes?

Do a clean flash of your ROM through dload method

in same situation.. any help pleasee ?
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
but i have access to fastboot..

This also happened to me. I cant get to fastboot and the phone was stuck on "You're device is booting now...".
What I did is I let the phone drain its battery. After draining the battery, I tried to access fastboot mode. Holding down volume button and connecting the USB cable, the phone booted into the erecovery mode instead of fastboot mode. So I did a data wipe. After performing wipes, I tried to boot into fastboot mode again, and it worked. So I flashed the recovery, ramdisk, and kernel images. After which, I flashed the system again in TWRP and it was successful. ? Now my phone boots normally. ?

i have the same problem. i cant boot in fastboot or recovery...

player615 said:
i have the same problem. i cant boot in fastboot or recovery...
Click to expand...
Click to collapse
Try Dload or let it drain of battery. Next plug-in USB when it turns on hold Volume Up and boot into eRecovery.

No OS Installed!!! Help Please!

I tried to get magisk to work after installing the latest OTA and I did something wrong and had to wipe all the data from the Oneplus recovery menu. Towards the end in TWRP while wiping, I wiped off the OS by mistake. After clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging. I do not have twrp and my device is not being detected by my pc in powershell for me to adb push the whole os and twrp and flash them. I am literally freaking my skin off at this moment. Please help me. If I didnt mention any important detail please ask, Im super frightened so I might have missed something.
tl dr: No OS, no TWRP and locked in fastboot. (thanks to null0seven)

prathk said:
I tried to get magisk to work after installing the latest OTA and I did something wrong and had to wipe all the data from the Oneplus recovery menu. Towards the end in TWRP while wiping, I wiped off the OS by mistake. After clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging. I do not have twrp and my device is not being detected by my pc in powershell for me to adb push the whole os and twrp and flash them. I am literally freaking my skin off at this moment. Please help me. If I didnt mention any important detail please ask, Im super frightened so I might have missed something.
Click to expand...
Click to collapse
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.

jcsww said:
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
Click to expand...
Click to collapse
I am not able to use TWRP. In the fastboot menu when I enter the 'Go to Recovery' option it just reboots back to the fastboot menu.
I'm relatively a noob in all this so if there's any other way please mention it.
UPDATE: I am currently downloading the stuffs required for the MSM tool, the download is extremely slow. Will check back once the download is done and I tried it. Thanks for atleast giving me some hope in the time being.

jcsww said:
You should be able to use TWRP to reflash the OS. Personally, I would put the device in EDL mode and use the MSM Tool to put the device back to factory stock. Once back to stock, you can get your OTA and then reflash TWRP and root your device once again.
Click to expand...
Click to collapse
While in the MSM tool after clicking 'Start', I got a 'Sahara Communication Failed' error. What do I do now?
UPDATE: Another problem right now is that after holding the volume up and down buttons simultaneously for a few seconds and inserting the cable to enter EDL mode (it shows as Qualcomm HS-USB QDLoader 9008 in device manager), within a few seconds the phone reboots into the fastboot again.

Sahara error it's not a real error. After that MSM does not finish installing OS?
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Choose the one you need. For example i need GM31BA (european version)

null0seven said:
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
This.
---------- Post added at 02:02 PM ---------- Previous post was at 02:00 PM ----------
prathk said:
IAfter clicking reboot, it just rebooted to the fastboot menu and when I click 'Go to recovery' on the fastboot menu it just boots back to the fastboot menu. My device is not being detected in powershell when I type in adb devices and it might be because after the first wipe that happened I didnt turn on adb debugging.
Click to expand...
Click to collapse
adb won't work in fastboot, by definition (only works in OS and TWRP). Fastboot mode is for fastboot (and fastboot does not need debugging to be on). And fastboot is what you want, to flash the stock ROM.

null0seven said:
Sahara error it's not a real error. After that MSM does not finish installing OS?
But first try FastBoot rom :
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Choose the one you need. For example i need GM31BA (european version)
Click to expand...
Click to collapse
No, its written waiting for communication with device and the app stops responding. I would attach a screenshot of the error but I myself am not able to try this method again (Check the update in my previous post).
UPDATE: I'm currently downloading the fastboot ROM. Hope it works.

He, prathk,
write that it's locked on Fastboot. NO twrp, no OS. That's why i suggest Fastboot rom, before MSM tool.
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
(it shows as Qualcomm HS-USB QDLoader 9008 in device manager),
this is GOOD. youre phone drivers are corect. Remove the cable from phone.
Do this :
With phone off hold both volume buttons only and plug cable into computer .
Or power off the phone. Press vol. UP, 5to 10 seconds, plug the cable.
Youre problem with MSM tool it's that the phone it's not shut OFF !

null0seven said:
He, prathk,
write that it's locked on Fastboot. NO twrp, no OS. That's why i suggest Fastboot rom, before MSM tool.
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
(it shows as Qualcomm HS-USB QDLoader 9008 in device manager),
this is GOOD. youre phone drivers are corect. Remove the cable from phone.
Do this :
With phone off hold both volume buttons only and plug cable into computer .
Or power off the phone. Press vol. UP, 5to 10 seconds, plug the cable.
Youre problem with MSM tool it's that the phone it's not shut OFF !
Click to expand...
Click to collapse
Thanks for the suggestion in your previous post, I added it.
I tried both the methods and both resulted in 'Sahara Communication Failed'.
And now even on trying both the methods it keeps restarting to the fastboot menu.

If the phone it's not off MSM not working.
Alternatively you can force your OnePlus 7 Pro to boot to EDL mode by the following steps:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.

As advised before, you need to download the fastboot package made by @mauronofrio
Run the "flash-all-partitions.bat" while in fastboot.
You seemed mebbe confused before, adb and fastboot are different, adb is only to be used either within the rom or while in recovery. Fastboot is to be used while you're in Fastboot mode. It will still let you flash multiple partitions, hence why the fastboot fix should work.
For future reference, the best way to wipe data while leaving the rom intact is "fastboot -w", that will also remove encryption. (The flash-all-partitions batch file will do this too)
As long as you get a result after typing "fastboot devices" then you should be ok.

I flashed the Fastboot ROM as many of you suggested and it worked. Thanks to everyone who helped out and also thanks for correcting my knowledge. I just want to know if I'll still be getting OTA updates as usual or should I manually download it and flash it from now onwards.

prathk said:
I flashed the Fastboot ROM as many of you suggested and it worked. Thanks to everyone who helped out and also thanks for correcting my knowledge. I just want to know if I'll still be getting OTA updates as usual or should I manually download it and flash it from now onwards.
Click to expand...
Click to collapse
If you've flashed the default partitions you should get OTA, if you flash TWRP and root then you'll download the entire new rom, you don't get an OTA option.