That happens very fast BRICK need assist - OnePlus 3T Questions & Answers

Hello everyone
I brick my device yesterday by reflashing franco kernel r2 on top of r1 , then suddenly my device behavior was so strange it boot me into the device but i lost google services and the 2nd restart i stuck out
i tried to use twrp cant boot into it to restore
i tried many method but nothing happens
i tried to flashboot boot.img , flashboot system system.img (cant)
then i tried to install the stock recovery and that went successfully but when i try to boot into it i get stuck
so all recoveries not working stock and twrp
i already unlocked my device
any idea?

Here's the unbrick too thread for this device. I know it works because I did the same thing the other day flashing Franco from r1 to r2. Enjoy and make sure you read all directions carefully.
http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306/page2

Related

OnePlus nightmare

Gosh where do I start?
So I installed a custom ROM and everything was working perfectly fine it was a ROM from here but I noticed a connection problem to 4G and Three UK advised me to restore back to stock as it was working then I was pretty sure it wasn't the ROM but I checked anyways or was going to ..
The OnePlus website didn't allow me to download the Oneaplus 3T recovery image so I had to hunt online for it and once I flashed it into recovery I stupidly re-locked the device so nothing could be flashed to it the problem was that the recovery image was for a OnePlus 3 and not a OnePlus 3T recovery image... You can see where I'm at now so literally I thought I was screwed somehow the Qualcomm recovery tool bypassed the OEM lock not sure how but it did and was able to write onto it eben though the device was locked it was able to restore it to a stock lollipop ROM ... I then re unlocked the bootloader...
Im trying to install TWRP but it doesn't fully install it shows up when I force boot in fastboot but once I flash a image it will launch the ROM but TWRP won't launch back up so I keep having to go into fastboot and re flash and fastboot boot command it to get into it any ideas on how to install it properly it just shows a LED light on the notifications light whenever I try and access it, it isn't there unless I reflash and manually boot any idea how to solve it
Try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
That's what I did to solve it been bricked but that won't help me with the recovery flash ..
Samsung User3 said:
That's what I did to solve it been bricked but that won't help me with the recovery flash ..
Click to expand...
Click to collapse
Have you tried the toolkit??
Samsung User3 said:
Gosh where do I start?
So I installed a custom ROM and everything was working perfectly fine it was a ROM from here but I noticed a connection problem to 4G and Three UK advised me to restore back to stock as it was working then I was pretty sure it wasn't the ROM but I checked anyways or was going to ..
The OnePlus website didn't allow me to download the Oneaplus 3T recovery image so I had to hunt online for it and once I flashed it into recovery I stupidly re-locked the device so nothing could be flashed to it the problem was that the recovery image was for a OnePlus 3 and not a OnePlus 3T recovery image... You can see where I'm at now so literally I thought I was screwed somehow the Qualcomm recovery tool bypassed the OEM lock not sure how but it did and was able to write onto it eben though the device was locked it was able to restore it to a stock lollipop ROM ... I then re unlocked the bootloader...
Im trying to install TWRP but it doesn't fully install it shows up when I force boot in fastboot but once I flash a image it will launch the ROM but TWRP won't launch back up so I keep having to go into fastboot and re flash and fastboot boot command it to get into it any ideas on how to install it properly it just shows a LED light on the notifications light whenever I try and access it, it isn't there unless I reflash and manually boot any idea how to solve it
Click to expand...
Click to collapse
LOL so your post comes off as you are trying to blame oneplus. Yet everything u explained and have done had everything to do with user error. Rules of xda..... Research. Research research. Once you think u have it research again and makes sure to read it. Did I say research?

Moto G7+ Flashing Lineage fails -> Touch doesn't work anymore - Brick?

Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.

Recovery Bootloop

So I successfully unlocked my bootloader and flashed custom ROM and recovery, first boot it was okay, I was able to setup Android and installed apps, now when I rebooted it, it only boots to recovery. Phone can still be detected by my PC, can also get detected in fastboot when in bootloader. So I think there's really a workaround for this I just didn't know how and I am now hesitant to follow web tutorials if it isn't an official forum just like this.
Things I already did:
Reinstall ROM
Reflashed custom recovery
Cleared Data/Dalvik/Cache
Factory Reset
Flash the stock firmware by SP Flash Tool, it'll help to revert back to stock and stop boot loop!

PHONE STUCK IN BOOTLOOP AFTER FLASHING KERNEL

I HAVE FLASHED A CUSTOM KERNEL CALLED "MINATI XENODROME" IT IS COMPATIBLE WITH THE DEVICE
AFTER FLASHING IT IN TWRP MY PHONE IS IN BOOTLOOP AND NOT RECOGNIZED BY FASTBOOT
MY DEVICE WAS RECOGNIZED BY FASTBOOT BEFORE THE FLASH
PLEASE HELP ME I AM SCARED
I TRIED REFLASHING WITH XIAOMI FLASH TOOL BUT IT GETS STUCK ON "fLASHING PRE-LOADER" AND THAN SAYS THAT IT COULDNT UNBRICK MY DEVICE
MY PHONE CAN BE BOOTED INTO FASTBOOT BUT WONT BOOT INTO THE RECOVERY
I FLASHED STOCK MIUI RECOVERY ROM V11.0.5 AND FLASHED THE KERNEL AFTER
PLEASE MY GOD HELP ME
Somehow this fixed itself by me just installing python?????????????????????
i dont ****ing know???
but i will take it
As far as i know its not good to flash kernel on this device with TWRP,better use adb.

always booting into twrp recovery

installed twrp successfully without any errors, phone booted and worked, later i installed magisk zip from twrp done successfully but phone stuck on nokia logo for some time, and always booting into twrp recovery, anyone pls help
maybe it was hard resetted.. try to do factory reset but if doesn't work flash a new rom
greg10 said:
maybe it was hard resetted.. try to do factory reset but if doesn't work flash a new rom
Click to expand...
Click to collapse
Flashed a stock firmware from OST, working fine now, not rooting again better stay away from things idk

Categories

Resources