Can't reinstall twrp after accidently updating CM13 to CM14. - OnePlus 3 Questions & Answers

I've been running cm13 nightlies on my OP3. I haven't updated in a couple weeks and last night i got a notification that there was some new updates. Since it's been a while i decided to do the update so i let the cmupdater do it's thing and went to bed. This morning i wake up and was greeted with a very cranky phone. I noticed i was having trouble with any google related app, and also popups of google apps crashing. So i go to settings and I see that my phone has been updated to CM14!
well that would explain the Google apps pproblem. I was going to flash gapps for 7.0 but i couldn't get into recovery. I had twrp installed but now i couldn't get into it. the phone reboots, shows the oneplus logo then shuts off. Then i decide to reflash twrp. i put the phone into fastboot mode and from my pc command prompt, tried the fastboot flash recovery. img. it says it was successful but i still can not boot into recovery. I made sure debugging was on and I also accepted my pc key when asked on the phone before booting into fastboot mode. I realise this is a dirty flash but is there anyway of recovering from this ? i usually flash the nightlies myself from the recovery,i don't know why last night i used the cmupdater.

You probably got it going by now but in case. Which version of twrp are you trying? I would try the latest twrp-3.0.2-23-oneplus3.img. Make sure OEM unlock is checked in device manager, root is allowed as well, try an app like flashify or something that can flash an image from within the OS and see if you have better luck.

Ducter said:
You probably got it going by now but in case. Which version of twrp are you trying? I would try the latest twrp-3.0.2-23-oneplus3.img. Make sure OEM unlock is checked in device manager, root is allowed as well, try an app like flashify or something that can flash an image from within the OS and see if you have better luck.
Click to expand...
Click to collapse
Thank you for your help. I couldn't try the flashify route as it would not install. Something about parsing the package failed. I did manage to fix it by downloading the latest twrp you suggested and flashing that. After that I was able to boot into recovery and flash pico gapps 7.1. Unfortunately that wiped out all of my apps but at least i didn't lose any of my files. Thanks again.

pdrift said:
Thank you for your help. I couldn't try the flashify route as it would not install. Something about parsing the package failed. I did manage to fix it by downloading the latest twrp you suggested and flashing that. After that I was able to boot into recovery and flash pico gapps 7.1. Unfortunately that wiped out all of my apps but at least i didn't lose any of my files. Thanks again.
Click to expand...
Click to collapse
Glad you got it going, I see now that I mentioned device manager... No clue where that came from lol, was suppose to be developer options. Regardless, you got it and that was the goal.

Related

Problems post super su install

So I installed TWRP and then moved on to install super su which is where the problem started. First I attempted to install SR1-SuperSU-v2.78-SR1-20160915123031.zip. Everything ran but after it led to a boot loop. After that I realized I had tried to install the latest file but not the latest STABLE file, so I then tried to install UPDATE-SuperSU-v2.78-20160905010000.zip to no avail. I then noticed when I go in to download mode i get a "FILE /mnt/media_rw/ext_sd/OPJAIMG.zip File Not FOUND" error on the bottom. Any idea how i could sort this out? (like a fool I did not make a backup before doing this) I downloaded the RUU (RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.17) but I wanted some advice before i do that so i don't mess it up more.
ATT m9
os 3.38.502.21
s-on
TWRP 3.0.2-0
Download Mode checks for this file to update the Firmware. If you are not planning on updating that, you don't need that file on your Phone. It's more a notice that an actuall error
Alright, that's encouraging. Any idea why i would get a boot loop after trying to install super su though? That's where I'm stuck right now. I'm not opposed to going back to stock and starting over if that's the only option. I just want my phone to be usable again.
Well if it installed in Systemless mode, it can cause a bootloop for a while, you might just need to be patient. Otherwise, i would maybe try an older version of SuperSu. I think 2.76 was pretty safe to install
I let it boot loop over night so no dice there. I'll give the older version a try. Hopefully that works.
No luck with 2.76. It boot looped for a half hour. Any other thoughts?
erics87 said:
No luck with 2.76. It boot looped for a half hour. Any other thoughts?
Click to expand...
Click to collapse
Yes, don't flash any newer version than 2.65. Updating via the play store afterwards is safe, though.
Sent from my HTC One S using XDA Labs
I had the exact problem, lucky enough i could fetch some log files during boot and sent them to chainfire, maybe we will see a fix someday
SuperSU 2.65 seems to be the latest version working in system-less mode on the HTC One M9, updating through Google Play Store works fine tho.
I will look for the log in a couple minutes and post it here for all that are interested
But don't worry, atleast it didn't brick our phone

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

