Develop Bugs

[Tutorial] Rooting Your Device in Linux

Root Galaxy Nexus (Either GSM or LTE) in Linux (Personally in Ubuntu)
Disclaimer: I am not at fault for anything you have done to your phone (ie. Brick, break, etc.). You are doing this at your own discression. I am merely stating what I did to unlock/root my phone.
Tutorial Broken Down Into Three Sections
I. Unlocking the bootloader
II. Installing Clockwork Mod Recovery
III. Installing SuperUser
Resources
1. Super User (used by flashing in Clockwork): http://download.clockworkmod.com/test/su.zip
You can get the latest version here: SuperUser by ChainsDD
2. Clockwork – based by carrier
1. Verizon (CDMA) version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.4-toro.img
MD5:*b2d31c29b7ef785f9c0802a12264d322
File size:*5,263,360*(bytes)​
2. GSM version: CMW Galaxy Nexus
File name:*recovery-clockwork-5.5.0.2-maguro.img
MD5:*445887336a863573997ccbaeedddc984
File size:*5,427,200*(bytes)​
Unlocking Bootloader
Part 1: Unlock
1. First off, you need to download the adb drivers. There have been mentions of just getting the drivers, but I actually have the entire SDK. You can download it here. http://developer.android.com/sdk/index.html
2. Plug in your device, then open up Terminal (Ctrl + Alt + T) and type in: “lsusb” (without quotes). This will pull up all the devices plugged into your usb slots. Look for the one that says samsung (others have found google, but please make note).
3. Find the device, then find where it says ID. After where it says ID, it should have a number/letter mix such as “04e8” or such. Make note of that for later.
4. Go to http://developer.android.com/guide/developing/device.html . This will give the instructions on how to Install the device drivers (specific to each manufacturer). Start from where it says “4. Set up your system to detect your device.”
5. Go to your internal and cd to platform-tools. (This should include both adb and fastboot.) Put your phone into fast boot. (Do this by holding the power, volume up, and volume down buttons while phone is off).
6. Once in fastboot, go back to your computer and type in “sudo fastboot oem unlock”. This will bring up the option to unlock your phone's bootloader on your device's screen. It will give you a disclaimer, and it will say that if you unlock, it will wipe all of your phone's data. Scroll to Yes using the vol up or vol down buttons, and select it with the power button.
7. If you boot straight from there, you will go through a series of boot loops (it was 2 for me) then will be prompted to go through the process of setting up your Google account again. again.​
Congratulations, your phone is now unlocked. However, this doesn't mean that you have rooted your phone.
Rooting
Part 2: Putting Clockwork Mod Recovery On Your Phone
(do step one for preparation of Part 3)
1. First, we will want to push su.zip to your phone's Internal storage or “sdcard” partition. Open up Terminal and type the command “adb push 'directory_of_su.zip'/su.zip /sdcard/”. Hit enter/return and it should transfer over. (Based on the quality of usb cord, times of transfer may vary.)
To make this easier, put su.zip into the directory of adb. Then all you have to use for the command is “adb push su.zip /sdcard/”.​EDIT:
After you root, you have to delete /system/recovery-from-boot.p and reflash or else every time you reboot, the recovery partition will be written over by android. This can either be done in terminal (phone or comp) or by a file manager with root access (such as Root Explorer).
Reference: http://forum.xda-developers.com/showthread.php?t=1392336
Thanks vihil
2. Put your phone in fastboot mode again (vol up + vol down + power)
3. Go back to Terminal and type in “fastboot flash recovery 'whatever the file name is'”. This will flash CWM (Clockwork Mod) onto your phone, deleting your phone's stock recovery image.
EDIT: If it doesn't work, i.e. due to permissions, run with sudo​
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.​
Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Special Thanks to scary alien on androidforums.com and jcarrz1 on XDA

Reserved
Reserved......

Thanks a lot I was looking for exactly this. Appreciated. Will try in a few hours when I get my phone.

