I forgot my pattern lock and am trying to factory reset using sony companion. No matter what I do it starts reinstalling then fails with the message: Software update failed An error occurred while repairing your device.Please try again. If the problem persists, please contact Sony support.
UEUpdateFailedUE_2002.8.3.0 / Windows 10 64 bit / Win32 / US
Drivers show SOMC Flash Device in devices manager. Also Com port shows as well. I have tried a couple different computers including mac with same results. I was able to enter fastboot and get it detected but get error denied on most commands mainly fastboot format userdata and reboot recovery. I know my google info but am unable to factory reset to get that option.
Thanks for your time and thanks to all the volunteers that make this forum such a great resource.
Related
Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
I have a HTC Google Nexus 9 tablet. I recently received the update to Android 6.0.1 via the normal push notification. The update got stuck on ‘optimizing your apps 1 of 74’. It normally moves up in the numbers within minutes but it remained on ‘1 of 74’ for an entire night. So, the next morning I switched off by holding the power button.
The system still booted but soon enough I received error messages like ‘there is an internal error, contact the manufacturer’ and during the boot it says that my system was corrupted.
I decided on a factory reset. It went through with it. But when setting up the cleaned system, there is another problem: I can pick my language and connect to my WIFi without problem. But then it goes to a screen where it says ‘checking connection. This may take a while.’ It gets stuck there for several hours - so it is clearly faulty as I don’t think ‘a while’ means 12 hours and more. I also don’t think that the factory reset solved the problem anyway as I still receive error messages, hinting at a corrupted system, during and after the boot.
So, I decided to try to flash a system image.
I got the Minimal Android Debugging Bridge ADB and Fastboot on Windows 7 and Ubuntu,
Then I followed the Google developers instructions and downloaded Volantis MOB30D from there.
I also got Android drivers for Windows, but I’m not entirely certain if they are right.
When I connect the Nexus 9 to the Windows computer, I now see in Device manager: ASUS Android Devices -> Android ADB Interface
It’s not an ASUS tablet though and I can’t see the Nexus 9 in ‘Computer’ (it used to show up there as ‘Portable Media player’
Is it possible that I got the wronger drivers and if so, how would I install the correct ones?
Then I start the Nexus 9 and hold power and volume up down to get to the bootloader.
It says ‘Fastboot USB’
I also says ‘device state - locked’ . I can’t get to the system settings to do the OEM unlock as I’m stuck on ‘checking connection’ when I boot normally.
Then I opened ‘Minimal ADB and Fastboot’ on Windows and tried the following commands:
Fastboot flashing unlock
… and it says:
FAILED (remote not allowed)
Then …
Fastboot oem unlock
… and it says:
(bootloader) ability is 0
(bootloader) permission denied for this command
Then I tried the same on Ubuntu. The device doesn’t show in the left hand side panel. When I try the above commands it just says
waiting for device
So, I guess Ubuntu doesn’t even recognize the Nexus 9
I then opened ‘Additional Drivers’ but it just says searching for available drivers and then no proprietary drivers are in use on this system
Any advice for Nexus 9 drivers on Ubuntu?
I also tried from the bootloader: Hboot → Recovery → Apply update from ADB
In Ubuntu I went to the directory where the ZIp file of the system image is located
Then I typed in the terminal:
adb sideload image-volantis-mob30d.zip
And it says …
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
1. You don't have correct drivers for Nexus 9. The Nexus Root Toolkit has a driver instillation guide.
2. You can not sideload factory images.
Try sideloading the failed ota available here
Code:
April 2016 Nexus OTA Updates - Security Level 2016-04-02
Nexus 9 (LTE) [URL="https://android.googleapis.com/packages/ota/google_flounderlte_volantisg/9ae7d85d6433d055a9e4f3049ac86eb0e562bbf1.signed-signed-volantisg-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
Nexus 9 (Wi-Fi) [URL="https://android.googleapis.com/packages/ota/google_flounder_volantis/6a2119f2077022c1ba852f2c613b8ce942c33836.signed-signed-volantis-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
If that doesn't work try sideloading Android N OTA
aeglyss said:
Any advice for Nexus 9 drivers on Ubuntu?
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
Click to expand...
Click to collapse
I don't know specifically about Ubuntu, but I've done several updates to usb-connected android devices using Debian linux, and I've never needed to add a device-specific driver.
Some additional ideas on the permissions:
(1) Did you enable "USB Debugging" in Settings->Developer Options?
(2) From your Linux machine, did you try to run adb as the root user or use sudo? I have to do this for both adb and fastboot. (Example command line: '$sudo adb devices', without the quotes.)
(3) Finally on the Linux side, did you try to connect first via adb? And, if so, did you look on your Nexus for an "Enable..." approval notification?
Good luck!
cheers,
john
Thanks everyone. I managed to fix it
aeglyss said:
Thanks everyone. I managed to fix it
Click to expand...
Click to collapse
Hi, I am at a similar point, my Google Nexus 9 failed doing the update, I then tried to factory re-set it and now it is trying to check connections...
I have downloaded the bootloader and my Windws 10 pc can see the tablet via explorer. I believe I have also switched the tablet to Fastboot but bootloader doesn't sem to be able to make the connection.
I was wondering if you are able to provide me with instruction as to how to rescue this tablet. I am not an expert, so I would appreciate any instructions to be as simple as possible.
Thank you for your help,
Mike
Hi I have moto G 2015 osprey XT1541, its unlocked running cyanogenmod
I recently upgraded to CM 14 experienced problems instantly, all the google apps wpuld crash.
Reverted back to CM 12 which worked and it had an error whilst upgrading in recovery,
something like
E:Failed to map file
E:Error exit from the fuse process :0
Installation Failed Installation Aborted
I have tried multiple roms, all come back with same error message. The recovery on the phone is the cyanogenmod one. Also in recovery if I do system reset I get
E: Failed to mount /data (permission denied)
I am having to try installing roms via sdcard as the phone is not recognised by my computer.
Any Ideas?
I would format userdata in bootloader then install TWRP and use that to install the next rom.
es0tericcha0s said:
I would format userdata in bootloader then install TWRP and use that to install the next rom.
Click to expand...
Click to collapse
How do I format userdata? I dont have that option in the bootloader. When I try to install anything using cyanogemod recovery including TWRP I get the same error message.
fastboot format userdata
fastboot format cache
If that doesn't work then you'll want to go back to complete stock with the original firmware for your variant (and carrier if yours came from one originally).
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
AndyGLowe said:
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
Click to expand...
Click to collapse
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
es0tericcha0s said:
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
Click to expand...
Click to collapse
I doesn't even show in Device Manager, I have tried another system with Win 7 on and that comes up with a notification saying a unrecognised device has been attached. But it doesn't make a difference if you install the drivers or look in device manager, had exclamation mark next to device but you cant do anything. I also have Ubuntu dual loaded on this system and that doesn't recognise it either.
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
sahil soni said:
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
Click to expand...
Click to collapse
did you guys solve your problem I have the same exact issues?
Hey guys
Recently I updated my phone(huawei mate 9 pro, Lon-L29) to the latest android version 9 and after the update the phone rebooted twice and it didnt skip that, it stuck on the eRecovery screen with 4 options:
scan wifi and upgrade
wipe data/factory reset
reboot
shutdown
I tried the first option several times with no success, I've got "Getting package info failed"
I tried Vol+power to wipe cache and reboot with no results
I tried to update it again by connecting it to my pc and pressing on vol+ and vol- and power and it showed me the updating screen and it stuck on 5% for 3 min and rebooted again to the 4 options.
I tried dload method with external usb because there is no sd card in mate 9 pro, nothiiiing.
I tried Minimal ADB and Fastboot, Huawei FRP Tool, to unlock bootloader/ frp, nothing!
I tried DC_Phoenix_v69 and HCU client, HCU showed " device not found" , "its not support chipset" , I tried to update it by Phoenix and it showed that huawei didnt accept all the files in update .app, exACKAGE_TYPE
but when I put another update .app it accepted PACKAGE_TYPE in it but not the other parts and in each one it gave me that my phone security is not supported by Phoenix!
In one of the files(update .app) that I tried the phone screen turned off and didnt come back again, I tried to open HiSuite to recover the phone and it showed that it stuck on fastboot, I tried to exit from fastboot by Minimal ADB and Fastboot and Huawei FRP Tool with no results!
I tried to exit from fastboot by Minimal ADB and Fastboot and Huawei FRP Tool with no results! My phone is dead(black screen) now and I didnt backup my files,
I tried chimera but it showed an error "failed to read the file" and the phone is in fastboot!
My phone is dead now and I didnt backup my files, so sad
Any help?
Im using Ubuntu 18.04.3. All was fine until the point it said success. Ive then unplugged the phone to see if it boots and it didnt respond to the power button until several minutes later. Now it does attempt to boot but ive left it for like 15 minutes and nothing - stuck on the xperia animation. Ive attempted to reboot into win10 and use the companion app to fix my phone but it says that the bootloader is unlocked.
Ive considered using fastboot to flash TWRP or relocking the bootloader and move from there, but literally every command i give it returns 'FAILED (command write failed (Success))'
Attempts to use windows to do that also went nowhere: Im unable to install the drivers. Ive downloaded the sdk studio, installed the google drivers plugin, located the folder with them, but when i connect my device it doesnt show in the device manager. If i connect it in fastboot mode, it shows as 'Android', but windows refuses to install the drivers claiming that they are incompatible.
EDIT: nvm, managed to install the drivers on windows, sucessfully flash TWRP and fix it from there
I guess a lesson was learned today: dont use linux for this kind of stuff