So after years of never needing to create an account.....I am stuck. Hoping yall can help me out.
I HAD lineage OS installed and everything was working fine. I wanted to revert back to stock so that I could get the google photos unlimited upload back.
I HAD lineage recovery installed but now I am soft-bricked and cant get into recovery.
My bootloader is unlocked and fastboot is working.
When recovery was working, I tried to install the full OTA and that failed so that lead me to the Full Factory Image.
I try to run the flash-all.sh script and it does all sorts of failing. (See flashAllLog.txt) I believe the crux of this is:
When I installed LineageOS, my phone started identifying as a Pixel 3 which was strange but whatever. When I am trying to run this flash-all basically it says that my bootloader is newer and it needs an older version.
So then I thought well maybe I need to erase the slots (eraseLog.txt). Those all worked fine but I still couldnt flash all
So then I was thinking maybe if I just flash the bootloader manually (manualBootFlashLog.txt). But that failed as well.
Am I just boned here or is there an android wizard out there who can point me in the right direction. Please let me know of ANY other information I could possibly provide
Here are 4 options, there's more even tedious stuff you could try but Id start with these
1.) Have you tried to just use fastboot to BOOT into the recovery.img file from the factory image zip (not flash it) and then you can sideload the OTA from there?
2.) You can also try to edit the flash-all file so it doesn't re-flash the bootloader. Just flash system, data partitions etc.
3.) Try another factory image. I assume you tried to flash the latest Android 10 full factory image, maybe try an older one? Maybe even Android 8 or 9 and the just take the OTA update in settings.
4.) Also can try to boot (not flash) lineageos recovery to see if you can at least flash back into LineageOS (or maybe a different custom ROM, PixelExperience for example enables the unlimited Google Drive storage) to get a working device again.
Related
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Try the flash all script again with latest firmware and let it boot up completely. It will take a while, once booted, flash TWRP and root if you want.
ntropia said:
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Click to expand...
Click to collapse
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That's an interesting perspective, actually.
I didn't know that you needed a special image for rooted devices.
Although, I would imagine that's always possible to 'un-root' it, and honestly I was hoping that 'fastboot flash -w...' would have removed any trace of the root.
Is that the case?
Either way, where could I find these modified images?
Thanks a bunch!
Solved
I found the solution which, as it happens when nothing seems to be wrong, was fairly trivial.
Basically, the scripts provided with the stock ROM from Google has problems, and this last command fails:
Code:
fastboot update image-bullhead-mmb29p.zip
saying that system.img is missing.
To fix that, you have to manually extract the content of the files and proceed to flash manually userdata, system, etc...
The problem is that if you don't flash also vendor.img, you're in trouble, and the device will not boot.
Some of the guides that I've found were suggesting that you need to do it for the Nexus 9, and I didn't notice when other guides were mentioning it.
Once you flash the vendor.img, the boot loop is gone.
I'll put it here, I hope it can be helpful to somebody.
Thanks to androidddaaron and k.s.deviate for the support!
(I've thanked also used the thank button near the posts, but if there's more to do, let me know)
Now, back to mess up the Project Fi SIM...
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
I had trouble with OB10 and adb. Said it couldn't read the file. I instead flashed TWRP and enabled mtp from there. I then pushed the full ROM to internal storage. Fastboot flashed the stock recovery and used 'upgrade from internal'. That flashed it fine. Then I reinstalled TWRP and SuperSU.
yasinmys said:
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
Click to expand...
Click to collapse
Have you downloaded the full ROM? Make sure you download the full rom from oneplus's website or any of the mirrors available on various forums on xda. Flash it normally like you flash a custom rom. It will work as I have done it a lot of times. Your file must have been corrupt.
yasinmys said:
I was trying to clean install Oxygen OS 4.0 onto my OnePlus 3. I did a huge mistake of formatting my entire data off of my OnePlus 3 using Wipe > Format Data > Yes in TWRP and now I cannot use my phone.
I don't know how to install the OS on the phone again and I am stuck. I don't even have a spare phone right now.
Can someone please help me? I tried checking the other forums, but they were confusing and I didn't understand anything. Please help me.
I tried downloading the software from OnePlus's website, but I couldn't install it through ADB cause the file is for some odd reason corrupt.
Please, somebody help me. I can't even send it back to OnePlus cause I am in a different country ATM.
Click to expand...
Click to collapse
Go to: h*t*t*p*://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/ (REMOVE STARS) download both stock recovery and rom of OOS v3.2.8 (located at the bottom of the page). Flash stock recovery via fastboot (I hope you know how to). After it was flashed, disconnect the cable, turn off the device in fastboot (power off). Then hold power and volume down keys down to boot into recovery. From there ADB sideload the stock OOS v3.2.8. Let it boot up and update to OOS 4.0 via OTA.
P.s. If you need the actual steps, let me know. I'll update it in this post.
nine5raptor said:
I had trouble with OB10 and adb. Said it couldn't read the file. I instead flashed TWRP and enabled mtp from there. I then pushed the full ROM to internal storage. Fastboot flashed the stock recovery and used 'upgrade from internal'. That flashed it fine. Then I reinstalled TWRP and SuperSU.
Click to expand...
Click to collapse
I had an issue with custom twrp + Freedom OS v2.0 (OOS v4.0). No xposed, a lot of battery issues with performance and toggling settings issues too. So I decided to stick with Freedom OS 1.7 (OOS v3.2.8) until OnePlus fixes the issues, with xposed available for Nougat and official twrp being released to support Nougat. Also, whenever I flashed custom twrp, which was recommended by the dev, it always asked me for a password. I did have PIN code with fingerprint option, a pattern option or none at all. All of which did not help bypass it, even using "default_password". I was stuck with OOS v4.0, somehow, with no twrp to work with as it locked my data. I backed my files before flashing from OOS v3.2.8 to OOS v4.0, lucky me. I managed to do what I have explained in the first response.
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
If your wanting to flash a factory image, you'll need a few things first.
I would highly recommend that you look over the linked thread carefully. It has many links and tips to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
https://developers.google.com/android/images
Make sure you have the latest adb and fastboot. Get them from Google...
Go get the latest image and Unzip it. Do not Unzip the folder inside. Move everything you just unzipped into the folder with adb and fastboot.
Now, if you've unlocked and unlocked critical, great. If you haven't unlocked critical, you'll have to. The system image won't install if the bootloader is out of date. Sadly, this will wipe your data.
If both are already unlocked, then open the flash-all file with a text editor and remove the,"-w" and the space preceding, then save the file. Removing the -w will keep your data. Run the flash-all.bat file and in about 10 minutes everything will be flashed.
back to stock
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls
lomski said:
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls
Click to expand...
Click to collapse
First thing!! Forget fast!! You need to fastboot flash a full factory image with the -w still in the script. Maybe even do it twice. Then go in and do a factory reset from the OS for good measure. Once that is done and you know it reboots you can go through the locking command. I would NOT toggle the OEM switch in dev though.
Sent from my Pixel 2 XL using XDA Labs
So this has been a a very frustrating experiance but I think I've got everything working again. I don't know how many times I've flashed different factory images and then tried to install TWRP and then install a new custom rom. So I want to explain all of the steps I took (if I remember them all).
0. I couldn't boot into my system but had TWRP installed. At this point I should have tried to get all my data from the sd card via "adb pull /sdcard" .
1. I didn't find any option to fix my system. So I followed this guide to install a factory image (link).
3. I skipped through all of the setup processes and gave my phone wifi. Then I went into the system and did a factory reset.
4. After skipping thourgh the setup again I enabled adb and bootet into the bootloader "adb reboot bootlader"
5. From the bootloader I booted into TWRP by "fastboot boot twrp-3.3.0.0-taimen.img. In the recovery I set the display time out to 300s because for some reason once the phone timed out I could get into twrp any more and the screen stayed black.
6. I transferred the twrp installer and my rom by " adb push TWRP_installer.zip /sdcard/Download" and " adb push ROM.zip /sdcard/Download"
7. I first added the TWRP installer to the flash queue and then I added the rom and then falshed them both. This allowed me to install the rom.
8. For some reason TWRP was not installed. So repeat step 5 and only flash the TWRP_installter.zip
Problems I had:
- In twrp I often got errors that said unable to mount system or vendor. I decided to ignore the error but this thread might help
- Installing TWRP while the stock rom is installed led to the problem that touch didn't work in TWRP
- Entering a pin for the stock rom and then installing TWRP led to TWRP asking for a pin to decrypt my data. Apparently this is not the case if you use a stock image which is older
After flashing stock ROM ota and twrp installer zip the only way to get TWRP to respond to touch is if you disable screen lock and connect to your PC before booting TWRP.
I've found the most reliable way to flash factory images is do it manually with fastboot, latest platform tools installed and a Linux OS like Ubuntu or pop os.
But first do some research and get comfortable with fastboot commands. And dear god don't relock your bootloader unless you're ?% sure it's totally stock.
@schpongo,
Also, a good point to keep when flashing via TWRP is to flash/install ONE AT A TIME. As per the great @Az Biker, you should even reboot to the bootloader after each subsequent flash/install. So, in your case, it seems that you might/should be rebooting to the bootloader three times; one for TWRP installation, one for flashing the custom ROM, and one more for any other subsequent installation (i.e. custom kernel or custom font)...
Also, as it's been said before, but stock kernel doesn't play nice with touch commands on TWRP, and (usually) the only way around it is to reboot into bootloader using the adb command -- as opposed to holding the volume-down button or from an app.
I know you figured this all out already, but it might bear repeating just in case you didn't know and/or to help any other users here...
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Okay there's a few things remember here after flashing the mokee trebleize pack you should have had the addition of the vendor partition included in your TWRP file system if you have the blue spark TWRP version YOU SHOULD BE ABLE TO SEE THE ADDITION OF THE VENDOR PARTITION WHEN YOU GO TO MOUNT FOLLOWING THAT.
*** Make sure that after the trebleize is installed or whatever don't touch vendor partition ever just leave it alone you don't need to do anything to it it's fine if some ROM needs to update it you don't have to worry about wiping it first because it'll take care of that with the configuration script in the zip file. Even if you want to go back to a regular Android 8. 1 ROM you don't have to worry about the vendor partition the way it's set up the vendor partition that exist inside the one plus 5T that was created for Treble is not seen by any AOSP ROMs so it's going to create its own vendor folder inside of the system partition like it normally does and that you will not conflict because the fs tab does not Mount the new vendor. By leaving vendor alone and never touching it you're just ensuring that when you flashed yes eyes you're not missing something that's essential to the boot up process and it's one thing that you can from any potential uncertainty as to why a treble mage may or may not be booting.
Follow this....
Normal Android ROMs you would usually wipe system data cache D-cache if you were going to install a new ROM that wasn't just an upgraded version of the one that you were already running you'd have to start from scratch always. This is still what you should do it whenever you want to start and flash a fresh regular ROM or treble run always do that but it's how you proceed from here that is a little difference between the two.
With a regular ROM you would just go on to flash the ROM that you want to install followed by Gapps and so on.
When you want to flash a treble image you need to be on a clean fresh ROM that has treble support already good to go in that it can see that vendor partition that was made before and that it contains the binderized HALs needed as well. Because official treble support is still in beta with the OnePlus 5T the only officially supported treble Android 8. 1 ROM is mokee so you always want to start with a clean flash of the Mokee ROM because it also contains the supported kernel and ramdisk and other things as well.
Upon flashing a fresh version of mokee you want to go ahead and Flash no-dm-variety to ensure data is not encrypted because it will lead to a bootloop and the only way to get it to work will be to either format your SD card or to install the no variety which is the way to go just install it every time you flash mokee so that way you know everything is good.
**** I've only had experience using Android 8. 1 GSi so I'm not sure exactly how it would work concerning open G apps because I've only had to do it with two 8. 1 apps I'm not touching the Android P treble ROM until it's official so anything that I'm saying here has nothing to do with that if that's the image you're trying to install that I can't help you with it because I don't honestly know I remember reading something about that changing something different with it and I got to read up more on it.****
So next part depends on whether the GSI you're trying to flash comes with GFS included inside of it some do some don't I think most do but just make sure you read the instructions on the forms from where you download them from where they will tell you about the gf's the ones that I've installed that didn't have gf's on I would install mokee then I would flashed gf's to mokee but I've seen ones where people have flashed the gf's after flashing the treble images well and they didn't have any problem so just make sure you read into that one. obviously if the GS I can change the gf's then don't flash any before flashing or after as it will be flashed when we install it to the image and everything will be.
Which brings us to the last part if you did everything right up to this point then you should have no trouble installing the GSI through either TWRP or fastboot but before you do just make sure you go back to White and you just swipe to factory reset again so that we know that we cleaned out the data and we're on something clean after on encrypting the data if you did Flash no variety but remember don't wipe any partitions you want to make sure that you leave mokee on there. if you do it correctly you won't even need to wipe anything afterwards you should literally just need to be able to install the image into the system partition now and then reboot and it should work fine
It's your choice on how to go about doing it I've had success with TWRP but I've had more success using the fastboot method if for some reason you do try TWRP and it flashes and says success in 10 seconds then just reboot to fastboot mode in just flash it from there because you probably going to run into an issue just factory reset it again before you do it by swiping you don't have to wipe any of the partitions leave those alone.
So either go to the fastboot route which is put the phone in fastboot Point your terminal to the area where your GSI is located on your computer and then type fastboot flash system xxxGSI NAMEXXX.IMG.... OBVIOUSLY REPLACE THE FIRST PART WITH THE ACTUAL NAME OF YOURS. Next press enter and give it a few seconds and then you should see it's a success at which time you can reboot the phone and it should boot after a few short minutes.
If you wanted to use the twrp I believe I saw something about how you have to be on version 3.2.2 or above most likely for blue spark version as I use that one because it has treble support and I can see the vendor image even though I don't touch it. So if you flash it here you want to make sure instead of rebooting to fastboot like before you would just go to install and select image then find the image on your phone select it and then select the system images where you are installing it and then wipe the bar at the bottom for Flash and then upon it finishing you should hit reboot and let the phone boot up the first time set it up and then you can go back and you can go back to TWRP if you want to flash magisk or any other modules or TWRP Zips I've stated first then make sure you move the phone and go back and do all the modifying after otherwise you're getting stuck. I hope this helps feel free to contact me if you have any trouble.
theandroidas said:
Hi all,
so today I found a treble-enabled ROM of Android Pie and wanted to flash it. Thing is, I need to enable treble for me first. The treble check says that Treble is indeed supported, and so does the OnePlus website, but I don't have access to the vendor partition in TWRP. Using TWRP 3.2.3-1, by the way.
So, I read that MoKee enables Treble. Tried that, flashed the rom, flashed the radio and then the rom, factory wiped, flashed rom, factory wiped, flashed radio and rom, nothing. Still can't get Treble support. Then I tried kylothow's Trebliser, but nothing there either. I am realy at a loss here - I even reinstalled OOS (newest beta of course) and I couldn't get the vendor partition to show up, which is weird considering installing said trebliser actually states "Vendor partition found, good!" when installing, and then proceeds to in fact patch the vendor partition. It just doesn"t do anything, I can't install GSIs, can't even get the treble check to register that I do in fact have treble.
So this is where I turn to you guys. Do you have any idea what I could do in this situation? Please answer genuinely and don't post "just wait for an official android p".
Thanks!
Click to expand...
Click to collapse
Bro can u plz tell me how to get back to 8.1 oreo i am on 9.0 and didn't get treble support
Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?