Related
Accidentally broke my G2's screen [blank & unresponsive].
I'm getting a replacement from T-Mo ...but need to extract a some data from the phone's memory.
I've tried connecting it to my computer but I can't access anything unless I put in the Unlock Pattern on my phone (which I obviously can't)
Any suggestion on what I can do?
****Update*****
Screen went out but touch screen functionality remains [Screen Defect?].
I've been able to use ScreenCast to see my screen on my pc & use it to some degree.
Temp. rooted my 'broken' phone with Visionary, ran Titanium Backup ... now trying to do Clockworks Recovery.
...need some help with operating Clockworks w/ a Broken Screen..
More info on second page
If you install adb via the Android SDK, you should be able to extract everything you want.
http://developer.android.com/sdk/index.html
EDIT:
install adb
use adb pull to get what ever data you are looking for, probably something in /data/data/ ??
you can use adb shell to poke around on your phone
I think you might have to be rooted. I don't have an unrooted phone to test this on.
gee one said:
If you install adb via the Android SDK, you should be able to extract everything you want.
http://developer.android.com/sdk/index.html
EDIT:
install adb
use adb pull to get what ever data you are looking for, probably something in /data/data/ ??
you can use adb shell to poke around on your phone
I think you might have to be rooted. I don't have an unrooted phone to test this on.
Click to expand...
Click to collapse
I've had the SDK but I can't access my phone files because they are inaccessible from my PC + my phone doesn't have USB Debugging / ADB enabled by default...
I tried running ScreenCast to try and emulate my screen on my PC (something I've done before) but it wouldn't work because, as before, the phone to be detected as an ADB device
Other suggestions?
If nothing else what's a quick way to wipe all data to factory defaults (without relying on a screen )
SmartHat said:
I've had the SDK but I can't access my phone files because they are inaccessible from my PC + my phone doesn't have USB Debugging / ADB enabled by default...
I tried running ScreenCast to try and emulate my screen on my PC (something I've done before) but it wouldn't work because, as before, the phone to be detected as an ADB device
Other suggestions?
If nothing else what's a quick way to wipe all data to factory defaults (without relying on a screen )
Click to expand...
Click to collapse
If you have Clockwork recovery, you can boot into recovery mode and use adb.
shutdown
unplug the USB and shutdown- press and hold the power button for 2 seconds, scroll down on the trackpad several times and then press the trackpad button twice. it should shut down, or else pull the battery.
reboot into recovery
hold volume "down" and press the power button for a second and release. Wait 5 seconds and then press volume "down" once and press the power button. If all goes well, the phone should vibrate briefly. Wait a few seconds and then try adb.
Get a Ubuntu livedisk, boot from it and plug the phone in. You can see the phone's contents as well as sdcard. That would be the easiest. But if you can't do that and you have the latest clockwork mod, you will still need to mount stuff from recovery before you can access it. These instructions are relevant to the latest version (2.5+).
Once in recovery per gee one's instructions the menu is as follows:
Main Menu
- reboot system now <<- cursor
- apply sdcard:update.zip
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
By default "reboot system now" is select where it says cursor. Volume up/down to go up/down and trackpad to confirm. Power is to go back. The trackpad will also navigate for you, but it's hard to control so avoid using it for movement at all costs. It is also very sensitive to double clicks, try and make your click as quick and clean as possible.
Press Volume down 6 times and you will land on mounts and storage, then press trackpad (very quickly so as not to make it register a double click).
That menu is as follows:
Mounts and Storage
- mount /system <<-cursor
- mount /data
- unmount /cache
- mount /sdcard
- mount /sd-ext
- format boot
- format system
- format data
- format cache
- format sdcard
- format sd-ext
- mount USB storage
Your cursor starts on mount /system. Press trackpad once will mount system, pressing it again will unmount. Volume down will take you to data, and so forth. Then you can access those directories from adb, and do adb pull as others have suggested. Pressing it again will unmount it, and should be done. Keep in mind it will only unmount if you close all windows that point to that directory and leave the directory in adb shell (you can leave the directory by typing "cd /" to do that). If you stay in the directory or something is pointing to it, it will cause an error.
If you're unsuccessful, you can try doing a backup from clockwork.
From the main menu, press volume down 5 times and press trackpad.
The menu that appears is as follows:
- Backup <<-cursor
- Restore
- Advanced Restore
Simply click the trackpad again and it will perform a backup.
It will save the backup of the phone to the sdcard at /clockworkmod/backup/2010-12-8.x.x.x/
After that I'm not entirely sure how to extract it, hopefully someone else can help.
But simply put, get a live CD of linux and you go to Mounts and Storage and then to mount USB storage, you should have access.
Pic Please
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
gee one said:
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
Click to expand...
Click to collapse
*facepalm*
or that. if you go into adb shell, you can mount whatever directory and cp it to the sdcard. you can use 'umount' to unmount.
adb push/pull will not work when in adb shell, but you can easily copy it over to your sdcard with the cp command.
funkeee said:
*facepalm*
or that. if you go into adb shell, you can mount whatever directory and cp it to the sdcard. you can use 'umount' to unmount.
adb push/pull will not work when in adb shell, but you can easily copy it over to your sdcard with the cp command.
Click to expand...
Click to collapse
I just tried finding my G2 using an ubuntu 10.10 installation- it wouldn't find my phone unless I enabled USB mode, and then it would only find the sdcard. I'm still pretty new to ubuntu, so I might be missing something. It's like a brown version of my Mac!
adb push/pull will work from the terminal command line on your computer, not the shell.
Had some obligations I had to take care of but ... thank you for all the suggestions, I'll be trying them all to see which one I can get going!
I just got my replacement today & the first thing I noticed was the Z-Hinge issue.
Its looser than my original 'broken' phone right out of the box, even though the original has been thoroughly used for about 2 months...
so I gotta go thru Another replacement process ...
I suppose I'm going to keep getting replacements that people sent back for the Z-Hinge issue
gee one said:
If you have Clockwork recovery, you can boot into recovery mode and use adb.
Click to expand...
Click to collapse
^ I don't have any recovery programs on my device (unfortunately).
--
@ funkeee: I'll def. try this, seems promising.
ddgarcia05 said:
Pic Please
Click to expand...
Click to collapse
^ of?
gee one said:
How about "mount /system" or "mount /data" from the adb shell? This should be enough to poke around to extract files.
Click to expand...
Click to collapse
^ how would I go about and do that?
and as I mentioned before my device is simply set up for mass storage mode & I'm certain I need to get past the Unlock screen to access anything (but I obviously cant)
What kind of data are you trying to extract? It might seem obvious, but I think I should ask for the sake of completeness- is the data actually in the phone or on the memory card?
gee one said:
What kind of data are you trying to extract? It might seem obvious, but I think I should ask for the sake of completeness- is the data actually in the phone or on the memory card?
Click to expand...
Click to collapse
Well I can get the data from the memory card via my replacement G2 or an Sd adapter...but its mainly messages and some miscellaneous content / apps I had saved on the phone itself & the settings; its not a Big deal, but its something I'd like to port over.
If I didn't have a lock on it I could've managed my way through the menus using hard keys w/ my replacement as a guide but I have no way of doing it.
I wish there was an easy way to make a backup... still haven't got time to try the methods mentioned before, but I'm going to try and give it a go tonite.
Do you have a stock, unrooted phone? If you installed hboot-eng.img then there might be a chance.
gee one said:
Do you have a stock, unrooted phone? If you installed hboot-eng.img then there might be a chance.
Click to expand...
Click to collapse
yup, stock & unrooted... any hope?
SmartHat said:
yup, stock & unrooted... any hope?
Click to expand...
Click to collapse
I'm out of ideas, for whatever that is worth.
Thank you very much for the input, everyone.
I managed to get my phone into USB Debug mode & I've been able to open up a lot of options... (since I can finally use ADB).
So, Now I'm using my previously installed Android ScreenCast to see my previously Dead Phones Screen! -- Gotta love Android!
-- Now, can anyone suggest the best method for me to a image of my device, so I can flash it onto my replacement?
A Nandroid backup would be perfect, but you don't have root.
adb pull /data/app /somewhere/on/your/pc/app
will back up non-system apps, but not the settings or data
adb pull /data/data /somewhere/different/data
will grab your settings and data, but there is mix of other stuff in there as well that doesn't restore so well because it also contains other data. I think someone who is well versed in sqlite might be able to put it all back together.
Are there any data that you are looking for specifically? SMS? Browser bookmarks? etc?
gee one said:
A Nandroid backup would be perfect, but you don't have root.
adb pull /data/app /somewhere/on/your/pc/app
will back up non-system apps, but not the settings or data
adb pull /data/data /somewhere/different/data
will grab your settings and data, but there is mix of other stuff in there as well that doesn't restore so well because it also contains other data. I think someone who is well versed in sqlite might be able to put it all back together.
Are there any data that you are looking for specifically? SMS? Browser bookmarks? etc?
Click to expand...
Click to collapse
well I just temp rooted my 'broken' g2 ... ran titanium backup; Flashed clockworks recovery & now am backing up again(just to have all my bases covered)
When I went in to 'backup current ROM' in the Clockworks app, phone turned off and my Screen Cast disconnected... So I have no means of checking if I need to do anything else before my Rom's backed up
*ed-*
...but then again, since I have Visionary Temp root, wouldn't Clockworks loose its super user privileges when it restarted?
Answered my own question.
So it looks like nothing else will be possible unless I permaroot, which would void my warranty, meaning I won't be able to send it back in to T-mo
You can check the clockworkmod folder on your sd card to see if the backup completed. There should be 4 or 5 .img files if it ran.
Sent from my CyanogenMod Vision
There's no G-Slate forum yet, so this goes here.
How to root your T-Mobile G-Slate
This process works under Linux. The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
You need:
The four files in the gslate_root.zip archive attached to this post.
To root:
Put those four files in a directory and open a terminal to there.
Shut down your G-Slate and plug it into your computer via USB.
Hold down both volume buttons and press the power button. The G-Slate will not appear to turn on, but it'll go into APX mode.
Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
./nvflash -r --read 8 system-orig.img
Wait while 400 meg of data copies.
cp system-orig.img system.img
mkdir system
mount -o loop system.img system
cp su system/bin
chmod 4755 system/bin/su
cp Superuser.apk system/app
umount system
./nvflash -r --download 8 system.img
Wait while it copies back.
./nvflash -r --sync
Press the reset button under the sim cover to reboot.
There's your rooted G-Slate. Making that process "one click" is going to suck.
Troubleshooting:
You may need to install the package libstdc++6 or lib32stdc++6 to get nvflash to run.
You may need to use "sudo" on the nvflash commands.
If you want to try to make this work on Windows, the nvflash.exe binary and the APX USB drivers are are available from nvidia.com
This is unbelievable! Can't wait to give it a shot.
EDIT: For future reference, DO NOT use Virtual Box to try and root your device. There are issues getting the drivers to work properly. Lsusb will not work. The following methods have been tested and work:
1. Wubi install of Ubuntu Linux
2. VMware install of Ubuntu Linux
3. Dual-boot install of ""
4. Dedicated Linux box (duh)
And remember: If at first you don't succeed, try try again. Then visit our IRC channel.
Trying this on Windows 7 is gonna be a trip. Never workt with ext4 before.
Install Ubuntu and you can dual boot into Windows or Ubuntu. That's what I do.
Sent from my LG-V909 using XDA Premium App
This method is confirmed working. Thank you so much for the hard work Chandon. It wasn't very hard to complete on Linux. I can't believe my G-Slate is rooted!!!! Hell yes! Oh and the device is not wiped during the process either just to let everyone know!
Some More Help
Would it be possible to pull the recovery partition off now?
Why I ask. I am in a bit of a pickle. My slate will get to the first LG boot screen and then freeze. It does not even go to the boot animation. I can still get into fastboot and APX mode and it is seen by my computer.
How did i get here. While poking around in fastboot I am pretty sure i wiped they recovery partition D'OH.
I was able to complete the steps listed (for root) with out issue but still cannot get past the boot screen since this is only modifying the system partition.
I am thinking that if that could be pulled from the device i could flash it to mine and bring my slate back to life?
Am I way off on this one?
SmellyTunic -
Attached are all the reasonably small partitions that I could pull off my device with nvflash. This should be everything except /system, /cache, and /data.
I suggest backing everything up before flashing any of these, on the off chance that there's some difference between devices.
Thanks so much for this! Is there a good linux live cd(or bootable usb flash drive) someone could suggest where this could be accomplished easily? Not ready to take the plunge actually installing linux on my system yet >.>
Here you go
shinkinrui
Info and steps can be found here http://www.ubuntu.com/download
Pretty easy to set up a dual boot machine.
Chandon,
Any chance you know off hand which one of those partitions is the recovery?
I suggest doing a Wubi install [1], where Ubuntu pretends to be a Windows app (which you can then uninstall like any other app later). Alternatively you could try using VirtualBox [2], but that's less guaranteed to work.
The only reason I wouldn't do this with a Live CD is that you'd risk losing your backup of the stock /system partition when you reboot. It would also make losing power in the middle of the flash really annoying.
[1] https://wiki.ubuntu.com/WubiGuide
[2] (edit: virtual box doesn't easily see the USB device)
Thanks guys, reading about that Wubi solution looks like the simplest way to have a dual-boot system. I like it! I'll be getting my root on later tonight
i prefer Ubuntu just cause you can install it in windows then simply restart and boot into Linux or Windows. This way you don't need to worry about not having Linux again.
SmellyTunic said:
Any chance you know off hand which one of those partitions is the recovery?
Click to expand...
Click to collapse
I'm sure that /system is 8 and the kernel is 13, but don't know about anything else. You might be able to figure it out by reading the ptable.txt file generated by the --getpartitiontable command - it's pretty clear except for the part where it uses 3 letter partition names.
Thanks. I will take a look when i get home from work.
Sent from my GT-I9000 using XDA App
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
deez1234 said:
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
Click to expand...
Click to collapse
I definitely concur.
thengkiu so much
works like a charm
I have no idea why I'd ever need/want to root my G Slate, I'm fairly simple in my desires for my device - but I have to say I'm delighted to see it is possible and am ever so grateful for folks who figure this stuff out because it keeps moving G Slate towards legitimacy.
Thank you!!
The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
Click to expand...
Click to collapse
No kidding. Since the linux method failed miserably for me, I've decided to press forward with trying to do it on Windows. Problem is, I have yet to find any way to mount an ext4 filesystem on Windows. There are several options out there that will allow you to read ext4 filesystems on Windows, but not write. Any suggestions?
my friend will be happy to see that this is possible.
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....
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
Afternoon all,
My G4 has hit the bootloop for the last few days. Periodically, it has powered up to the main screen, but not for long enough for me to recover data.
I just spoke to a data recovery place that told me that if I can put my phone into download mode, they can recover the data. Lo and behold, my phone is currently next to me in download mode!
I'm quite keen to avoid dropping that amount of money if possible, so does anyone know of a way to recover the internal memory of the phone via download mode?
Apologies if I'm duplicating a previous thread - I had a quick look, but couldn't see any with the same issue.
Probably when the phone is in download mode they can copy the partitions bit by bit then try to do data recovery from those partition images.
So if the phone doesn't boot, it doesn't mean the data partition is corrupted so in theory you could try to copy the data partition and mount it and see what files you can recover.
I do not know the exact commands to dump the data partition but I think that's the way it can be done.
Anyone else willing to give a hand here?
Thanks for the help so far. I believe the data is intact - when the phone starts up, the data is all there. It's just accessing it that is the issue.
Sent from my Nexus 5 using Tapatalk
something similar to
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/mnt/media_rw/external_SD/data.img
OR
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
don't quote me on that but in theory this should work...
make SURE you have a 32gb SDCard in the phone first
Where would that command be entered mate? Sorry, only ever used my phone stock before.
Sent from my Nexus 5 using Tapatalk
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
je2854 said:
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
Click to expand...
Click to collapse
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
terisse said:
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
Click to expand...
Click to collapse
If you try this, please put the phone in a ziploc bag 1st and seal it so humidity won't get inside the phone while in the fridge.
nagalun said:
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Click to expand...
Click to collapse
just a question though... How can you use this command if it will not boot?
---------- Post added at 08:59 AM ---------- Previous post was at 08:50 AM ----------
to get into download mode do the following...
Pull Battery
Hold Volume Up
Plug in USB Cable (make sure it's plugged in the computer)
Release button after 5 seconds
follow the link to grab the files needed for "Send_Command"
Grab LG Root here
once you are in the mode and you followed directions you can copy the command I wrote
above to copy your data partition. The reason you must have a 32gb+ SDCard is you will
be making an exact copy of the /data partition where you can remove the SDCard and recover
whatever is needed.
je2854 said:
just a question though... How can you use this command if it will not boot?
Click to expand...
Click to collapse
Hmm... With the Send_Command.............? dd is a command too :silly:
nagalun said:
Hmm... With the Send_Command.............? dd is a command too :silly:
Click to expand...
Click to collapse
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
je2854 said:
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
Click to expand...
Click to collapse
in that case the command you have given him will copy 4492 mb only.
Here is why:
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
input_file=(some partition) block_size=8192 skip_this_much_data=65536 how_many_data=548352 output_file=(somewhere)
actual data copied is 8192 * 548352 = 4492099584 bytes, and you are skipping some data from the beggining with 'skip'
you do still need to mount the sdcard, the "mmcblk1" is not treated as a directory, and it is very unlikely the sd card is mounted automatically in download mode.
nagalun said:
in that case the command you have given him will copy 4492 mb only.
Click to expand...
Click to collapse
remember me saying (if you read) above that I said "something similar to"
Hi all. Firstly, thanks for all your responses!
I've not got much of a clue what I'm doing unfortunately, I've never really messed with Android before - I'm typically fairly computer literate, but I've steered clear of messing with and rooting phones for the most part.
So to clarify, I've downloaded LG Root, Running either of the exes just leads to a cmd box that's open for about a second before closing, so I'm presuming I've missed a step. Is there a guide already in existence on how to use it?
But once in, ensure there's a sizeable Micro SD card in (it's a 64gb so I should be okay!) and use the send_command exe to send:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
And then the entire image should be on the Micro SD card.
How would I then mount the data image to be readable? I've only used .iso for mounting before.
Apologies for my ignorance - I'm probably making helping me quite difficult!
Sorry all, correction to my previous:- Do I basically follow http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
And replace step 10 with the above command?
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
je2854 said:
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
Click to expand...
Click to collapse
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
IlyaKol said:
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
Click to expand...
Click to collapse
Mine will only get to optimising Apps, even if still in the freezer.
Sent from my Nexus 5 using Tapatalk
Hi all, sorry for the double posting, but just to make certain before I do something that will accidentally brick my phone. I'm intending to do the following:
Put phone in download mode and connect device.
Open LG_Root folder
Run a command window in LG_Root
Code:
Send_Command.exe \\.\Com4
Then, line by line, command:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Once I've done all this, what happens next? Will I see responses on the screen etc?
Again, I apologise for the probably stupid questions. I don't want to brick my phone and lose all of the data, but I'm going away with work so would like to square it before I go if I can.
Many thanks to you all so far.