Last week, while updating my phone, something went wrong resulting in my phone not booting properly. When turning on the phone it got stuck on the OPO logo. Thus, I first tried to wipe cache, didn't work. Then I tried something else and accidentally deleted the "system" data. I was now looking for a way to put the OS back on my phone with terminal (I work on Mac). The problem is that my computer doesn't detect my phone (when typing "adb devices"), and I think it is because the ADB-debugging box in the developer tools isn't checked on my phone. The problem is that I cannot check that box because I can't boot my system.
Who has a suggesting for what to do?
Thanks in advance,
Gijs
There is a thing like ADB called Fastboot mode. Look up how to boot your oneplus into fastboot mode (it's just a key combo) and then you can do things that you could on ADB with fastboot like loading a new ROM.
Related
I've a Honor 10 View Lite with a broken screen (it's not usable) and I would try to recover data from it.
Following some tutorials it seems possibile to do that with ADB and the phone in recovery mode (holding power button + volume up).
I've installed ADB drivers through UniversalAdbDriver.msi and Fastboot version 1.4.3 Portable on Windows 10.
Being the screen black it's difficult to understand if the phone reboot in custom recovery mode or in normal mode, but when I open shell on the same folder of Fastboot and type 'adb devices' no device is found. I've also tried connecting another phone in recovery mode (Huawei Mate 10 Pro perfectly working) but the problem is still the same, no device found.
What can be the problem? Some wrong or missing installations?
I also have to specify that both the phones have USB debugging disabled and I hope this is not a problem because in the broken phone it's impossible to find a way to enable it. That's also the reason why I'm trying to recover data through ADB and not through programs like FoneLab and so on that required USB debugging enabled.
I will also accept advices on solutions different from ADB to recover data in these conditions, if they exists.
Thank you
I don't think adb will work for this unless usb debugging is enabled. At least, the device might show up in "adb devices" list, but it would show up as "unauthorized" and you wouldn't be able to pull data off it.
What kind of data are you trying to retrieve? Don't suppose you have cloud backup?
If it's just the screen that's broken maybe you can find a way to mirror the screen onto an external display somehow.
I had rooted my Yu Yureka plus by unlocking the bootloader using adb fastboot method, then flashing the TWRP recovery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that.
But while playing a game the phone automatically rebooted and ever since have been stuck on "Preparing to start.. Starting apps.."
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls, but can't access anything
Any suggestions what I should do now?
I have tried doing a factory reset from recovery but the problem persists and none of the hardware buttons are working, had to remove battery to access the recovery (still cyanogen recovery is opening).
Please HELP!
you can us this tutorial to get back to stock rom
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Is there an option to remotely unlock the online Android Device Manager's lock feature if I have the password? I do not see an option to do this but have read a couple examples of entering code to do something similar:
Open your terminal and type:
adb shell
Now enter these commands:
su
rm /data/system/cm_gesture.key
reboot
If a lockscreen appears after reboot, it should accept any pattern.
I have read many answers in forums but I do not have my phone, it was stolen and I am desperate. Also, I have the Google Device Manager password I used to lock my Samsung Active S5 after it was stolen. Any help or suggestions would be greatly appreciated.
Try powering it off and powering back up again..
For me the screen for entering passcode came up after rebooting..
I was so scared too, it seems to be a bug..before rebooting I couldn't find anyway to bring up the password screen neither ..
i too had locked my nubia mini device through android device manager.
it can be bypassed by rebooting into recovery mode and you need to format /data and /cache.
after this restart your phone through recovery mode it may take 5 to 10 minutes to finally show "android is updating your apps " something like this.
this method worked on my nubia mini and i thing technically it might work on every android phone that is capable of booting into recovery mode.
this method would not delete your photos,music,etc.
only contacts and app data will be gone,i am sure that won't be an issue.
I tried to flash the Android L Developer Preview(http://developer.android.com/preview/setup-sdk.html) onto my Nexus 5 (no custom ROM or bootloader) following the steps at https://developers.google.com/android/nexus/images. When using flash-all.bat, I ALWAYS get stuck on
erasing 'cache'...
The only thing I can do is reboot the phone by holding down the power button until it is off. Then when I boot again I see the Google logo followed by the green Droid which probably means recovery mode. Sometimes under the Droid there is a blue progress bar, just like the one that comes up when updating, but it does not show a progress but rather just indicates action. When the Droid is up I also cannot reach the phone with fastboot or adb.
I also tried reverting back to Andrid 4.4.4, but I get the same error. Nobody else seems to have this problem, they all erase their cache in a matter of seconds and then format it.
It would be really cool if anybody could help me with either reverting to Android 4.4.4 or successfully flashing Android L.
Benedikt
Is your phone with unlocked bootloader? If no, type in console:
fastboot oem unlock
After that you should to enter in bootloader, open shell and write:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Start "flash-all" script again and enjoy your Nexus.
I have a really serious problem which is preventing me from doing Android development at work, which I have a strong imperative to get fixed as quickly as possible.
So, I plug in my phone to my OS X machine. I go to the terminal and I do this:
rutski#imac:~$ adb devices
List of devices attached
3331833A243A00EC device
Now, that looks good so far. But if I do some work for a few minutes I'll eventually get an error somewhere during "adb install", and when I run "adb devices" again I see that now the device is NO LONGER THERE!
So I unplug the phone, and plug it back in. I run "adb devices" and see the device back again, expect the cycle will repeat, and it will reliably disappear after a few minutes.
But it gets better. DDMS for me is completely unusable. I open up an OS X terminal and run "ddms" from the command line. A window pops open with a device list, and my device is there. However, if I so much as click on my device, it will vanish from the list, and I'll get this in the terminal window:
08:26:05 E/EventLog: device not found
com.android.ddmlib.AdbCommandRejectedException: device not found
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:736)
at com.android.ddmlib.AdbHelper.runLogService(AdbHelper.java:469)
at com.android.ddmlib.AdbHelper.runEventLogService(AdbHelper.java:445)
at com.android.ddmlib.Device.runEventLogService(Device.java:290)
at com.android.ddmuilib.log.event.EventLogPanel$8.run(EventLogPanel.java:454)
Yes, I've made sure that USB debugging is enabled. I've done a start-server kill-server with adb. I've rebooted both the phone and my machine several times. Nothing fixes the problem.
What the heck am I doing wrong here?
EDIT:
I just noticed that after rebooting my machine things are stable until I run an app that crashes via something like calling a method on a null object; that's when the device first vanishes from DDMS, and it is flakey forever after. Still, I'm confused about what to do here. I need to be able to debug crashes, and they will happen.