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
Hello !
I update my Zenfone 4 (ZE554KL) to Android Oreo (WW_ZE554KL_15.0405.1711.76) via "normal" recovery mode. I downloaded the firmware from official website.
After that, all went ok, except that my USB isn't working anymore on any computer. When I plug the cable, nothing happens, nor on phone, nor on PC. Before update, it worked perfectly.
I tried restarting it (of course), cleaning the setting cache and enabling Develop Mode again, changing debug mode on and off and revoking pemissions.. nothing worked, after all. :crying:
Did this happened with someone else? If so, someone could fix it someway?
Thanks in advance !
wrong forum, you might be looking for this one: https://forum.xda-developers.com/zenfone-4-2017
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 !
Hi, I have just resurected my Mi8 it was with boot loop no network / no wifi. I coudn't activate usb debugger mode. It have been in a drawer for nearly 2 years.
Today i was looking at firmwares and found Qualcom QCT fix, trying to flash the patch, I din't flash it, but in one of the loops get access to the setting due to a crash and wipe everything (Default recovery don't wipe everything) After that the wifi came back and the bootloops end.
After that updated to MIUI 12.0.3 (The higher detected was on 12.0.1). Enable USB debugger mode, go to developer tools - My Mi Unlock Status and is locked.
I will try to unlock (I think that is a requirement to flash twrp), flash twrp and another rom.
Here goes my questions:
- I don't know why on MIUI Stock OTG is not working for me. I wanted to conect it by ethernet but not detected, nor USB or external keyboard.
- which is the best rom up to day with OTG enabled. Xiaomi eu 12.5 (Based on Android 10) or Pixel Experience?
- Stock Kernel or custom Kernel?
- Trying to fix my phone today ended with 10 diferent drivers and now abd don´t detect my phone or detect it offline