Hello!
Just today I bought myself a second-hand Oneplus 3T that had issues booting into the system. The start of the boot animation would show, but after that the screen just goes black and a white notification light turns on. Confident in my basic skills, I bought it and started trying things.
It boots into recovery and fastboot, all nicely, so first I tried wiping everything with stock recovery and then installing OOS that I downloaded from oneplus. Installed it through the stock recovery ADB Sideload, didn't change a thing. So since the bootloader is locked and cannot be opened, I went on to tryin the Qualcomm 9008 unbrick. Went through with it got a green text in MsmDownloadTool and all, but still nothing. Tried to install that same OOS on this "fixed boot partition" but the only change I noticed that I couldn't even get the start of the boot animation. Just the oneplus logo splash screen and black with white light after that....
If the device is powered down it shows the offline charging screen and a green notification light.
The device is out of warranty, I need the help of you people.... I might try installing twrp and formatting the system partition and installing on that, that is if I can get twrp installed in this kind of a situation.. Thanks!!
EDIT; Tried installing twrp, of course cannot flash it through fastboot but I also tried tricking MsmDownloadTool to install twrp instead of stock to no avail. I got the boot animation starting back but nothing else, also clicking "Install from internal storage" in recovery does absolutely nothing, doesn't bring up a file explorer like I would have expected..
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
thes3usa said:
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
Click to expand...
Click to collapse
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
MrMatson said:
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
Click to expand...
Click to collapse
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
thes3usa said:
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
Click to expand...
Click to collapse
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
MrMatson said:
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
Click to expand...
Click to collapse
As I'm aware, you can select packaged files which you have downloaded. It is basically the same file the MSM tool downloads, but it could be a higher version. (I.E: MSM tool downloads OOS 3.5.6 by default, but you could flash a file which you downloaded yourself, which can be OOS 4.0 or so.)
Correct me if I'm wrong, I've only used the MSM tool once or twice, and I'm speaking from reading about it on other threads.
Don't panic, your phone can get into fastboot and recovery, so you can definitely save it. Its just a little annoying, but it's not like its a Samsung device. I've myself had the white light. It can be easily fixed.
Supporting each other is what a community is for. Helping each other is what we do.
Good luck, and update us on what happens.
Update: Tried versions 3.0.6 and 3.0.8 of MSM in addition to the version 3.0.0 I had before. No luck. I'm starting to feel like I've tried everything there is to try... The device works everywhere else like it should, it just doesn't boot into system. Recovery and fastboot and Qualcomm mode are available, just can't seem to fix this with those... I need some help
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
He said in OP he can't flash TWRP.
krombopulos said:
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
Click to expand...
Click to collapse
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
Yea... I got my bootloader locked so no luck there... Thanks anyway!
MrMatson said:
Yea... I got my bootloader locked so no luck there... Thanks anyway!
Click to expand...
Click to collapse
Yeah You need to UBL first bro, try via fastboot to flash twrp.
Im using msm tool first, then flashing OOS, next UBL
I don't think UBL will help either, as I am stuck on stock reocevoery.
Update: https://forum.xda-developers.com/general/rooting-roms/installing-twrp-locked-bootloader-t3669879 this guy seems to have succeeded in doing what I tried on a Xiaomi phone. I don't know if it's possible to replicate on a oneplus though... No luck so far
MrMatson said:
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
Click to expand...
Click to collapse
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
Oh... As I have stock recovery, the back key can be used to go back, and it seems to work... Well, any hardware modifications will have to wait, as I do not have a T2 driver and there seems to not be a single one in stock in Finland anywhere, gotta wait out on one from china.... But maybe trying some other parts will work The navigation keys also light up briefly when booting, for a second or so. Thanks!
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
koax88 said:
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
Click to expand...
Click to collapse
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
MrMatson said:
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
Click to expand...
Click to collapse
Just curious, did the seller give you any information about why the device was bricked?
Cause if he was just trying to modifying the software without knowing what he was doing you should have resolved it by now, as MSM-download-tool does not show specific errors I assume it's able to write software correctly to the corresponding partitions but then something prevents it from booting up to android system, unfortunately the chances for any hardware related problem are definitely there, even very likely...
So if you bought the device assuming a software related problem but got a hardware defect it could look just the same from outside, only further possibilities I see is by having a look inside and even then you'll need some luck finding the issues...
Don't know if you have one of these little phone repair shops around but they're helpful sometimes getting advice about hardware, etc. also YouTube is a great resource for tutorials...
Just my 2 Cents, good luck
- hope you succeed in the end!
Sent from my OnePlus 3T using XDA Labs
Dear Friends,
since i press wipe data after update fail, my phone is looping on mi icon. my bootloader is locked and i cant Enable USB Debugging since i cant accese my phone.
i tryed mi flash tool wont work also MiPCSuite wont recognise miflash_unlock saying my account is not bound to the phone
i am looking for any kind of help (exept opening the phone i am affrid to damage it).
Best regards,
Mor Nixon
hey man
i have an answer for you(me)
i saw the lite and jesus came to me after seeing me suffering the last few weeks
test point worked only with a wierd specific mi flash i found something that i think stimulate 64 bit
after that i had problems with google store services, itried endlessly but couldnt go on no more
i install twrp and flash eu miui unofficial and right now its showing me good sign (hope it will stay that way)
until next time man..
morzniks said:
hey man
i have an answer for you(me)
i saw the lite and jesus came to me after seeing me suffering the last few weeks
test point worked only with a wierd specific mi flash i found something that i think stimulate 64 bit
after that i had problems with google store services, itried endlessly but couldnt go on no more
i install twrp and flash eu miui unofficial and right now its showing me good sign (hope it will stay that way)
until next time man..
Click to expand...
Click to collapse
Great.. you're your own savior. Nice to see ya
__PG__ said:
Great.. you're your own savior. Nice to see ya
Click to expand...
Click to collapse
i was so happy about it
until ...
the phone keeps having random crashes...... bHAaaaaa
and i tried many global stable custom roms X_X
ill start praying for a new god
morzniks said:
i was so happy about it
until ...
the phone keeps having random crashes...... bHAaaaaa
and i tried many global stable custom roms X_X
ill start praying for a new god
Click to expand...
Click to collapse
Maybe it's due to a specific app.
Unlock bootloader then Flash Any Custom rom. Or flash MIUI via Fastboot method and check the crash. Most probably you have done a Dirty flash instead of Clean flash.
Wipe data/system/cache/dalvik then flash your ROM for a Bugless experience :highfive:
i did Clean flash in all of tham.
ill just try to go for the bes custom rom that is simple. im not looking for customisation at all, just want the phone to work with minimum features, stable...
if you know witch is the rom for me that could help :]
im now going to check who crash less frequently
cuse miui reboot sometime 4 times in 1 minute
Can you tell me what you did? Also was your internal storage intact or was erased? Because I am also having the same issue.
girishpai said:
Can you tell me what you did? Also was your internal storage intact or was erased? Because I am also having the same issue.
Click to expand...
Click to collapse
i opened the back of the phone and touched the test point 2 dots
then i connect to the computer and i was able to flash miui official rom (any one i wanted)
Hi,
I recently bought this phone knowing the touch was not responsive and just looking for any clues on where to start.
The screen works and using the side buttons can adjust volume (visible on screen) and bring up power menu but can't do much else since the touch is not working.
the phone has been factory reset so it loads into the MIUI 12 setup guide. I've tried linking it up with Mi PC suite with no luck. is this looking like a hardware failure or software maybe?
Also there is no damage to the screen
Thanks in advance
Lee
i think you will need to find xiaomi mi flash tool for your device and flash the stock firmware
you can download it here. I dont know much about that phone though so im only making suggestions.
Try to flash the whole MIUI firmware again.
Thanks for the help, I suspect it might be a firmware issue but had no luck with flashing using some tools so far but I'll try that link and see what happens
I've applied for the bootloader to be unlocked and waiting the 7 days for that, is there anything I can do in the meantime?
I've confirmed that the phone works and is not crashed as I plugged a mouse into it and am fully able to use the phone this way.
I tried to flash update via local but got an error that I cannot flash lower version.
Anything I'm missing?
hello everybody
this redmi note 9 global 3/64 gb was working just fine.
one day the screen became so lagy so i tried to factory reset it then the screen became totaly not responding so i took it to repair shop he said the touch screen was the problem so he replace it, and didn't work so the problem was not in touch screen.
then suddenly the phone got hard bricked i give it to many repair shop and they can't fix it, every repair shop said different storys, one said the problem is in motherboard's circuit, another one said the phone is global but the manufacturer put an Indian motherboard...
i lost a lot of money but the phone is not fixed
then this week i tried to check if the motherboard stills alive so i plug it on my pc then i saw the usb port of this phone on device manager, so i tried to flash it with sp flash tool,, i downloaded miui 13 fastboot rom (the phone was on miui12 before he got hard brick), i install drivers and bypass and i run sp flash tool i load all the settings, when i press start it says "STATUS_DA_HASH_MISMATCH".
i tried everything to solve this, but nothing, i saw many people who got this error message and i tried there solutions but NOTHING!
i'm not going to more repair shops because one of them stole my selfie camera, so this is my last hope.
i hope someone who has experience to help me.
rz_q said:
hello everybody
this redmi note 9 global 3/64 gb was working just fine.
one day the screen became so lagy so i tried to factory reset it then the screen became totaly not responding so i took it to repair shop he said the touch screen was the problem so he replace it, and didn't work so the problem was not in touch screen.
then suddenly the phone got hard bricked i give it to many repair shop and they can't fix it, every repair shop said different storys, one said the problem is in motherboard's circuit, another one said the phone is global but the manufacturer put an Indian motherboard...
i lost a lot of money but the phone is not fixed
then this week i tried to check if the motherboard stills alive so i plug it on my pc then i saw the usb port of this phone on device manager, so i tried to flash it with sp flash tool,, i downloaded miui 13 fastboot rom (the phone was on miui12 before he got hard brick), i install drivers and bypass and i run sp flash tool i load all the settings, when i press start it says "STATUS_DA_HASH_MISMATCH".
i tried everything to solve this, but nothing, i saw many people who got this error message and i tried there solutions but NOTHING!
i'm not going to more repair shops because one of them stole my selfie camera, so this is my last hope.
i hope someone who has experience to help me.
Click to expand...
Click to collapse
Try mtk auth bypass tutorials on YouTube
the DA file was not compatible with your device, mostly it just work fine with MTK_AllInOne_DA.bin, try looking for DA file that compatible with your device and try flashing it again. or here, https://m929.ru/_pages/mtk_bypass.html
loftheaven said:
the DA file was not compatible with your device, mostly it just work fine with MTK_AllInOne_DA.bin, try looking for DA file that compatible with your device and try flashing it again. or here, https://m929.ru/_pages/mtk_bypass.html
Click to expand...
Click to collapse
i installed the baypass tool on this link and i tried to flash using MTK_AllInOne_DA and DA_6765_6785_6768_6873_6885_6853 but didn't work