Disclaimer: phones not root, knew nothing about rooting the device prior to the incident, so please bear with me for a second here.
Dropped my phone few days ago, screen broken(black screen) but still works. Hoping to recover the stuff in it.
Did some research, turns out that the phone can be remotely control on PC
-USB debugging wasn't enabled on my phone so it wasn't feasible.
Did some more research, turns out that USB debugging can be activated alternatively by running adb shell
-need to mount system and data partition, but phones not rooted so it was no good.
Did a little bit more research, turns out that system and data mount can be done via flashing a kernal with recovery in ODIN/download mode.
-went to the Kernal pages, tried to figure out how to install but it seems that the kernals available for Note 5 requires OEM to be unlocked.
That being said, I am properly lost now. Can someone give me some advice to it?
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
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.
Hi to all!
I have a Cherry Mobile One G1, pure stock (Android N, not rooted, no recovery and USB Debugging DISABLED), been with me for almost 2 years bought brand new. What happened was I was going to download a movie then suddenly the phone restarted and its stuck on bootloop. The only thing I can do with it is boot it to fastboot. It can be detected by my pc's device manager as Android Bootloader Interface but ADB terminal cant seem to detect it. Is there anything I can do to revive it? If there is, can any genius mind help me out?
My dilemma now is trying to turn USB debugging via fastboot which is not possible since adb could not even detect my device. If only I can have it enabled, I would know how to fix the rest.
Any help would be very much appreciated. Thank you and God Bless!
This happened to me before. factory reset via stock recovery fixed it. If you can't boot to recovery try removing the sd card first. It will take a while to reset, don't take the battery off while it does and make sure it's charged.
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!