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?
Related
I have a Z here with broken screen/digitizer. ADB is not enabled, I want to enable through any means and then config it via vnc or similar with the long term goal of turning it into a headless mediaplayer(xbmc).
I am able to control it using the painstaking method of plugging in a usb kbd or mouse, doing some blind movements and then swapping that out for an mhl/hdmi cable so I can see where I am at.
With that I have been able to disable the lock screen, start terminal emulator, get into developer options and some other things.
The phone had previously been rooted and had adb enabled but my SO had updated it to stock OTA 10.4.B.0.569 (4.3)before The Drop without my knowing so I lost both of those.
So, the problem...I cannot enable adb. I can get into the developer menu but the options are greyed out. I cannot select anything. I don't know why. I suspected it was because there was a usb device plugged in (either mouse/kbd or screen) but I have checked a Z tablet running 4.2 and a Z1, which is running 4.4.2 and you can enable usb debugging with a device plugged in on both those. I tried toggling dev options off/on, but no difference. Annoying.
Because I have lost root I cannot enable it via terminal either.
I unlocked the bootloader and installed a custom recovery (Advance Stock Kernel with Recovery v11 (FW:*10.4.B.0.569}*) from this this thread, linked from [HOW TO] Root 10.4.B.0.569 [ONLY UNLOCKED BOOTLOADER]
In doing this the phone was reset to defaults, but it made no difference to the Dev Options being disabled. I can get into it, but most options are still greyed out, so still no adb
So now I am stuck. With no screen, I have no idea what steps to take to flash the SuperSU zip file from recovery. This is where I need some help
I have no problem wiping the phone, installing custom roms etc. but I need to get root and adb working somehow.
Is there any reason why USB debugging, amongst others, in Developer Options might be disabled?
Possibly a permissions problem? Fixable without root?
Could someone running the same recovery possibly detail the steps needed using the hardware buttons (up, up, power, down, power, etc) to flash supersu so I can get root?
Assume blank external sdcard with only that zip on it
Could someone recommend a custom rom that is safe to install on that software version that has root and maybe adb enabled?
Would it be possible to flash that from fastboot?
afaik, only stock/signed roms can be installed that way?
If I got adb working, could I sideload a rom/zip from that recovery or another non-touch recovery(swipe to proceed is definately out)?
Does anyone have any suggestions, ideas or alternative methods to attempt, in order to get control over the device?
thanks in advance to anyone that can help!
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.
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 !