Related
(had rooted phone running cm12 nightly earlier) So i downloaded the oxygenos file yesterday, forgot to extract and directly went to TWRP, clicked wipe (ticked everything EXCEPT internal memory) then went to the .zip file of oxygenos and attempted to flash, Obviously that failed and as a result i had no OS. Did a fastboot thing and flashed cm12 back on (already had file on phone) then extracted oxygenos, went to TWRP and wiped all except internal then flashed and successfully rebooted.
Then, I even had to flash SuperSU for root again, a new version since the one on my phone was old i guess
Here's the thing now. I have all my apps up and running, but i cant find ANY of my photos, videos or music. At no point did i forget to untick internal memory.
WHAT CAN I DO??
(kinda Newb to this whole flashing and rooting thing, apologies)
Bridge Ric said:
(had rooted phone running cm12 nightly earlier) So i downloaded the oxygenos file yesterday, forgot to extract and directly went to TWRP, clicked wipe (ticked everything EXCEPT internal memory) then went to the .zip file of oxygenos and attempted to flash, Obviously that failed and as a result i had no OS. Did a fastboot thing and flashed cm12 back on (already had file on phone) then extracted oxygenos, went to TWRP and wiped all except internal then flashed and successfully rebooted.
Then, I even had to flash SuperSU for root again, a new version since the one on my phone was old i guess
Here's the thing now. I have all my apps up and running, but i cant find ANY of my photos, videos or music. At no point did i forget to untick internal memory.
WHAT CAN I DO??
(kinda Newb to this whole flashing and rooting thing, apologies)
Click to expand...
Click to collapse
If it's gone it's gone. Forget about it.
Bridge Ric said:
(had rooted phone running cm12 nightly earlier) So i downloaded the oxygenos file yesterday, forgot to extract and directly went to TWRP, clicked wipe (ticked everything EXCEPT internal memory) then went to the .zip file of oxygenos and attempted to flash, Obviously that failed and as a result i had no OS. Did a fastboot thing and flashed cm12 back on (already had file on phone) then extracted oxygenos, went to TWRP and wiped all except internal then flashed and successfully rebooted.
Then, I even had to flash SuperSU for root again, a new version since the one on my phone was old i guess
Here's the thing now. I have all my apps up and running, but i cant find ANY of my photos, videos or music. At no point did i forget to untick internal memory.
WHAT CAN I DO??
(kinda Newb to this whole flashing and rooting thing, apologies)
Click to expand...
Click to collapse
Try mounting it to a PC and seeing if you can locate them
Sent from my A0001 using XDA Free mobile app
abhi08638 said:
Try mounting it to a PC and seeing if you can locate them
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
How do I mount?
Bridge Ric said:
How do I mount?
Click to expand...
Click to collapse
Plug your phone into the computer with a USB cable
Sent from my A0001 using XDA Free mobile app
abhi08638 said:
Plug your phone into the computer with a USB cable
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I did that of course Didn't work couldn't see anything on there I realised I had accidently unlocked boot loader AGAIN thus wiping internal stuff.
Bridge Ric said:
I did that of course Didn't work couldn't see anything on there I realised I had accidently unlocked boot loader AGAIN thus wiping internal stuff.
Click to expand...
Click to collapse
LOL!! What were you thinking while typing commands in fastboot mode?
Bridge Ric said:
I did that of course [emoji14] Didn't work couldn't see anything on there I realised I had accidently unlocked boot loader AGAIN thus wiping internal stuff.
Click to expand...
Click to collapse
How do you accidentally unlock your bootloader? Your data is gone.
Transmitted via Bacon
timmaaa said:
How do you accidentally unlock your bootloader? Your data is gone.
Transmitted via Bacon
Click to expand...
Click to collapse
I dont know if that did happen someone on OPO forums told me that it did, all i did after flashing oxygenos was flash supersu root file again and after that i noticed i have no access to writing on internal memory and i even tried what this guy on OPO forums said forums.oneplus.net/threads/need-help-urgently-no-write-access-to-sd-card-i-think.150503/page-2 and now after doing that i rebooted all i see is an O going round and round on my screen.
Im DONE with this crap OS how do i just reflash CM12 when my phone doesnt switch on but TWRP does?
Bridge Ric said:
I dont know if that did happen someone on OPO forums told me that it did, all i did after flashing oxygenos was flash supersu root file again and after that i noticed i have no access to writing on internal memory and i even tried what this guy on OPO forums said forums.oneplus.net/threads/need-help-urgently-no-write-access-to-sd-card-i-think.150503/page-2 and now after doing that i rebooted all i see is an O going round and round on my screen.
Im DONE with this crap OS how do i just reflash CM12 when my phone doesnt switch on but TWRP does?
Click to expand...
Click to collapse
It isn't the OS at fault, many people have flashed it without a single issue, sorry, but it's user error. Start from scratch by flashing the stock images, I have instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
It isn't the OS at fault, many people have flashed it without a single issue, sorry, but it's user error. Start from scratch by flashing the stock images, I have instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You're sure i should start with section 8? Sorry, "Once bitten, twice shy"
Bridge Ric said:
You're sure i should start with section 8? Sorry, "Once bitten, twice shy"
Click to expand...
Click to collapse
Yes, that's all you need to do (as long as your bootloader is actually unlocked). It will reinstall CM11S and format your userdata so you can access it again.
Transmitted via Bacon
Well, I've gotten myself into quite a pickle. Root was finally gained for the T-Mobile D6616 model over the weekend. The method works great and I had no trouble with it at all. I then installed Nut's Dual Recovery without any issue. Rebooted into TWRP multiple times over the next day or so and took a backup.
Next, I installed Xposed and started loading up all the modules I have missed since I got this phone. Everything was working great until.... I decided to edit the build.prop in order to silence the camera shutter sound. It's a pretty simple edit; I've done it a dozen times before:
Code:
ro.camera.sound.forced=0
For some reason that didn't look right to me. I thought I remembered the line being slightly different. But whatever, I threw it in there, saved it, and rebooted.
And now I'm stuck in a boot loop.
Even that is not usually a problem. My plan was to boot into TWRP, replace build.prop with the backup, reboot and be on my merry way. But.. Now my custom recovery seems to be gone. No idea why. When I boot into recovery, it seems to be stock and gives only the options: 1) continue powering up, 2) safe mode, 3) factory reset, 4) power off.
1) Powering up obviously doesn't work.
2) Safe mode doesn't work - boot loop continues
3) Tried factory reset. The little Android dude showed up, a progress bar worked on restoring to factory, and then.. still boot loop continues.
I have successfully gotten the phone to show up in adb ONCE since the boot loop appeared. I have no idea how I did it, and I haven't been able to replicate it. My plan was try to pull and edit the build.prop from adb if I can get it to show up again. But no joy so far.
Bootloader is still locked on this device, so no fastboot options.
So now I'm really at a loss for what to try next. Any ideas?
Reflash with stock rom.
electrash said:
Reflash with stock rom.
Click to expand...
Click to collapse
Yes, but... How do I do this with no custom recovery and no access to fastboot?
SportingChap said:
Yes, but... How do I do this with no custom recovery and no access to fastboot?
Click to expand...
Click to collapse
Use flashtool and a stock FTF
gregbradley said:
Use flashtool and a stock FTF
Click to expand...
Click to collapse
D6616 is not listed as being supported.
This flash tool can only be used by Xperia™ devices having an unlocked boot loader
Click to expand...
Click to collapse
Again... D6616 bootloader is not unlocked.
SportingChap said:
D6616 is not listed as being supported.
Click to expand...
Click to collapse
All xperia devices are supported by flashtool
You are talking about Sony's flashtool that only works with unlocked bootloaders
I am talking about the original flashtool developed here on XDA
Check flashtool.net
gregbradley said:
All xperia devices are supported by flashtool
You are talking about Sony's flashtool that only works with unlocked bootloaders
I am talking about the original flashtool developed here on XDA
Check flashtool.net
Click to expand...
Click to collapse
I see now. Looking into it, thanks.
I wish I could thank you more than once, gregbradley! Everything flashed and restored back to the way it was - except I lost internal storage. Bummer. Oh, well. Life goes on.
For anyone else who stumbles across this thread:
Use this thread to download the stock .ftf file for your particular Z3
Use the instructions here to download, install, and use Flashtool
Use these instructions to root (or re-root) and install TWRP recovery if you have the T-Mobile variant (D6616) Note: The link to recovery in that post is broken. You can find the latest version here: http://nut.xperia-files.com/ -- click on XZDualRecovery
If the root instructions seem to work but you don't see SuperSU after reboot, delete the contents of data/local/tmp and try again:
Code:
adb shell rm -R /data/local/tmp/*
So it' s not exactly the way it was.
SportingChap said:
except I lost internal storage. Bummer. Oh, well. Life goes on.
Click to expand...
Click to collapse
That's a learning curve, always make a backup of everything you want to keep, or keep it on the external SD card.
But glad to hear you are back up and running.
gregbradley said:
That's a learning curve, always make a backup of everything you want to keep, or keep it on the external SD card.
But glad to hear you are back up and running.
Click to expand...
Click to collapse
Yeah, didn't anticipate this one. When I took the nandroid backup in TWRP, it didn't click that there was no "internal storage" option to back up - only system, data, trim area, boot, and cache. Must be different on other devices, because I know I've backed up internal storage in the past.
A lot, if not most, of what I had on internal storage is backed up on my desktop in various folders. So I'm not at a total loss.
And.. I hear you on using external. I always did use it for most things prior to getting this Z3. I have a 64gb sdcard and use it for nandroid and TB backups (and mp3s). I had to make the decision to go along with KitKat's insistence on using internal with no external write access for apps. Now that I have root, I patched it via FolderMount and might redo my symlinks for the Pictures folder, etc. We'll see.
Sigh.. Isn't Android fun?
it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.
After i wanted to install Android P, i got a bootloop. so i wanted to go to twrp but now my files are encrypted and twrp is not asking for a pin or pattern so i can't decrypt my internal storage files.
Now the biggest problem is that i just came back from a family weekend and i made a lot of pictures, witch i can't acces now, and i really want them back.
Now i can't install a new os or anything ...
Can someone please help me! i'm really despirate
(sorry for my bad english)
Try downgrading twrp , night get it to ask for pin
downgrading is never the answer. In fact, that will cause this problem to happen. Now i must ask, are you temp booting twrp or is twrp installed to phone.
I got this when I temp booted the mtp enabled twrp the other day, although it still asked for my passcode and said description was successful. When I rebooted the installed (official) twrp it all came back....
MrSteelX said:
downgrading is never the answer. In fact, that will cause this problem to happen. Now i must ask, are you temp booting twrp or is twrp installed to phone.
Click to expand...
Click to collapse
Now i am booting from temp twrp, before that i got the latest twrp installed
Bringing this back up... Did booting from temp twrp work? Ran into the same issue.
Temp boot and use the usb c to pull ur data from the device to a computer. After that you can wipe and start over. Unbricking guide available in the help section
Having the same issue. If I boot using fastboot TWRP I'm able to decrypt data. I did that and flashed stock OOS and the same TWRP version (BluSpark) that was used in the fastboot. But the folders are still encrypted. It's weird how a fastboot can decrypt it but a regular recovery boot can't. Is there any alternatives available?
I'm in the process of backing up my data before I officially bite the bullet.
spartan268 said:
Having the same issue. If I boot using fastboot TWRP I'm able to decrypt data. I did that and flashed stock OOS and the same TWRP version (BluSpark) that was used in the fastboot. But the folders are still encrypted. It's weird how a fastboot can decrypt it but a regular recovery boot can't. Is there any alternatives available?
I'm in the process of backing up my data before I officially bite the bullet.
Click to expand...
Click to collapse
Only way i know to get rid of this by removing the encryption on the data is to Format the Internal Storage !
Totone56 said:
Only way i know to get rid of this by removing the encryption on the data is to Format the Internal Storage !
Click to expand...
Click to collapse
That's what I did in the end. I just backed up my media through fastboot TWRP beforehand. Beats having to use the download tool at least
spartan268 said:
That's what I did in the end. I just backed up my media through fastboot TWRP beforehand. Beats having to use the download tool at least
Click to expand...
Click to collapse
Probably the best way indeed. I think i'm gonna start disabling forced encryption to stop these kind of problems.
Totone56 said:
Probably the best way indeed. I think i'm gonna start disabling forced encryption to stop these kind of problems.
Click to expand...
Click to collapse
How to do it? I tried with zero luck
starche_old said:
How to do it? I tried with zero luck
Click to expand...
Click to collapse
I haven't tried yet, don't know for now !
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.