Downloaded the sdk file but have no idea what to do. My windows computer died and it would be a lot easier on that to do all this but all I have is a computer with linux currently so if anyone would be kind enough to tell me how to install sdk I'd appreciate it. I seen the read me and seen it says execute "android" first but I don't know how to do that. I realize this is incredibly annoying to the xda hive mind trust me I hate needing help like this I'm nothing close to a noob as far as rooting flashing and all that good stuff I'm just unfortunately stuck with only Linux. I'd really really appreciate it.

under the tools folder there is a script called android, u can either run it in a terminal or hopefully if u were to click it, it was ask if u want to run it!

If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.

Seems like my fastboot is stuck on `waiting for device`. I have the fastboot screen on my GN.
Before rebooting into fastboot `adb devices` successfully showed a device (i.e., usb debugging is enabled, dunno whether it is needed for the unlocking):
$ fastboot oem unlock
< waiting for device >
Any idea?
EDIT: Found the solution. After doing a `fastboot devices` it told me "no permissions fastboot" so I needed to be root on my computer for it to work.

FadedLite said:
If you want to run it, you can just cd to it in terminal, then do "./android" and that should do the trick.
./ is the way you execute scripts in linux.
Click to expand...
Click to collapse
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.

C-4Nati said:
Thank you! That worked correctly and installed it. Now the next step to check the usb and if its there does not work, I might be entering this incorrectly but I typed just lsusb and enter nothing happened, held down ctrl, alt, t then typed in lsusb and nothing happened then just copied that entire part encase I was suppose to and got this.
[[email protected] ~]$ (Ctrl, Alt, T): lsusb
bash: syntax error near unexpected token `:'
Like I said I'm not expecting help because I know XDA doesn't like noobie questions, I will be greatly appreciative if you have patience with me and will even be willing to donate once I unlock the BL and root it. Thank you again.
Click to expand...
Click to collapse
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system

For simplicity, you can shorten that to: mount -o rw,remount /system
You can also delete it from a terminal on the phone or any file manager that allows root access. I think the free ES file explorer has root options.

vihil said:
You don't really need that step. Since '04e8' is Samsung and you have a Samsung device it will likely always be 04e8.
Part 1, 3. and 4. can be summarized as following:
Put the following line into /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Execute: chmod a+r /etc/udev/rules.d/51-android.rules
Type the following to verify it is working: "adb devices" It should display something like:
List of devices attached
01492B093401000F device
Part 1, 6. should probably changed to "sudo fastboot oem unlock"
Also, Part 2, 1. the preparation makes no sense to me: "(do step one for preparation of Part 3)". How can I go into Clockwork recovery before completing Part 2? Since Part 2 is about installing Clockwork...
Edit: And I just realised, C-4Nati, you should not write the "(Ctrl, Alt, T):" out.. that's just a shortcut to open a terminal. Just "lsusb" is fine. Then it should work.
---------- Post added at 11:33 AM ---------- Previous post was at 11:09 AM ----------
For anyone wondering why the step by step instructions in the OP do not work:
You need to flash the Clockwork recovery and install su.zip before you can remove the /system/recovery-from-boot.p (and if you follow that link provided it will cost you around $3.50 but you should be able to do it manually, will try to figure it out).
---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------
(I couldn't find the /system/recovery-from-boot.p on my GN filesystem but maybe someone else does)
To remove /system/recovery-from-boot.p:
$ adb shell
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
# rm /system/recovery-from-boot.p
# mount -o ro,remount -t ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
Click to expand...
Click to collapse
for needing to type in lsusb, i found that as somewhat of a precaution. I had seen on other threads that others had their device show up as either google or samsung. So i just figured rather check first instead of installing both or something.
for the preparation, basically you do that since your phone is already on. after flashing cwm, you would have to boot back into your phone, push the file to your sdcard, then boot back into recovery. All it does is that it saves just a bit of time.
As for the sudo fastboot, I didn't actually have to do that, but i'll add it, Thanks.
As for the cwm terminal commands, i'll add that as well. Thanks again.

FadedLite said:
Part 3: Flashing Super User onto your phone.
1. Next, go into Clockwork by hitting the volume up or down buttons till you see recovery mode. Hit the power button to enter Clockwork.
2. Scroll down (using volume buttons) till you get to “install zip from sd card”. Use the power button to select it.
3. Scroll down to “su.zip” and select it. Then, hit the selection for installing the zip file.
4. Go back using the “Go Back” selection to return to the main screen.
5. Reboot the system using the “reboot system”.​Congratulations! You now have Root access!!!
Have fun with Flashing ROMs!
Click to expand...
Click to collapse
not yet. after flashing su-bin-3.0.3.2-efghi-signed.zip (which is just the binary), the user still needs to flash Superuser-3.0.7-efghi-signed.zip, to have Superuser.apk placed in /system/app, otherwise GUI apps won't have access to su. (unless, of course, the zip you are linking here has them both)
It's preferable to have users linked to ChainsDD website, there people will find latest binaries and Superuser.apk. I also don't see any mention to him in the OP. Even if this is a tutorial, don't forget to give credit where needed.

Some help for an Ubuntu Noob/Not a Noob to Windows
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar

jmartino5920 said:
Hi all,
Long story short, I no longer have Windows (nor a way to load Windows without a purchase; I'd rather not). So I have a fresh install of Ubuntu Linux 11.10. I have read this guide and some of the helpful responses and have yet to be able to get adb and fastboot up and running. I am beginning to understand the nuances of Ubuntu and have tackled adb and fastboot in Windows but Ubuntu is different. I would say I have put in two 12 hour sessions with no desire to pack it in and go back to Windows (I am avoiding a VM as well).
Here is where I seem to be stuck (mind you I have done a fresh install numerous times to start with a fresh playing field in case I have messed up something): Whether downloading the full SDK through Eclipse (cos I'd like to dev apps soon and why not have it?) or downloading the SDK on its own, I get it without fail. The steps leading up to entering in commands for terminal so that the computer recognizes either just my Nexus or a slew of OEMs are easy enough but maybe I am messing up. It is where getting the computer to see my device (udev steps) I can't seem to get it right. I have even looked at other guides for reference (most seem messy and convoluted) but keep coming back here.
I know you probably need more to go on and I am sooooooo willing to tell more. I just hope someone is down to help a brother out. Like I said, I just need some direction. I have manually rooted and all that jazz, just in windows. Thanks in advance for your help.
jmar
Click to expand...
Click to collapse
Are you getting a "waiting on device" message or something similar when you run adb or fastboot?
Forget about the udev nonsense (not important really until you start developing full time) and just drop a sudo before your commands.
You can shoot me a PM or a gtalk (same username as my xda) if you want and I'd be more than happy to help you get your system going.

Thanks, still a bit more annoying that Windows but this tutorial makes it easy.

Sorry if this is ignorant, but can I use these instructions with Unix & terminal on Mac OS X? I'm thinking yes???

I rooted mine in linux as well... No problems. For some reason I was able to do it much easier though...
I did the fastboot oem unlock step above (Part 1). Rebooted then installed superuser from the android market. Then I installed Clockworkmod from the android market.
Done.
Not sure if I'm missing out on something by doing it this way but so far I've had no issues....

Cracked Screen.

Ok long story short i was getting the Power button mishaps. So i banged my phone to fix it worked great a few times but last night while doing so i cracked my screen Stupid move ever lol. KIDS DONT TRY IT !!!!
Its all black now and i want to be able to retrieve my pics on the phone.Cause when i connect it to my PC it does nothing just charge.
How can i so since i cant see nothing?

Broken screen
Colombia81er said:
Ok long story short i was getting the Power button mishaps. So i banged my phone to fix it worked great a few times but last night while doing so i cracked my screen Stupid move ever lol. KIDS DONT TRY IT !!!!
Its all black now and i want to be able to retrieve my pics on the phone.Cause when i connect it to my PC it does nothing just charge.
How can i so since i cant see nothing?
Click to expand...
Click to collapse
Did you save your photo's on your internal storage or on an external SD? If you saved them externally you can put your Micro SD in a flash drive and pull it up that way.

Or if for some reason you do not have access to an sdcard adapter you could use adb and pull them from the phone from a terminal.
Sent from my SGH-T989 using xda premium

bseager said:
Did you save your photo's on your internal storage or on an external SD? If you saved them externally you can put your Micro SD in a flash drive and pull it up that way.
Click to expand...
Click to collapse
codecaine21 said:
Or if for some reason you do not have access to an sdcard adapter you could use adb and pull them from the phone from a terminal.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Most of the are on my internal SD ... How would i go using ADB method ?

Colombia81er said:
Most of the are on my internal SD ... How would i go using ADB method ?
Click to expand...
Click to collapse
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
This will pull all files ending with the jpg extensions. You can of course pull whole folders.
I just wrote that off the top of my head and it wasnt tested. I have to get to bed. I have to get up at 4:30am for work and it is now 11:30. Damn computer is so addicting! The one liner might not work but you get the point. Google adb pull and adb push.

codecaine21 said:
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
This will pull all files ending with the jpg extensions. You can of course pull whole folders.
I just wrote that off the top of my head and it wasnt tested. I have to get to bed. I have to get up at 4:30am for work and it is now 11:30. Damn computer is so addicting! The one liner might not work but you get the point. Google adb pull and adb push.
Click to expand...
Click to collapse
Thanks the issue will be to see if im on recovery mode since i cant see nothing

Colombia81er said:
Thanks the issue will be to see if im on recovery mode since i cant see nothing
Click to expand...
Click to collapse
A friend had the same issue a few weeks ago and I just popped her battery out and popped it back in. Then held the power + vol up + vol down till i felt vibration and held on for another 2 seconds. Then waited 20 seconds just to be safe. I connected my phone. I ran sudo adb devices in a terminal to make sure it was connected. Which is was and then ran the necessary commands.
Sent from my SGH-T989 using xda premium

codecaine21 said:
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
Click to expand...
Click to collapse
Yeah that didnt work its in recovery now. Im trying to figure this out i just dont want to d/l the pics. I dont mind backing up the whole entire thing. How would i go on doing that.

Colombia81er said:
Yeah that didnt work its in recovery now. Im trying to figure this out i just dont want to d/l the pics. I dont mind backing up the whole entire thing. How would i go on doing that.
Click to expand...
Click to collapse
That's a tough one... for me at least. I mean you are able to reboot into recovery but I am unaware of a method that will allow you to back your system up from a terminal. Adb has a backup command but you need to be able to see your screen to use it.
You could use the dd command over ssh ->
Code:
[B]sudo adb shell dd if=/dev/block/mmcblk0 | sudo ssh [email protected] "dd of=/~/Documents/recovery.img"[/B]
and check the progress with
Code:
[B]while true; do readarray -t array < <(pgrep -l '^dd$'); var=$(echo "${array[@]}" | sed 's/ dd//g'); kill -USR1 $var &>1 && sleep 5; done[/B]
but I "think" the FAT32 FS is limited to 4GB file transfers. So you will receive an error after 4GB's and the transfer will abort. Also, I am unsure of the t989's pit layout. Which blks you would need to backup if you did decide to dd single partitions. Like cache, system, recovery, boot, etc.
Maybe some computer whiz will be able to help you. I am sorry I couldn't help. Maybe one of the more experienced Linux/android users/devs can help you if you haven't already figured this out.
If someone did know, it would be cool if you could post the solution. I am curious as how to one would go about doing this.
Sent from my SGH-T989 using xda premium

codecaine21 said:
Reboot into recovery(Not download mode). open a terminal and use adb's pull command. You could use adb's pull command in conjunction with the find command. Something like
Code:
adb shell find / -name "*.jpg" -exec adb pull {} ~/Documents +
Click to expand...
Click to collapse
Im hoping you are still around for some more assistance. Im actually in the middle of the same issue as OP, except possibly that the phone was completely stock with android debugging disabled, and the touch interface is also non-functional. You'd think that would be great for getting stuff off the phone, but I was unable to use the on screen menu to actually turn on usb mass storage.
I decided to try and use push / pull from recovery, however I found out that the directories I want arent available in recovery mode (DCIM / Download with a very very important 0000001.vcf in it).
I was able to get into recovery and use "adb reboot download" and Odin'd "recovery-cmw-hercules.tar" to the phone to give me a working CMR environment (v5.0.2.6). I thought I could feel my way through the menus after another "adb reboot recovery" to blindly guess - Vol Down x 6, Pwr x 1, Vol Up x 2, Pwr x1 - type thing, to navigate"mounts and storage" and then find "mount sdcard".
However, I have been unsuccessful. I did manage to mount system / data / cache , just not sdcard, and I dont know why.
TLR No screen, no touch. Odin'd CMR. Am sitting in Command Prompt with ADB Shell / Pull working. Still can't access ~/DCIM folder on internal SDCard. Hoping for some help. What am I missing? Bonus: A screen shot of the CWR mounts and storage menu would be very helpful!

Ok so i got it....
So I first used this comand:
Code:
adb shell find / -name "*jpeg"
It gave me this
/sdcard/Download/155546_394801767258170_1181721421_n.jpeg
Then i used this command to pull everything from my internal sd-card
Code:
adb pull sdcard C:/Docs
Worked like a Charm

[GUIDE] Authorize adb with broken digitizer.

So, yesterday my brothers Pit bull, Maggie, knocked my GS3 out of my hand and onto the cement driveway...
The result? A shattered screen, cracked display, and broken digitizer.
I wanted to perform a backup of my current rom (CM11 Latest Nightly) but figured out that my computer was not authorized for ADB.
Well, I wasn't about to let that stop me. Here is what I did to fix that little problem.
The following guide assumes that you already have the drivers for your phone installed and also that you have ADB set up.
I have only tested this on TWRP 2.7.1.0. I do not know if it will work on other recoveries.
First things first, power off your device by doing a battery pull.
This is the best way to ensure you are fully powered down since you can't see the screen.
Next, boot your device into recovery by pressing and holding the power, home, and volume up buttons.
Once you feel the device vibrate, release the buttons.
Plug in your phone and pull up a command prompt window.
Check and see if the device is being recognized by running
Code:
adb devices
.
Connect to the device by running
Code:
adb shell
.
Next, to mount the data partition where the files we need to edit are located, run the following code.
Code:
mount -t ext4 /dev/block/mmcblk0p15 /data
It is very important you type this exactly as written. Double check a few times to be sure.
Exit the shell by typing
Code:
exit
Now, we need to find our computer's adb key. For me, it was located in "C:\Users\%Username%\.Android\".
The file we are looking for is adbkey.pub.
Push this file to your device using
Code:
adb push adbkey.pub /sdcard/adbkey.pub
Pull up another shell by typing
Code:
adb shell
Remove the current adb key by typing
Code:
rm /data/misc/adb/adb_key
Insert the key into your phone's authorized keys by typing
Code:
cat /sdcard/adbkey.pub >> /data/misc/adb/adb_keys
Exit the shell
Reboot your device with
Code:
adb reboot
Profit! :good:

Hey buddy! Great tutorial! However, I'm getting an error trying to mount mmcblk0p15. I get the error:
"mount: mounting /dev/block/mmcblk0p15 on /data failed: Invalid argument"
Do i need super user privilege do to this?
Thanks! Great tutorial, btw.

Broken Display

Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?

fxppas said:
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
Click to expand...
Click to collapse
send it back and pay money for repair or you can buy yourself a new display + digitizer
for the glass oneplus take ~100 dollar. someone in this forum had the same problem.
you can ask the support first

Without debugging and with encryption you really can't do much ...
Sent from my OnePlus 3 using Tapatalk

@panther124
I just want to have my data back.. I dont really want to fix it. The mobile phone is slightly bended and has tons of scratches on the backside and a big bump. If you see the phone you will be surprised that it is still working As far as I understand is the data lost if I send the phone back.
Isnt it possible to connect just another cheap display on the phone to just for passing the lock. So I can enable debugging.

fxppas said:
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
Click to expand...
Click to collapse
Hi
did you unlock the bootloader?
maybe you could still root it and adp push / pull stuff from it

AlexLebowski said:
Hi
did you unlock the bootloader?
maybe you could still root it and adp push / pull stuff from it
Click to expand...
Click to collapse
I can enter shell with adb if I use power+vol up to boot into bootloader. But I dont know where my files are. "/sdcard" /media / mnt" I dont find anything.

fxppas said:
I can enter shell with adb if I use power+vol up to boot into bootloader. But I dont know where my files are. "/sdcard" /media / mnt" I dont find anything.
Click to expand...
Click to collapse
try look into "/storage" or "/data", or any other directories, use "adb pull" to copy everything you can to your computer.

Internal storage is at /storage/emulated/0
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Internal storage is at /storage/emulated/0
Click to expand...
Click to collapse
[email protected] ~/on3bu $ sudo adb shell
[email protected]:/ $ cd /storage/
[email protected]:/storage $ ls
sdcard0
[email protected]:/storage $ ls -l sdcard0
lrwxrwxrwx root root 1970-04-23 10:16 sdcard0 -> /sdcard
[email protected]:/storage $ exit
[email protected] ~/on3bu $ sudo adb pull /storage/sdcard0
failed to copy '/storage/sdcard0' to './sdcard0': No such file or directory
[email protected] ~/on3bu $ sudo adb pull /sdcard
failed to copy '/sdcard' to './sdcard': No such file or directory
[email protected] ~/on3bu $ sudo adb shell
[email protected]:/ $ ls /storage/
sdcard0
[email protected]:/ $
Not with my phone

Hey, sorry for the late reply, i've been sick the last day.
First of all a stupid question
Have you seen that all your data is there under /storage/sdcard0? or is it an empty folder
try specifying the output directory of adb pull like
Code:
adb pull /storage/sdcard0 /home/username/
I'm thinking maybe it's a linux related problem, since linux doesnt always automatically create folder structures. So if your error message changes keep me posted.
Also:
my data is directly under /sdcard
so if i
Code:
adb pull /sdcard
I get
Code:
pull: building file list...
pull: /sdcard/ViPER4Android/DDC/Custom_jmxc23.vdc -> ./ViPER4Android/DDC/Custom_jmxc23.vdc
and Last but not least
maybe the sdcard isn't mounted correctly...
try
Code:
mount -a
in adb shell and leaye the shell open, then open a new one and try pulling the stuff from it.
I'm also new to XDA so until now i only had to solve my own problems but maybe it helps just give it a try
I'm also not shure if your pattern lock has encrypting your data (/sdcard).
but there is also a solution for removing lockscreen patterns via adb shell.
Good Luck,
Alex

Stuck in bootloop but has very important files.

The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.

Z91 said:
The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Click to expand...
Click to collapse
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?

sharjeel.019 said:
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
Click to expand...
Click to collapse
I can get into recovery but adb only works in sideload so I can't do stuff like adb pull, etc.

If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery

TheFixItMan said:
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
Click to expand...
Click to collapse
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?

Z91 said:
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Click to expand...
Click to collapse
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero

TheFixItMan said:
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
Click to expand...
Click to collapse
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?

Z91 said:
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Click to expand...
Click to collapse
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)

TheFixItMan said:
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
Click to expand...
Click to collapse
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.

Z91 said:
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Click to expand...
Click to collapse
If your phone doesn't reach the stage where adb is enabled there's nothing you can do