Hello there fellows,
I have an Oppo R1K R8001. It is a Qulacomm Device and does not have and SDCard. I have just updated the phone VIA OTA and the process was completed without any problem.
After my phone is turned one it keeps showing Force Close errors on everyting. com.somethign.phone [close].
I have downloaded the OTA update for this phone but it does not have a SDcard.
Can somebody please help me out on how I can flash this phone?
Thank you
-------------------------------------
I fixed it. Turned off phone. Then plug the USB Cable and phone appeared in ADB mode.
Then I used ADB push method to put the OTA file into the phone and it worked.
Flashed VIA Recovery and it worked.
bump
Related
I tried to flash CM7 RC2 onto my phone last night. I usually do this manually, but last night I did it through Rom Manager which I think was probably my first mistake.
Anyway, the package flashed fine but after a reboot my SIM and SD card were no longer recognised. So I went into recovery (Amonra) and wiped ready to flash the update manually only to find my SD card wasn't recognised: E:Can't mount /dev/block/mmcblk01p (No such file or directory). So, left with a phone with no ROM.
I can still get into recovery and bootloader but that's it. I've seen a few posts on here with regards to USB bricks, but my phone is no longer recognised by adb. However, I haven't accessed the phone via adb for some time now, so not sure of the reason I can't connect is my PC setup or the phone. I've got the HTC Bootloader device appearing when I plug it in via USB though.
Can anyone advise on anything I can do to sort this?
Thanks
Might be a driver issue when your in recovery. Re-install the drivers for the device using Device Manager and point windows to the driver directory within the SDK folder.
Hi,
It happened ~2 months back on upgrade to 4.3 that my PC stops exploring to Galaxy Nexus files storage.
Start getting error - attached the image.
Today I need to fix this asap. adb devices is working.
Tried "Rescan Image", Updated the Samsung Driver 1.5.14.0 but still no way.
So what can be the issue and what are the steps?
Please lead me to correct steps to perform if published.
Try another usb data cable.
.
My device was rooted with the old method and I accidentally did an OTA update, so it's bricked right now.
I've tried to flash the pre-rooted system image, but I can't do that if my phone doesn't show up on fastboot, adb or device manager. I've tried connecting to every USB port, in the bootloader, the recovery as well as the normal boot screen (which the phone can't get past).
I've also tried installing the Intel Android drivers through the .exe file, I would do it manually but I don't think I can do that unless Device Manager detects my phone in the first place.
Is there something I'm missing here?
aloy99 said:
My device was rooted with the old method and I accidentally did an OTA update, so it's bricked right now.
I've tried to flash the pre-rooted system image, but I can't do that if my phone doesn't show up on fastboot, adb or device manager. I've tried connecting to every USB port, in the bootloader, the recovery as well as the normal boot screen (which the phone can't get past).
I've also tried installing the Intel Android drivers through the .exe file, I would do it manually but I don't think I can do that unless Device Manager detects my phone in the first place.
Is there something I'm missing here?
Click to expand...
Click to collapse
i'm not sure this link can help you but better trying than do nothing, hope our phone back to normal again
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I can't update my OP3. The device is on Open beta 16. When updating through settings, the update downloads and then it shows a restarting dialog box that does nothing. The only way to get rid of it is to restart the phone(which leads to an update failed notification). I tried updating via adb sideload but it isn't detected on my PC even though I have the drivers(neither is fastboot detected). I also tried to update via adb with the file on the system but it just says update failed. The phone is completely functional in all other ways and I haven't faced the issue while updating previously.
TL;DR : OTA update gets stuck on restarting and can't detect the phone in ADB/Fastboot but rest of the phone is completely functional
My problem started when I attempted to bypass the FRP by flashing a custom TOT file. I neglected to notice the file was specified for a 32GB version. I flashed it on a 16GB version using LGUpgrade Tool. The phone then froze at the splash page that just says "Google" . I thought I was fortunate enough to be able boot to recovery mode and so I flashed the stock firmware through ADB - the same ROM version that was previously on my phone and from a copy which I had used in the past with no problems. Everything seemed to be working again except my PC doesn't detect the USB connection anymore. I've tried the same procedure but now the command 'adb devices' doesn't list the phone. However, there is a point when I boot to recovery mode the PC makes a sound as if it detects the phone but then moments later it makes the other sound as if it gets disconnected. As I stated earlier, my phone seems to be where I was stuck at FRP with Android version 7.1.2 but my problem now is I can't get the PC to detect the phone when it's plugged into its USB connection. Nothing shows in Windows Explorer as well as Device Manager? I tried re-installing the drivers. Stopping and restarting the ADB server... still no detection. Is there a way to set USB mode to MTC while in FRP mode? Should it matter in Recovery Mode?
I'm going to wait for a response before I attempt to flash again but this time through the SD card because this will be a first time for me using that method and I hope there's a less risky solution.