using terminal in ubuntu with adb. can access root with phone booted fine. Need to access su with phone in recovery as im attempting to mount internal storage to perform emergency data recovery. Im using the guide from MohammedAG's blog. (which seems to have been taken down as of yesterday....)
Is this possible? phone is rooted with safestrap 3.72 installed.
Im able to get the drive to mount temporarily (with phone booted), with this command:
echo /dev/block/platform/msm_sdcc.1/by-name/userdata > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
it shows the files and directories for between 2-10 minutes then the phone will reboot. Want to create a drive image using GNU ddrescue.
Any help/thoughts/insight would be greatly appreciated.
Success!!!!
Ok so i figured out another way. I was unable to access root from recovery...I would get error "CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found"
But I DID have access with phone booted. I was working in unbuntu terminal as MohammedAG suggested as Windows cannot read ext3 partitions. This would work temporarily as I mentioned above but would then crash and reboot the phone. Due to the system being double mounted?? i think...
So i tried it in windows, the command worked I saw the drive! It asked me to format so i could use the drive...Cancel. The drive was now still visible(but not usable by windows) as a logical drive.
So using iRecover (diydatarecovery.nl) which supports ext3/4 drives I was able to perform recovery on the device and create an image file just to be safe.
Recovered a ton of files! Awesome!
Related
I am trying to get tun.ko installed per (url removed cause I'm new) = code.Google.com/p/get-a-robot-vpnc. I have root and mounted system rw but when I try to copy it whether by adb or terminal I get "cannot create /system/lib/modules/tun.ko: not enough memory. Anyone have some clues for me please? Thanks.
Never mind. Was finally able in recovery mode.
I've managed to make a typo somewhere when updating the build.prop and it hasn't written it, now my tab has a /System/build.prop.old file, but no /System/build.prop file. I've got a backup of the file, has anyone either got a valid UPDATE.ZIP file for a JK5 EU firmware version of the build.prop that I can write (will it work from the "external" SD card?) - or some other way of gaining root access via the recovery ADB shell so that i can rewrite this file, or am I going to need to reflash via Odin? I've tried creating my own update.zip file but it tells me that it can't find it, so I'm guessing it has to be on the internal SD card, which is not a lot of use as I can't mount it.
Not a big deal if I have to, I'd just rather know an alternative in case I stuff it up again
EDIT: Nevermind, I worked out how to gain root access whilst in recovery, pretty simple really - the same as the regular manual-root process but just using a different work folder. The /tmp folder is writeable in recovery mode so I just copied the rageagainstthecage binary into there via "adb push", set it to executable, ran it, killed the adb server and restarted it, reconnected and I had root access, moved the build.prop back and all is well again.
Based on this, it'd be a piece of cake to write an UPDATE.ZIP that did a full permanent shell-root and also installed busybox and superuser.apk. Any point or are people happy enough with the existing methods?
i have a mz601 xoom - european.
i played to much with it and now it stoped recognizinig the sdcard
i have tried all without luck.
can anybody help me with that?
i noticed the error mesaage everytime i power on the xoom with sd card inside:
"android.process.media stoped"\
maybe i ereased the folder?
You say you played too much with it...what did you do exactly? Without more information, we can't help you.
please help
i tried to install ubuntu, and that was the read me file:
what is this?
An ubuntu 10.10 maverick (with LXDE window manager) machine in your pocket. Perfectly usable from the phone itself using a VNC client, this allows you to install any ubuntu software onto your phone and have it with you always. Coupled with the (potential) ability for your phone to be hooked up to a television with TV Out (works with the Nokia TV Out cable available on eBay), and for (supposedly any) HID-compliant bluetooth keyboard and mouse to be linked up to the phone (requires Android 2.2), this really does become a PC in your pocket.
Requirements:
- android phone
- superuser + busybox
Included:
- 3.5GB virtual machine image (ubuntu.img) with ubuntu and certain applications pre-installed (listed below). The image is resizable with uec-resize-image, although FAT32 (the most likely format of your SD Card) has a maximum file size of <4GB.
- A script to boot into ubuntu from android (ubuntu.sh)
- A script to start the VNC Server and other startup commands. This is contained within the ubuntu.img file at /root/init.sh, accessible and modifiable once ubuntu.img has successfully booted.
How to boot:
- Place ubuntu.sh and ubuntu.img in the same directory in your SD storage.
- Enter a terminal and enter 'su' to become a superuser (root).
- Navigate to the directory where you placed the files (e.g. "cd /sdcard/external_sd/ubuntu").
- Execute the script by typing "sh ubuntu.sh".
Tip: Some android terminal emulators (e.g. better terminal) allow you to specify an initial command that is run as soon as you launch the application. Multiple initial commands can be defined by pressing return between each command when you define it, so for example the initial command:
su <return>
cd /sdcard/external_sd/ubuntu <return>
sh ubuntu.sh <return>
after a hour without respons i rebooted the device, and the hole system was down. i got stock with the logo. so i formatted the hole directories via cwm and isntalled stock rom upgraded to 3.2 and it gave me the error i wrote earlier every time i had a sdcard inside.
so i downgraded (via fresh install) to 3/1 and somehow succeeded to instal timat 3.2 but with the same sdcard problem.
cmw does not recognie the sd card also. can it be that i have to creat a directory or something like that?
please help
Your problem is beyond the scope of my understanding. I know someone can probably help you, but I've never seen that exact issue before.
Good luck!
I sadly dropped my nexus 4 on hard tiles yesterday face down and the whole front cracked everywhere! The phone still turns on, I can copy internal storage off fine, but since the touchscreen doesn't work anymore I'm having trouble with getting system data off e.g. sms.
I've managed to get non touch CWM installed, made a nandroid, but now I can't copy the damn thing off! ADB gives me unauthorised for every command, and obviously I can't use the phone to authorise my PC. Am I now essentially screwed? Been googling for ages and can't find a way round the fact I can't use ADB or force my phone to authorise my PC without using the screen.
Any other ideas would be massively appreciated. The phone is rooted, CM10.2, and luckily usb debugging is enabled.
Cheers!!
You said you can copy internal storage right? so why not pull the nandroid from /clockworkmod/backup?
Sent from my Nexus 4 using Tapatalk 4
I do not use CWM, but I do use TWRP and it allow me to access to the /data and /sdcard partition just fine, /system is off limit though. I don't know where your nandroid is backed up in, but I assume its in /sdcard.
Try this: Flash TWRP in fastboot mode, then press the volume button either up or down twice, then press Power to access the recovery. Then on the main menu of TWRP, you can do adb commands right away.
I can then simply back up my whole /sdcard partition by: adb pull /sdcard/ C:\backup
Or backup the all the apps data: adb pull /data/data/ C:\backup
Thank you both for the advice. I've tried using adb in recovery, but it says: remote object '/sdcard' is not a file or directory.
If I type adb devices, I get my phone ID along with 'recovery' next to as expected.
Any ideas?
Thanks.
EDIT: Ignore this, just added a / after /sdcard and now its pulling ok. Thanks so much!
I was typing this up before I read your edit:
If you don't know where certain files are, you can type "adb shell" to enter the phone itself, there you can look at the phone directory structure and find where your files are located.
Use the cd and ls commands to navigate in the phone: http://afrodita.rcub.bg.ac.rs/~ivica/nlm/part1/cd_ls.html
Once you're done, type "exit" to get out of adb shell. Then you can use the "adb pull" command to copy the files.
Hi,
I need some help from experienced members.
I recently followed the guide carefully and updated my acer a500 to CM10.2
[ROM] [A500] Android 4.3 [CM10.2 Unofficial] Build 6
Everything went well as expected and even used the new ROM and the tablet for about 4 days without any issues. The device had turned off due to low battery and when i tried to turn back on, it is stuck in initial boot with the android robot picture stating booting primary kernel. It just stays here for ever.
I can access the recovery menu and have tried to reload the Rom and gapps files after doing a wipe; however have had the same result.
As i cannot boot, i am unable to connect and transfer any other rom files to it. What should i do? I need your help please.
Still looking for help
As mentioned previously i am unable to load to primary boot, as it just hangs at the android logo.
I am able to go into recovery menu, however when i goto install from internal storage it says "No Files Found".
I dont seem to be able to access the internal storage, please help.
srskiller said:
As mentioned previously i am unable to load to primary boot, as it just hangs at the android logo.
I am able to go into recovery menu, however when i goto install from internal storage it says "No Files Found".
I dont seem to be able to access the internal storage, please help.
Click to expand...
Click to collapse
Not sure if I have an answer for u but think I'd be trying wiping data and both caches. If that don't work then erase data/media.
If still no joy, then run babsector.rar file. Its an all in one tool that will reset partitions and flash the v8 bootloader and cwm. If it throws an error pls post the output.
You could also try the rom thread in case oyhers have reported similar issues
dibb
Solved
Managed to fix it.
Problem i was having was that i was not able to access the internal storage via recovery; as it kept saying no files found and that it could not even mount the drive.
I had to use a USB thumb drive, made it to boot as /sdcard and then copied my ROM file and gapps file on it. Then did a restart to recovery and installed the ROM and gapps files.
I was then able to boot normally and also had access to internal storage.
Hope this helps someone else.
Earlier: when i had it stopped at android logo; i also tried babsector and i also did the following:
Connect the tablet to the PC in RECOVERY. At this point, ADB should work. If not, check the drivers on the PC - I had to manually specify the Acer ADB Composite driver.
* Open a Command prompt window
* Start ADB shell by typing:
ADB SHELL
* Now execute the following:
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8