How could i transfer files in CWM?
Both my sdcard and internal partition was accidentally wiped out when trying to fix a bootloop earlier.
Currently, my phone could only access fastboot and recovery mode. I wanted to transfer *.img on my sd partition so i could flash a ROM to fix this problem.
I already tried to mount the usb storage from CWM recovery. but it would give me an error "E: unable to open ums lunfile"
is there any way to push a *.img file to my sdcard? or is there any way that i could flash TWRP?
Update to latest CWM
Check to see if you have the latest CWM. If not then flash the new one. Once your connected you can just drag & drop from your pc.
Sent from my HTC One X using xda app-developers app
BenPope said:
Update to latest CWM
Click to expand...
Click to collapse
Thanks for that Ben, but is it possible to update to the latest CWM, i could not boot my phone, I could only access recovery/fastboot mode. Im sorry being so stupid, im just new to this stuff :crying:
EDIT: my bad. thanks for the advice. trying to update now
Banzai761 said:
Thanks for that Ben, but is it possible to update to the latest CWM, i could not boot my phone, I could only access recovery/fastboot mode. Im sorry being so stupid, im just new to this stuff :crying:
EDIT: my bad. thanks for the advice. trying to update now
Click to expand...
Click to collapse
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
not working
I unlocked the boot loader after following all the steps on htcdev.com..
it was successful.
then i installed CWM v5.8.4.0
then i tried to install Viper X custom rom from the recovery.
but even with the aroma installer, i has to select next,etc with with vol+,vol- button and then power button to click.
what is wrong with my phone..please help me..
wcypierre said:
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
Click to expand...
Click to collapse
Thanks for your help
George_Orever said:
Thanks for your help
Click to expand...
Click to collapse
thank you very much
---------- Post added at 02:02 AM ---------- Previous post was at 01:54 AM ----------
wcypierre said:
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
Click to expand...
Click to collapse
every time i try to push a file i get this
C:\adbfastboot>adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip/sdcard
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
What do i do?
I think that you wanted to push adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip to /sdcard.
If yes, then, you need an additional space for it to separate the source and the destination
adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip /sdcard
mikkygwaz24 said:
thank you very much
---------- Post added at 02:02 AM ---------- Previous post was at 01:54 AM ----------
every time i try to push a file i get this
C:\adbfastboot>adb push cm-10.1-20130411-EXPERIMENTAL-endeavoru-M3.zip/sdcard
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
What do i do?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why dont you enter the recovery and mount the sdcard as a usb diskdrive and copy to it what you need ?
wcypierre said:
yeah, you can send files to sdcard at cwm, by using adb.
1. Open your cmd and navigate to the folder with the adb files(the folder where you flashed your roms, kernels, or recovery).
2. Access the cwm at your phone and connect an usb cable to the computer.
3. Put the files that you wanted to send to your phone at that particular folder
4. Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
4.1. Depending on your OS, you may want to add "./" at the front of the command if you're using unix based os(this is an oversimplified version)
5. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
6. Wait for a while or reboot your cwm so that the filename will appear and just reflash the file.
7. Voila!
Click to expand...
Click to collapse
This!
Just saved my life.
- I had a pandroid LG G2 but locked.
- To unlock, I had to restore to stock (3+ hours mainly download times) and first time setup.
- It was working perfect as stock. But Wanted CWM or TWRP. Installed CWM correctly.
- MAde nandroid backup
- Reboot - said yes to reapply Loki + Super.
- Destroyed everything in the phone. Download mode will not work. Only thing I could do is go in recovery!
- Been working all sort of fix but none worked. Can't put custom roms either (weired loki error)
- Finally thought I should try pushing this original backup on phone! worked and installed in 10 min!!
PrinceMS said:
This!
Just saved my life.
- I had a pandroid LG G2 but locked.
- To unlock, I had to restore to stock (3+ hours mainly download times) and first time setup.
- It was working perfect as stock. But Wanted CWM or TWRP. Installed CWM correctly.
- MAde nandroid backup
- Reboot - said yes to reapply Loki + Super.
- Destroyed everything in the phone. Download mode will not work. Only thing I could do is go in recovery!
- Been working all sort of fix but none worked. Can't put custom roms either (weired loki error)
- Finally thought I should try pushing this original backup on phone! worked and installed in 10 min!!
Click to expand...
Click to collapse
You're welcome. Glad that my solution worked well for you
PrinceMS said:
This!
Just saved my life.
- I had a pandroid LG G2 but locked.
- To unlock, I had to restore to stock (3+ hours mainly download times) and first time setup.
- It was working perfect as stock. But Wanted CWM or TWRP. Installed CWM correctly.
- MAde nandroid backup
- Reboot - said yes to reapply Loki + Super.
- Destroyed everything in the phone. Download mode will not work. Only thing I could do is go in recovery!
- Been working all sort of fix but none worked. Can't put custom roms either (weired loki error)
- Finally thought I should try pushing this original backup on phone! worked and installed in 10 min!!
Click to expand...
Click to collapse
Not trying to highjack this topic, but how did you push the file to the sd card when the LG G2 does not have an sd card, only storage. I ask as I have the LG G2 and have clockworkmod installed as my recovery, but my internal storage is blank and my nandroid backups are gone. I cant find a way to get a rom onto my internal storage so I can flash it.
Edit: After shedding a few tears (Just Kidding) thinking I was screwed since I only had internal storage. As long as you have adb setup correctly, do the following:
1. Enter clockworkmod recovery
2. go to mounts and storage
3. Mount /data
4. Type adb push filename.zip /data/media/0
5. After the file has copied over, unmount /data in the mounts and storage
6. probably not required, but I rebooted recovery.
7. Install your zip.
Thanks wcypierre for basically giving me the process. I just needed to rework it a bit.
Without Ninthsense and Roothorick this would not be possible, and all credit for this belongs to them!
This is a guide for installing a recovery.img from your SDcard, without the use of your USB port, ODIN, or CWM
This is through the android terminal emulator app, with root permissions. or via ADB over WIFI
**The issue: I cannot transfer data at all through my USB port and was not gonna attempt flashing out of fear of brick!
I was able to extract the recovery.img from the ODIN flashable CWMrecovery 6.0.1.2 package developed by Terinfire but was unable to create a CWM flashable zip because I lack the expertise. (I still have my old CWM touch recovery developed by Aquethys).
After reaching out Ninthsense and Roothorick helped me with the command line to make this possible.
Whats needed:
1) a broke USB (don't attempt this unless its the very last option)
2) the recovery image file for this phone
3) ROOT ACCESS!!!
4) a terminal app or ADB over WIFI
Below is the Partition Table for the Glide(thanks ninthsense):
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
To connect ADB over WIFI (thanks ninthsense):
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
**if doing this using ADB you must enter a shell and run the su command
adb shell
su
Now do the following:
1) move "recovery.img" to root of SDcard
2) backup current recovery:
(if in terminal and not ADB over WIFI you must enter "su" before continuing)
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
3) Install new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
Thats it!!!! reboot recovery and enjoy!!!
Hey you forgot the first step :laugh: , on how to connect to the device through "ADB over network".
ninthsense said:
Hey you forgot the first step :laugh: , on how to connect to the device through "ADB over network".
Click to expand...
Click to collapse
I will modify the OP, I figured I would list the terminal steps because of its ease of use Ill add both!
**edit** done! how's that looking?
Cprager said:
I will modify the OP, I figured I would list the terminal steps because of its ease of use Ill add both!
Click to expand...
Click to collapse
Add the list of partitions as well, maybe somebody will find it useful for backing up and restoring something else as well.
ninthsense said:
Add the list of partitions as well, maybe somebody will find it useful for backing up and restoring something else as well.
Click to expand...
Click to collapse
done!
You're a life saver!!!!
Cprager said:
Without Ninthsense and Roothorick this would not be possible, and all credit for this belongs to them!
This is a guide for installing a recovery.img from your SDcard, without the use of your USB port, ODIN, or CWM
This is through the android terminal emulator app, with root permissions. or via ADB over WIFI
**The issue: I cannot transfer data at all through my USB port and was not gonna attempt flashing out of fear of brick!
I was able to extract the recovery.img from the ODIN flashable CWMrecovery 6.0.1.2 package developed by Terinfire but was unable to create a CWM flashable zip because I lack the expertise. (I still have my old CWM touch recovery developed by Aquethys).
After reaching out Ninthsense and Roothorick helped me with the command line to make this possible.
Whats needed:
1) a broke USB (don't attempt this unless its the very last option)
2) the recovery image file for this phone
3) ROOT ACCESS!!!
4) a terminal app or ADB over WIFI
Below is the Partition Table for the Glide(thanks ninthsense):
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
To connect ADB over WIFI (thanks ninthsense):
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
**if doing this using ADB you must enter a shell and run the su command
adb shell
su
Now do the following:
1) move "recovery.img" to root of SDcard
2) backup current recovery:
(if in terminal and not ADB over WIFI you must enter "su" before continuing)
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
3) Install new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
Thats it!!!! reboot recovery and enjoy!!!
Click to expand...
Click to collapse
:victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory:
I cannot thank you enough for this post! I was trying to locate that partition since the USB doesn't work on the Glide I am repairing, and alas! - you came and saved the day!
Thanks alot, mate!
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Hi
this is from the BoardConfig.mk
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
I want to find the actual size partition adb shell cat /proc/mtd" or "adb shell cat /proc/emmc" or "adb shell cat /proc/dumchar_info" doesn't work !
Steps:
*root your device;
*install TWRP or CWM for your device ;
*install busybox tools ( Busybox Free Goolge Play);
After this, enter to recovery mode. Mount /system into TWRP or CWM.
Plug USB cabe, and in your computer input these commands:
adb devices --> verify if device is connected
Now, install parted into /system/bin:
adb push <path-to-file>/parted /system/bin
Now, insert this command:
parted /dev/block/mmcblk0 unit B print
The output is similar :
Code:
~ # parted /dev/block/mmcblk0 unit B print
Model: MMC 008GE0 (sd/mmc)
Disk /dev/block/mmcblk0: 7818182656B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 6291455B 2097152B MRD
2 6291456B 8388607B 2097152B MRD_BK
3 8388608B 10485759B 2097152B MEP2
4 10485760B 31457279B 20971520B ext4 EFS
5 31457280B 46137343B 14680064B Reserved
6 46661632B 48234495B 1572864B LOKE_2ND
7 48758784B 50331647B 1572864B LOKE_1ST
8 50331648B 67108863B 16777216B PARAM
9 67108864B 83886079B 16777216B RECOVERY
10 83886080B 100663295B 16777216B KERNEL
11 100663296B 125829119B 25165824B MODEM
12 125829120B 142606335B 16777216B ext4 NVM
13 142606336B 352321535B 209715200B ext4 HIDDEN
14 352321536B 713031679B 360710144B ext4 CACHE
15 713031680B 2307915775B 1594884096B ext4 SYSTEM
16 2307915776B 7817134079B 5509218304B ext4 USER
Use the column size to fill in the BoardConfig values.
The first column it refers to the mount point.
Ex.: the kernel partition has 16.777.216 bytes mounted in /dev/block/mmcblk0p10
Links references:
http://forum.xda-developers.com/showthread.php?t=2450045
http://stackoverflow.com/questions/...ormation-for-android-device/15639867#15639867
http://forum.xda-developers.com/attachment.php?attachmentid=2397268&d=1384688569
naufragoweb said:
Now, install parted into /system/bin:
adb push <path-to-file>/parted /system/bin
Click to expand...
Click to collapse
Path to.. what file?
Nicofisi said:
Path to.. what file?
Click to expand...
Click to collapse
Path to the "parted" file in your PC
Hi Guys
I'm new to the Forum and start with asking a question - apologize for that, I know that it's impolite.
I'm pretty desperate at the moment. Tried to switch on my Galaxy Nexus some days ago and it did not start. If I try to switch it on (long button press), the google logo appears for about 72 seconds, then "something" happens on the screen (usually the logo becomes brighter and horizontal lines appear on the screen). And that's it.
There's no clear reason why the mobile is broken now.
The big problem is that I have lots of pictures of my little boy on that device, from his birth until now (it's his first birthday tomorrow). These pics are very very important to me, the only pictures I have from his birth. I did not backup those pictures - I'm stupid. So my goal is to rescue those images from the device somehow. Currently I'm spending every free second to read and learn how to recover those images...
Device info:
Galaxy Nexus, Tuna Maguro 16GB
HW Version: 9
Bootloader Version: PRIMEMD04
Baseband Version: I9250XXLJ1
Everything is stock version, Android 4.4.2 (I think), stock bootloader
What I've tried so far:
- Installed fastload / ADB on Ubuntu 14.04 from repo. Manually installed ADB 1.0.32 as well.
- I can boot the device into Fastboot / Rescue / Odin mode, that works.
- Tried to clear the cache. It hangs after "Formatting /cache". No "completed" message. If I go to the recovery menu now, I get a couple of messages which say
"E:failed to mount /cache (Invalid argument)"
and then lots of "Can't mount /cache/recovery/log" messages.
If I boot in Rescue Mode, select "apply update from ADB" and connect the mobile to the PC:
Code:
[ 502.524071] usb 1-5: new high-speed USB device number 3 using ehci-pci
[ 502.657321] usb 1-5: New USB device found, idVendor=18d1, idProduct=d001
[ 502.657330] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 502.657348] usb 1-5: Product: Galaxy Nexus
[ 502.657352] usb 1-5: Manufacturer: samsung
[ 502.657355] usb 1-5: SerialNumber: (redacted)
So it gets detected, at least.
Then:
Code:
$ ./adb get-state
sideload
$ ./adb devices -l
List of devices attached
(serial redacted) sideload usb:1-5
$ ./adb backup -all
adb: unable to connect for backup
$ ./adb bugreport
error: closed
$ ./adb shell pwd
error: closed
$ ./adb logcat
- waiting for device -
^C
I've downloaded the stock yakju ROM from the google dev website (can't post links, sorry).
There are a bunch of files in that archive:
Code:
$ ll
total 298996
drwxr-x--- 2 m m 4096 Aug 21 2013 ./
drwxr-xr-x 7 m m 4096 Aug 30 23:50 ../
-rw-r----- 1 m m 2363392 Aug 21 2013 bootloader-maguro-primemd04.img
-rw-r----- 1 m m 956 Aug 21 2013 flash-all.bat
-rwxr-x--x 1 m m 827 Aug 21 2013 flash-all.sh*
-rwxr-x--x 1 m m 785 Aug 21 2013 flash-base.sh*
-rw-r----- 1 m m 291192953 Aug 21 2013 image-yakju-jwr66y.zip
-rw-r----- 1 m m 12583168 Aug 21 2013 radio-maguro-i9250xxlj1.img
Code:
$ zipinfo image-yakju-jwr66y.zip
Archive: image-yakju-jwr66y.zip
Zip file size: 291192953 bytes, number of entries: 5
?rw-r--r-- 2.0 unx 4481024 b- defN 09-Jan-01 00:00 boot.img
?rw-r--r-- 2.0 unx 5042176 b- defN 09-Jan-01 00:00 recovery.img
?rw-r--r-- 2.0 unx 485561008 b- defN 09-Jan-01 00:00 system.img
-rw------- 2.0 unx 140860420 b- defN 13-Aug-13 22:56 userdata.img
-rw-r----- 2.0 unx 93 b- defN 13-Aug-13 16:00 android-info.txt
So my questions are:
Am I doing the right thing here? I Hope that this is a software problem and the hardware is ok.
If yes, which of those file(s) should I flash to the device, without risking the loss of data?
Can you think of any other possibility to recover the data? Clockwork mod or TWRP maybe? Or a custom sideload script (inside the uploaded zip file).
I've read that flashing a custom bootloader wipes the device - so maybe CW / TWRP is not a good idea...
Thank you very very much for your help.
Matt
It may have been a while, bit it might help anyways
Boot your phone to the Bootloader mode. Connect it to your PC via USB.
Use Terminal to cd into your adb/fastboot folder.
Grab the latest TWRP from here: https://dl.twrp.me/maguro/
Copy it into the same directory as fastboot and rename it to recovery.img
Then try to boot into recovery (assuming you haven't rooted your phone and you have a locked bootloader) with "./fastboot boot recovery recovery.img"
I am not sure if this will work with a locked bootloader, but it's worth a try.
If it boots to TWRP then "./adb pull /sdcard/ /backup/" this should create a folder with all the contents of the internal memory in the fastboot direcory. Just let it copy, its done when you are at a prompt again.
Hi I habe an Note 8 pro and I tried to convert an 64 GB scandisk card to internal storage.
here are some information, I had two information ab
out the disk Id
adb shell sm list-disks 179,0
adb shell sm list-volumes all 179,1 puplic
adb shell sm set-force-adoptable true
Continue type : adb shell sm partition disk:179,1 private
Continue type : adb shell sm set-force-adoptable false
Continue type : adb shell sm list-volumes all /sd card still public
I try it wtih 179,1 first one second and it was done, but nothing had changed, second with 179,0 an error message apears.
Had xiaomi this thing disabled ?