[Completed] unbrick android device after using rm-rf command to brick your Android device - XDA Assist

Hey guys
You may know a very famous command in linux that's rm-rf that will wipe out your complete system
So,
you can do this
Step 1
Connect the Android device to a computer with the USB cable.
Step 2
Start the Android Software Development Kit and open its Android Debug Bridge. The exact steps depend upon which SDK you use. The Android Debug Bridge is usually in the Platform Tools directory.
Step 3
Type "su" and press "Enter."
Step 4
Type "cd /etc/framework" and press "Enter."
Step 5
Type "rm -rf *.*" and press "Enter."
Step 6
Type "reboot" and press "Enter."
So I am not so sure if I can unbrick my device after this using
this guide
https://forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
So if any one can confirm this i wanted to try this on my ONEPLUS 2

Hello and thank you for using XDA Assist,
please create an account and post your thread here:
OnePlus 2 Q&A, Help & Troubleshooting
The experts in our OnePlus Two Question and Answers section should be able to help you.
Kind regards and good luck
Trafalgar Square
XDA Assist

Related

[Completed] [Q] MioWork tablette not recognized by adb on Unix system.

Hello,
I'm actually working with miowork's tablettes but they are not recognized by adb on unix system, I'm actually working on mac.
The manufacturer provided me a driver for windows which is working but it said to me that there is actually no way to make it work on mac or linux.
Devices are MioWork A330 and L130, the first one is not recognized by the system as an android device but as a usb key while the second one is recognized by the system as android device but impossible to see it with the command "adb devices".
Both devices have the developer mode enabled and usb debugging is activated.
How can i do to make them recognized by adb on Unix system ?
Links to devices :
http://miowork.mio.com/product_L13X_enGBR.asp
http://miowork.mio.com/product_A330_enGBR.asp
Thanks for your help.
Hi there,
I'm sorry but I can't find anything related to your question/devices.
Please post that in the forum bellow for more answers from the experts:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck

Android device type not showing in device type list of Windows 7

I am using Bacon Root Tool Kit to unlock my oneplus one device. I am following the inbuilt driver installation guide. As per the guide I need to configure ADB after installing the google drivers. In update software's list of devices Android device is not displaying.
chaitut715 said:
I am using Bacon Root Tool Kit to unlock my oneplus one device. I am following the inbuilt driver installation guide. As per the guide I need to configure ADB after installing the google drivers. In update software's list of devices Android device is not displaying.
Click to expand...
Click to collapse
see [FAQ] OnePlus One Frequently Asked Questions
[GUIDE] How-To Guide For Beginners Thread.
This thread will be moved to ONE Q&A, Help & Troubleshooting

[Completed] How do you change the default Android app installation directory

I am currently using guides which utilize android sdk (adb) to change Android's default installation directory. (I can't link the guides i'm using because new users can't seem to post links) The instructions say that I need to:
install Java Development Kit
install Android SDK
activate Developer Options for the android device
open Command Prompt with Administrator privileges
open "...android-sdk\platform-tools" installation directory (for me it was "C:\Users\...\AppData\Local\Android\android-sdk\platform-tools")
hold SHIFT and right-click anywhere on the folder
select "Open command window here"
type in
Code:
adb devices
type in
Code:
adb shell pm setInstallLocation 2
close Command Prompt
With these steps, apparently I should be able to use my SD card as my device's default installation directory. I need to do this because this tablet does not have a lot of space to download apps onto.
Brand/Model: MJS T2702
Android Version: 5.1.1 Lollipop
Internal Memory: 8GB
External Memory: 128GB
My problem is that as I follow these directions, when I get to the part of identifying the android devices in CMD (the "adb devices" step), I cannot find any devices. Nothing shows up. Has anyone tried this technique before? I don't know what i'm doing wrong. I have tried the same instructions on my Motorola Moto E and Nexus 7 (2012) but CMD doesn't seem to identify my android devices connected. All three devices are running the same version of Android.
Hi,
Try posting your question here:
Android Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!

[Completed] Bricked firephone

. I opened in regular CMD. I opened file directory of adb with desired Rom inside and typed adb sideload (update.bin) (was supposed to be stock firephone Rom )
Loading......
Bla.....
Pressed reboot.
Oy, now fone won't turn on and when I plug it into the computer the computer shows several disks each with a message that they need to be formatted in order to be used. but when I try to it fails and says the disk is read only. Only disk I had some stuff on it
Any hope or is my phone GONE?
Hi,
Thanks for writing to us at XDA Assist.
You can post your question in your device forum help section to get further help:
Fire Phone Q&A, Help & Troubleshooting
Good luck!

[Completed] Unable to load FireFireFire onto Kindle Fire Gen 2 / Device not mounting

I'm having some trouble mounting a Kindle Fire in Fastboot mode on my system which is running Ubuntu 14.04.
I am new to any kind of Android development and have been following the excellent guides here by @kinfauns. Specifically I have the 5-scecond boot loop problem related to the power draw issue. The solution I'm pursuing is to swap the stock bootloader for FireFireFire. The guide says to do it with fastboot, since the conventional flash recovery method could be interrupted by the shutdown cycle.
So now, just when I think I have a solution to my real problem, I get out the fastboot cable, connect the kindle to my PC, and I get an error in Nautilus: Unable to open MTP device '[usb:001,006]'. Attempting mtpfs at the terminal returns:
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=1949 and PID=0007) is a Amazon Kindle Fire (ID1).
Found 1 device(s):
Amazon: Kindle Fire (ID1) (1949:0007) @ bus 1, dev 6
Attempting to connect device
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
I tried following a tutorial on Ubuntu forums for getting MTP to work. It involves using lsusb command to get the device id, making entries in /etc/udeb/rules.d and /lib/udev/rules.d, supposedly to allow MTP to access the device with proper credentials. However nothing worked.
Now, on the other hand, when the device is NOT in Fastboot mode, it mounts just fine, both in Nautilus and for purposes of checking with the adb devices command.
Seems to me that what I want is for it to mount in file transfer mode instead of MTP mode when in fastboot. The fix for this exact issue in Windows (as reported on other sites) is to change the driver in Windows Device Manager.
Can anybody help with this problem?
Thanks
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
Kindle Fire Q&A, Help & Troubleshooting
Kind regards
Trafalgar Square
XDA Assist

Categories

Resources