[Completed] ADB segmentation fault. - XDA Assist

The screen on my Note 4 is smashed and I'm trying to do a factory reset on my phone using adb with my phone booted to recovery, the phone shows up correctly in windows explorer and I can access the storage just fine, but when I type the command "recovery --wipe_data" in the adb shell, it starts and then gives me a segmentation fault, I've searched the internet and can't seem to find any solution to this. Please can someone assist with this, I thought it would be trivial but it seems far from it!

XDA Visitor said:
The screen on my Note 4 is smashed and I'm trying to do a factory reset on my phone using adb with my phone booted to recovery, the phone shows up correctly in windows explorer and I can access the storage just fine, but when I type the command "recovery --wipe_data" in the adb shell, it starts and then gives me a segmentation fault, I've searched the internet and can't seem to find any solution to this. Please can someone assist with this, I thought it would be trivial but it seems far from it!
Click to expand...
Click to collapse
Hi
Thank you for using xda assist
I would advise you to create an account first and then you can post questions here
http://forum.xda-developers.com/note-4/help/noob-friendly-question-t2866810
for sure experts there can help you on this
thank you.

Related

[Completed] [Q] Interrupted flashing process

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.
Hi,
Thanks for using XDA Assist please post here Android Q&A, Help & Troubleshooting
Good Luck!

[Completed] fastboot will not recognise device (HTC One M7)

I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble. We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the HTC One (M7) at http://forum.xda-developers.com/htc-one which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/htc-one/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.

[Completed] Can't unlock bootloader (iOcean X8 Mini)

Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!
Hello and thank you for using XDA Assist,
please create an account and ask your question in this section. The experts there should know the best about your device.
Kind regards and good luck
Trafalgar Square
XDA Assist

[Completed] LG H650E Zero - device not found in adb tool

HI!
1. I have an LG H650E Zero and i'm trying to control it using adb in order to pull build.props but with no success.
The system display a " Device not found " message. I've tried every kind of LG drivers but the problem's remaining.
2.Another problem is that when i try to use fastboot a "Failed" message is displayed for any offastboot commands. It's important to mention that my device it's recognized by laptop in fastboot mode.
3. Is there any kind of custom bootloader for this device to be installed?
I'd appreciate any of your help! Thank you in advance.
billyjayserres said:
HI!
1. I have an LG H650E Zero and i'm trying to control it using adb in order to pull build.props but with no success.
The system display a " Device not found " message. I've tried every kind of LG drivers but the problem's remaining.
2.Another problem is that when i try to use fastboot a "Failed" message is displayed for any offastboot commands. It's important to mention that my device it's recognized by laptop in fastboot mode.
3. Is there any kind of custom bootloader for this device to be installed?
I'd appreciate any of your help! Thank you in advance.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
Please consider posting your question in this friendly help thread where you'll find expert advice:
http://forum.xda-developers.com/showthread.php?t=2259645
Good luck!

[Completed] T-Mobile lg v20 becomes un-visible when put into bootloader mode.

I can't add any comments on XDA forum where this wuestion belongs because I don't have 10 or more comments posted instructions other than programming and ROMs. however I did post it on the XDA assist forum but i was sent to check out a forum that had nothing to do with my problem. I have the correct drivers I have everything I need to have and as soon as I put my phone into the bootloader mode for some reason the computer cannot recognize it anymore. on the command prompt I type in ADB devices and nothing shows up however, before I put my phone into bootloader mode when I type in ADB devices my phone shows up. apparently this is a phenomenon that only happens to 3% of the people that try to flash this device. I'm not the only one apparently.
Redhat1 said:
I can't add any comments on XDA forum where this wuestion belongs because I don't have 10 or more comments posted instructions other than programming and ROMs. however I did post it on the XDA assist forum but i was sent to check out a forum that had nothing to do with my problem. I have the correct drivers I have everything I need to have and as soon as I put my phone into the bootloader mode for some reason the computer cannot recognize it anymore. on the command prompt I type in ADB devices and nothing shows up however, before I put my phone into bootloader mode when I type in ADB devices my phone shows up. apparently this is a phenomenon that only happens to 3% of the people that try to flash this device. I'm not the only one apparently.
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately it seems you know more about this issue than us, have you tried following this guide
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
when flashing your device to see if it works
Good Luck
Sawdoctor

Categories

Resources