OnePlus 3 keeps booting into TWRP Recovery Mode - PLEASE HELP!!

I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
SOLVED : I flashed TWRP 3.0.3 once again and somehow it got fixed
'' doing a wipe help you bypass the password''... Well yes probably, but depending on what type of wipe, you might have wiped your rom/system. So if that is the case, there is no rom to boot into, and your stuck in twrp recovery. Restoring an empty Nandroid wont do anything either. So my guess is you will have to download stock or custom rom and do a fresh install.
If needed, this method works very well.
I used it to day, with success.
Good luck !
Thank you. but will this work with latest TWRP 3.0.3 or will i have to use old one as mentioned in that post?
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
rshah0429 said:
I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
Click to expand...
Click to collapse
Had the same problem and panicked like hell. I just switched a few twrp recoveries (modded and official) and found one that worked and phone booted.
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
thank you. i will try this
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
I can't find TWRP 3.0.4.0 Can you please link it?
rshah0429 said:
I can't find TWRP 3.0.4.0 Can you please link it?
Click to expand...
Click to collapse
See Here
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img
Its not official but working for me...
Try flashing the stock recovery. I got stuck in recovery loop after the OTA update got installed over twrp. Flashed the stock recovery and right away it booted me to the rom.
It's a problem of older twrp with nougat so you need to flash twrp new version

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

Updates fail to install

I have a Sprint Moto Z2F, BL unlocked, rooted running the stock ROM
I've tried to return back to stock, recovery and not rooted but bootloader is still unlocked and tried to take the update but it always fails to install. What am I doing wrong?
hello....Bueller, .Bueller
Well reading other threads, if you unlock your bootloader and root, then go back to stock you can't get OTA updates
TwoBuells said:
Well reading other threads, if you unlock your bootloader and root, then go back to stock you can't get OTA updates
Click to expand...
Click to collapse
From another post I read from @Uzephi just recently there are some users who have been able to return to stock and receive the updates but IIRC there is a certain procedure to follow for it to work. Search @Uzephi's post and you'll be able to find it.
Sent from my Moto Z2 Force using XDA Labs
To add to what @fast69mopar said, here is the thread you should check out.
thanks
Yes, follow that thread. I have never had an issue getting updates on my sprint variant.
Uzephi said:
Yes, follow that thread. I have never had an issue getting updates on my sprint variant.
Click to expand...
Click to collapse
I've tried three times, I'm not wiping or formatting data, mounting the right way or order, when I get some time I'll try again. phone is running fine now, I just have updates frozen now so the notifications don't bug me.
Flashall works great,
I fastboot boot the TWRP.img file
then boot into TWRP, flash the TWRP zip and Magisk zip files.
I get a " can't mount system error", I'm not sure what to have checked when I wipe after installing TWRP
I tried to install the TWRP 3.2.2.0 but could never get the phone to boot after installing twrp zip
TWRP 3.2.1.0 is the only TWRP I can get to install and boot.
I have something overwriiten or not installed correctly \
I have to do some more reading of these threads and see where I'm doing wrong.
this slot a and b is confusing, maybe I did something wrong there. ( I really have not done anything with slot a or b, just installed files like those slots are not there. maybe one of them is corrupt
I tried a few more times but still can't get the OTA update to install.
I put my phone in the fastboot mode
I run Flashall
Flashall does its thing then when I reboot I sign in to my Google account, the phone is activated to my carrier. I get a notification for the system update, then it fails.
I go back to fastboot, flash and setup TWRP then root and restore my data and I'm back to normal
after Flashall my phone is back to stock, I tried to let the OTA update install and it fails everytime.
Maybe I should try some different ROM's since its so easy to get back to stock if something goes wrong.

Categories

Resources