UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Restore Bricked OnePlus 6T on Linux

    Scheduled Pinned Locked Moved Oneplus 6/6T
    19 Posts 11 Posters 8.2k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • S Offline
        Stefano @hekathegreat
        last edited by

        @hekathegreat Hi, I'm facing same problem here on Op6t. No luck with Linux, nor with Windows.
        What did they tell you in the repair shop? What was the issue there? Corrupted partition/s?
        29€ is not bad price for restoring it, better than to buy another phone.

        H 1 Reply Last reply Reply Quote 0
        • MrT10001M Offline
          MrT10001
          last edited by

          I repaired a bricked Oneplus3 using the ADB sideload feature in recovery and the zipped stock ROM.

          Xiaomi Redmi Note 7.... And more...
          I have too many devices...

          H 1 Reply Last reply Reply Quote 0
          • H Offline
            hekathegreat @Stefano
            last edited by

            @stefano After installing PostmarketOs, there was no way back to android, at least not with my knowledge. After hours of trying, I took my phone to service, here in Finland it was mcare, which supports mainly apple and oneplus devices. Just look some oneplus service and dont tell them that you have been playing with custom roms πŸ˜„ My op6 got onto bootloot so "that was the reason", no questions asked.

            1 Reply Last reply Reply Quote 0
            • H Offline
              hekathegreat @MrT10001
              last edited by

              @mrt10001 if you can get into recovery, it is not bricked πŸ˜„

              S MrT10001M 2 Replies Last reply Reply Quote 0
              • S Offline
                Stefano @hekathegreat
                last edited by Stefano

                @hekathegreat O.K, thanks for the info.
                I was flashing TWRP recovery and I already had UT on it. Never happened to me with any other phone, well, not in such a level that I can't fix it myself. I might try again to use MSM tool, but since I don't use Windows, it's rather a pain to do it. So many versions of MSM tool, so many versions of drivers to try... I'll give it another shot and then just repair shop, I guess...

                Edit:
                I managed to fix my Op6t with Windows ( yeah, unfortunately not Linux.
                I used MSMtool and it finally worked. The culprit was , you have to install the driver once in Qualcomm Crashdump mode connexeted to PC, then unplug it, swithch the phone off, launch the MSMtool, hold the volume up on the phone and at the same time just plug it to PC. Then MSMtool program already running, it just detect it and do all for you. Clever. I couldn't believe it. I was trying to flash the phone with fastboot for fortnight now and I just done it and I'm so happy. Phone is ok. UT is going there very soon.

                1 Reply Last reply Reply Quote 0
                • MrT10001M Offline
                  MrT10001 @hekathegreat
                  last edited by

                  @hekathegreat If you get into recovery and can't do anything else, it's bricked. πŸ“΄ πŸ“΅ :frowning_face:

                  Xiaomi Redmi Note 7.... And more...
                  I have too many devices...

                  TotalRandoT 1 Reply Last reply Reply Quote 0
                  • TotalRandoT Offline
                    TotalRando @MrT10001
                    last edited by

                    @mrt10001 With the 6T it can often "look" bricked. Hold for bootmode as long as you humanly can, and when you can hold no more it should turn on.


                    Nerd with UT on a OnePlus One. OnePlus 6T waiting in the wings for VoLTE.

                    MrT10001M 1 Reply Last reply Reply Quote 0
                    • MrT10001M Offline
                      MrT10001 @TotalRando
                      last edited by

                      @totalrando I use all my tools at hand and have a lot of success in recovering bricked devices. The Oneplus3 that would not leave recovery after many, many attempts, I managed to sideload Android, which worked, then allowed me to unlock the bootloader, which makes it so much easier for future repair. I have sore fingers from the amount of power and volume button holding on these devices.

                      My advice is if a phone is bricked i.e. is totally dead, leave it on charge for 24 hours. If that doesn't work, charge it attached to a PC, not a laptop or plug in charger. I have got a lot of devices going again just by plugging it into a PC (making sure the PC is on) for an hour or so.
                      If it boots to the bootloader and that's all it does, try to erase/format the cache with fastboot. If that fails, good chance the storage (eMMC) has failed.
                      If you can get TWRP going, format the partitions and wipe the data. If it fails at that, it is either a partition table error or there is hardware failure. I have seen this lots on the Nexus4 and 5, repartition ZIP is fantastic here.
                      If all that fails and you always boot back to recovery, it usually means a hardware failure, CPU, eMMC, RAM. I persevere here just to make sure, and will strip the device down and look for any flaws on PCB's or connectors. Usually you will see moisture damage that can be repairable with some isopropyl alcohol. The biggest cause of shorts though is usually a damaged USB connector. Thankfully most these days are a separate cable as my solder skills are awful. That can cause all sorts of funny issues.
                      Once all back together, if it works great. If not I break it for parts.
                      So to me bricked is a dead phone, a phone that boots to the bootloader and stops, a phone that boots to recovery and stops or the phone that bootloops after you have tried everything....

                      Xiaomi Redmi Note 7.... And more...
                      I have too many devices...

                      J 1 Reply Last reply Reply Quote 1
                      • LakotaubpL Lakotaubp referenced this topic on
                      • J Offline
                        jordimas @MrT10001
                        last edited by

                        @MrT10001 Hi, did you sideload android in a locked bootloader? Because you said you unlocked the bootloader after it. I thought it was impossible to sideload or flash anything in a locked bootloader (sideload is like a flash). Also, to sideload you only can do adb sideload, but from the fastboot you can't use adb.

                        MrT10001M Mario.CHM 2 Replies Last reply Reply Quote 0
                        • MrT10001M Offline
                          MrT10001 @jordimas
                          last edited by

                          @jordimas I sideload the stock ROM through the op3 stock recovery. That can be done with a locked bootloader.

                          Xiaomi Redmi Note 7.... And more...
                          I have too many devices...

                          1 Reply Last reply Reply Quote 0
                          • Mario.CHM Offline
                            Mario.CH @jordimas
                            last edited by

                            Hi @jordimas,

                            The "recovery mode" is part of the boot loader, similar to the PC.
                            It can be used to repair and/or sideload the current OEM operating system.

                            Fastboot is more like a "bios".
                            Fastboot is a "command-line tool" with many more commands than just the one Β«flashΒ».
                            But be warned, you can destroy your device, because similar to the bios of PCs, there are different fastboot properties depending on the device manufacturer.

                            See also here https://technastic.com/fastboot-commands-list/#Fastboot_Commands_List

                            and in particular here https://technastic.com/fastboot-commands-list/#Fastboot_Command_to_Unlock_the_Bootloader

                            and https://technastic.com/fastboot-commands-list/#Prerequisites

                            finaly https://technastic.com/fastboot-commands-list/#Reboot_the_Device_into_the_Recovery_Mode

                            πŸ‘‰ You should read up more before you try it out. Above all, it should always be device-specific.

                            Greetings Mario

                            πŸ“± Oneplus Nord N100 UT20.40 (OTA5); then Xperia X (since 2020) at last UT 20.04(OTA5), now out of service due to defective camera
                            🐎 When you realize you are riding a dead horse, get off!
                            My languages skill: πŸ‡¨πŸ‡­πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ, and only orally: πŸ‡¬πŸ‡§ πŸ‡ΉπŸ‡­

                            1 Reply Last reply Reply Quote 0
                            • W Offline
                              wurmphlegm @AntiDroid
                              last edited by

                              @AntiDroid So i ran the script you provided with all the images, and it got pretty far. It flashed after the part where it said go into the twrp main menu and then press Y to continue, then it restarted....but now my OnePlus6T will not go back into fastboot mode. It just automatically boots into Qualcom CrashDump Mode. It does nothing else.

                              AppLeeA 1 Reply Last reply Reply Quote 0
                              • AppLeeA Offline
                                AppLee @wurmphlegm
                                last edited by

                                Hi @wurmphlegm

                                Have you tried to force the fastboot mode?
                                I remember having to do it manually as the installer wasn't able to make my device comply.
                                So I used the volume buttons and power button to make it happen.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post