Related
Hi there,
perhaps you guys can help me
I use a onePlus 3T 128GB and directly after delivery I update the OS, install twrp, make a clean backup and then personalized the phone.
Runs quite good but yesterday I wanted to update the system to 4.0 Nougat...
So I downloaded the full installer, backuped the full current system via twrp and then flash and install the 4.0 version.
Yeah... doesn't work really good...
After the Pin and the code for the sim card, the OS ask for a third pin code but none of both works. And I never have another pin code since years...
Then I wipe the cache and system with twrp and restore the last backup. Doesn't work. It only boots to the onePlus Logo and then nothing happens.
Same for the first clean backup without any personalisation...
For now I have an great smartphone that doesn't work... yayy...
Anyone of you has an idea how can I get my running phone back – with all my data and apps?
Edit1: adb sideload doesn't work
Edit2: Full Installer installed >> reboot >> no OS installed
Thanks for all guys.
Oliver
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
You said you wiped your system..
what did you expect?
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
raj7749 said:
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
No, it doesn't work
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Jo_Jo_2000 said:
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
When wiping system before installing a full roms zip (not only an incremental update), I would expect a working, os containing partition - like on the oneplus one (did that many times on bacon). But I can confirm, it's not working on opt3; at least not with oos4. In this case I need to restore working systemmpartition (from twrp-3.0.3-0), and flash then the rom zip.
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
GammarursPulex said:
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
Click to expand...
Click to collapse
Would you try the following: From twrp restore your very first backup (firmware, system and boot), don't leave twrp and wipe (reformat with f2fs) data (I'm talking of the entire userdata partition, not only "wiping data without wiping media"); flash the full oos4 zip (the one with 1.4GB); don't leave twrp, go to Advanced->copy logfile. Try to boot system.
If the system stiil refuses to boot up completly, get the logfile with adb via twrp and show us.
DO NOT try this, without usb-c otg cable and usb stick, because you are reformating your data partition. That's the reason I have not tried this: need to get an usb-c otg cable (BTW: recommendations on usb-c otg cables welcome, but OT: so PM).
GammarursPulex said:
No, it doesn't work
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
mcdachpappe said:
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
Click to expand...
Click to collapse
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
GammarursPulex said:
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
rms4067 said:
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
Click to expand...
Click to collapse
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
GammarursPulex said:
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
Click to expand...
Click to collapse
When you say load the backup, you mean a backup that you made in TWRP recovery, prior to bricking your phone?
My experience with the unbricking guide was that it in essence did a full wipe and reset (including the recovery partition). That would eliminate TWRP from your phone as well as any stored backups you had.
When I unbricked, I opted to just leave it stock as nougat was around the corner.
I also re-read your original post. I wouldn't have considered your phone "bricked" at that point.
I would bet that you could have booted the phone into TWRP.
You'll want to keep these things in mind too for future TWRP encryption issues (it's a known issue that most likely won't be fixed).
1) before you make a twrp backup, remove any figerprints/pins/passwords from your device, sometimes prevents issues for me
2)if you existing pins/passwords don't work try "default_password" that may work
3)if all else fails, boot into twrp, navigate to /data/system/ and down the list will be a few files to delete
- password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
4) the last step is always the first step for me, too many issues with twrp and encryption
GammarursPulex said:
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
Click to expand...
Click to collapse
u r doing something wrong.. please follow guide correctly
It works 100℅
Just out of curiosity, did you unlock the bootloader before you did everything? Also did you go into settings -->developer mode and turn on OEM unlock and USB debugging?
From my experience, try wiping everything through twrp --> install the firmware/backup --> and then try doing another wipe and reboot. Now I understand you might lose your root/SU after wiping, but perhaps this will at least boot into the system for you.
If all else fails, try using ODIN and flash your stock firmware http://downloads.oneplus.net/devices/oneplus-3t/
EDIT:
If you're having driver issues try this.
1. Go into device manager (as admin)
2. Double click the device that you're having trouble with
3. Click on "Details" tab
4. Under "Property" dropdown, choose "Hardware Ids"
5. When you select that you should see a bunch of values under there. Right click the first one and copy it.
Ex:\ I have an S7 phone so mine looks like "USB\VID_04E8&PID_6860&REV_0400&ADB"
6. Now the value you copied, try searching it in google. Or paste it on here for us to help you find drivers compatible with it. Usually you can find compatible drivers in google. Once you find them and download them, if you go back to that device and click "Update Driver" you can manually point to the extracted drivers. It will find the compatible *.inf file and install it for that device.
Hope this helps!
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
this works for me, every time i kill my 3T.
you must be doing something wrong.
Follow everyline
Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?
after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.
Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.
FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out
I have a OnePlus 8 Pro running Oxygen OS 11.0.4.4.IN11AA. Upon installing Magisk, I can no longer turn Wifi on. I have tried restarting, clearing the cache from recovery, resetting network settings, basically all the things the "wifi wont turn on help pls" guides say to do. Mobile data and bluetooth work absolutely fine, so what's going on?
Sound is also non-functional. Even after plugging in earphones (which worked with this phone previously) nothing comes out, and the phone doesn't even seem to recognize them. I also noticed that after a reboot the volume controls are set back to the defaults.
Additionally, the system is very slow to start up and the screen stays black until after the unlock prompt (which displays over the black screen) and then the wallpaper and everything else loads. (after which the device is responsive as normal)
These problems occurred even without installing any modules or otherwise modifying the device. I'm using the latest version of Magisk, 22.0 (22000).
I originally tried to make a GitHub issue, but it was closed by the bot since I didn't follow the template GitHub never showed me. Also, us non-canary users experience issues too. [mini-rant over]
Sorry if this is a duplicate, the search system appears to be malfunctioning since the updates.
The Fix!
Looks like I'm solving all my problems today. I had a hunch that the culprit was the boot.img which I downloaded--it was corrupt. So I went to OnePlus' site and downloaded the OTA package, extracted the boot.img from that, and flashed it through fastboot. When I rebooted, I was greeted with the beautiful almost old-IOS charging sound, and Wifi!! That boot was quite speedy too!
Hi could you explain how did you reboot your phone i have totally same problem...i tried msm download tool but i cant get my device to show there....could you please tell me how did you put OTA package into phone ? thx
FIXED!
in the end I was able to use MSM Download tool....i just had to manually download Qualcomm drivers so that my phone can be recognized. After that MSM worked and rebooted my phone totally clean. Gosh not gonna root for a while now XD
PS: More fun is that my Windows PC wasn't connected to internet so i had to download everything on my macbook and through USB stick I was bringing all app to Windows.....longest 6 hours of my life
Jaywinik said:
Hi could you explain how did you reboot your phone i have totally same problem...i tried msm download tool but i cant get my device to show there....could you please tell me how did you put OTA package into phone ? thx
Click to expand...
Click to collapse
From fastboot, use the volume keys to select Power Off and then press the power button once. Make sure the phone is unplugged while doing this. Then, with the MSM tool ready on your computer, hold down both buttons on your phone and plug in the cable from the phone to the computer. It should automatically boot into EDL mode, and MSM should say Connected.
My
Jaywinik said:
Hi could you explain how did you reboot your phone i have totally same problem...i tried msm download tool but i cant get my device to show there....could you please tell me how did you put OTA package into phone ? thx
FIXED!
in the end I was able to use MSM Download tool....i just had to manually download Qualcomm drivers so that my phone can be recognized. After that MSM worked and rebooted my phone totally clean. Gosh not gonna root for a while now XD
PS: More fun is that my Windows PC wasn't connected to internet so i had to download everything on my macbook and through USB stick I was bringing all app to Windows.....longest 6 hours of my life
Click to expand...
Click to collapse
When I had to do this I didn't connect the device to the network since I don't trust Windows 10 not to open a billion ports up and use my infrastructure for Microsoft's business. Copying to and from a crappy 2.0 drive sucks!
Hello everybody,
To explain things a bit better than just this title. I have a Mi 5 that was working smoothly for quite a long time. Had a modified MIUI ROM flashed on it with many specific apps such as xposed, Magisk and also TWRP. However, my GPS has turned completely dead for some months. Couldn't use it anymore. After some researches, I found out it could be software related. So I decided to flash a new ROM (AOSP Extended) to see if that could fix the GPS issue.
First I backed up the whole system via adb on my laptop and then wiped the whole system. It turns out after trying to flash the AOSP ROM, I came across a message saying I should have MIUI 8.1.30 or older. Or something like that... Can't remember exactly. Just read that I was supposed to update my ROM to a newer stock ROM to be able to flash AOSP in a second time. I did a lot of different operations and I can't remember them all but it turns out one moment, adb started to flash a ROM because the adb command line was saying it. But it failed. Aftert that moment, my phone definitely got bricked. I have no clue what exactly happened, it's kind of confused...
Currently, the phone is always displaying dark screen with mi logo and "unlocked" mention below. Power and volume up will just reboot it to the same state (meaning twrp is not longer installed or accessible). In this dark screen mode, plug the phone to a computer will do nothing, it's not even detected in devices manager. On the other side, power and volume down will boot the phone into fastboot mode, the computer beeps when I plug the USB cable and I can briefly see the Android device with a yellow warning in the dev manager. But after something like 20 seconds, fastboot mode goes off and phone restarts on black MIUI screen.
I've tried to install Google drivers, Qualcomm drivers and did numerous actions but the phone isn't detected anymore. Also, tried to type command "adb devices" in the short time when the phone is detected by computer in fastboot but it shows an empty list. I'm pretty desperate, seems I've tried anything and I've no ideas now... Just saw there is possibly a hardware fix which requires to dismount the back of the phone. Not sure what it does but I'll try it out if no other solution shows up...
Any idea is welcome ! Thanks
Well, looks like my thread wasn't so popular Finally found a workaround after nearly 8 hours searching for a fix. Thought that might help anybody else having the same struggle as mine. What I can tell is that it's not related to the computer used since I've made the same operations on 3 different computers, same problem for each of them. In fact, there were two problems :
First the bootloader not remaining more than 30 seconds. To stop this, I had to open the devices manager and as soon as the Android device would appear after turning it into Fastboot, I would right click on the visible device (appearing with an exclamation mark) and update manually the driver following the process that is described in many topics (locate the Google Android devices USB drivers that I downloaded right before). The time is quite short so you have to be pretty fast, otherwise, the MI 5 would disappear, forcing you to do the fastboot mode operation again. I have to say that doing it without the device being recognized is not working. So if you install with the legacy driver option, it's not going to be associated directly to the device. At least, not in my case.
Once I had done this, the Fastboot mode would remain on. I found my way pretty fast until that moment but the problem was adb wouldn't detect my device. Typing "adb devices" command would return no result, no matter what I did. Strangely, installing an old version of MiFlash (last ones gave me error) would help the computer to detect the device. I don't know why, possibly because the drivers are better ? Anyway, MiFlash helped me to access the phone and Flash a new ROM. Usually, I was just using adb and it would do the job but this time not.
Hope it can help !