Please help me, my boot show error:
E:Can't read MISC: (No space left on device)
Click to expand...
Click to collapse
Do you have custom recovery? if yes, boot in recovery and access the phone via adb shell and check disk space with df. you will see the percentage of how much disk space is in use. if it is system, try to delete the boot sounds and some ringtones. if its data, delete the contents of /data/local/tmp (i suppose there are many apks there which aren't in use at all).
Hope this helps
55% /system
19% /data
18% /cache
25% /sdcard
how to clear width shell
babyskill said:
Please help me, my boot show error:
Click to expand...
Click to collapse
I have same problem and no one help me
hi
I have same problem... i was try this:
1. Install RUU-2.73.405.5 exe can be from HTC website(You need GoldCard)
link: ftp://xda:[email protected]/Hero...ed_NoDriver.exe
2. Install Instant Root
3. Install Recovery Flasher
4. Install Recovery-RA-hero-v1.6.2.img
5. Reboot in recovery mode - if You have error: Can't read MISC(No space left on device) go forward:
6. Copy misc.img and recovery-RA-hero-v1.6.2.img to your SDCard
misc.img is here: http://content.modaco.net/dropzone/nandroi...6.405.6_WWE.zip
7. adb shell
8. su
9. mount /sdcard
10. cat /dev/zero > /dev/block/mtdblock0
11. dd if=/sdcard/misc.img of=/dev/block/mtdblock0
12. flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
13. reboot recovery
but isn't help me..
I hope U will be more lucky
Htc hero cant misc error recovery mode
How to bootloader mode or fastboot mode ?
Please help me unbrick my soft bricked Asus SL101 tablet.
I'm normally pretty good at rooting and upgrading android phones etc to custom ROMs and decided to install CM9 on it recently.
Rooted using PERI
Installed CM9 using PERI
Rebooted into CM9
Screen appeared telling me it cannot access my encrypted user data partition
Gave it permission to re-format that partition (I had nothing on it that wasn't on my PC anyway)
Tablet reboots and returns to screen asking to format encrypted partition
(rinse and repeat)
From everything I have read the solution seems to be re-installing the factory Asus ICS firmware, logging into the encrypted partition and unencrypting it. However, all of my attempts to install the stock Asus ICS firmware (9.2.1.27) have failed as follows.
Code:
[B]assert failed: write_raw_image ("/tmp/blob", "staging"[/B])
I researched that and found that I could create a dummy "staging" through ADB.
(post 3 of this thread: http://forum.xda-developers.com/showthread.php?t=1235724)
So I set up Android SDK and ADB, but running the commands produces no result.
Code:
C:\Users\Joe\adb shell
~# mount /dev/block/mmcblk0p4 /staging
mount /dev/block/mmcblk0p4 /staging
~# exit
exit
I then run the zip install in Rogue again, but get the same result.
Any help will be greatly appreciated.
I deleted Rom file in sdcard. I cant flash a rom. I have recovery, root and Philz Touch.
How can i copy Rom zip file from computer to Phone? Any idea. I have rooted KK, i dont want to do all things again.
How to: Copy ROM zip file to the freshly wiped device
I found and share with you, it worked.
Have you ever been in a situation where you mistakenly (or not) wiped the content of the internal storage (including system partition and virtual SD card) on your phone or tablet and unfortunately it doesn't support external storage? Now you can't flash desired custom ROM because you removed it and the device can't be booted due to wiped system partition. Don't worry - it's very easy to fix!
Here are the steps you need to follow to copy the correct rom.zip package to your internal storage:
Download this mini-sdk package and extract it to c:\mini-sdk
Rename the custom ROM package you want to flash to "rom.zip" and copy it to c:\mini-sdk
Connect your device to the PC
Boot your device in recovery mode
Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:
cd /d c:\mini-sdk
adb shell
mount /data (error might mean that /data partition is already mounted)
on Android 4.2 and above: mkdir -p /data/media/0
on Android 4.1.2 and below: mkdir -p /data/media
exit
on Android 4.2 and above: adb push rom.zip /data/media/0
on Android 4.1.2 and below: adb push rom.zip /data/media
Wait for a few minutes until the file is copied. It will looks like command shell is not responding, but that means it's still copying. Wait patiently until you'll see blinking cursor again.
Depends on your custom recovery, use the navigation keys to flash the custom rom.zip package in a typical way you used to flash custom ROMs. It should be on your internal storage now. Done! http://android-revolution-hd.blogspot.com.tr/2013/12/how-to-copy-rom-zip.html
easier solution:
*bring device in recovery mode
*open cmd, go to adb.exe
*type adb.exe push *filename.zip* /sdcard/your path **/sdcard is already linked to /data/media/0
*wait after pushing the file, reboot recovery again
*choose file and flash
*** other method ***
*use the sideload function in recovery
*adb.exe sideload *rom.zip* in cmd
it says usb device descriptor failed...is it due to bad cable??
it says usb device descriptor failed...is it due to bad cable??
In recovery mode I am not able install any ROMS, theres the error Failed to mount /efs (Invalide argument)
I can only flash stock roms using odin, everything works on stock roms except for the wifi, after connecting/disconnecting multiple times, the wifi stops responding and wont work in the future
---------------------------------------------------------------------------------------------------------------------------------------------
(( SOLVED ))
First thing you should do, is to backup your EFS if you still have it.
I had mine but it wasn't mounting properly.
In order to back it up, please download terminal emulator on a rooted device and follow this video
I would try to back it up, even if you think the efs is messed up... worst case scenario is you end up where you started, not worse off.
---------------------------------------------------------------------------------------------------------------------------------------------
Your device needs to be rooted.
1.) Download SDK tools here - Scroll down to the bottom and "Get just the command line tools"
2.)Install TWRP , Find your device, download the .tar and flash it using ODIN
Boot in to recovery, in TWRP you want to go to mount, make sure system, esf are checked.
3. If you installed SDK tools, go to c:\android tools\SDK tools. hold shift and right click on the area inside the folder and select run command line from here.
4.) In cmd, type
Code:
ADB devices
ADB Shell
SU
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
5.) You should be good!!!
[Solved] Link2sd "mount warning" fix for all samsungs and android 5.1.1+ stock ROM
Hi.
I suppose many samsung and some sony devices have the problem "mount warning" displayed by Link2sd after installing it for manage second partition on external sd card. You do not have to generate mounting scripts again and again and restart system by Link2sd's own menu option to fix this. This solution lets to mount second partition automatic in boot phase.
Thank you to Warre101 for the idea.
If you want to use Link2sd you have to have rooted device. I did it on samsung galaxy tab 4 with stock ROM 5.1.1..
The best application for make all operations is Total Commander (TC).
1. Create subdirectory su.d in directory /system where you store your script, do it in left window of TC.
/system/su.d
2. Set 700 (RWX) permision for new created directory in Propertis TC's menu option . (Long tap directory name)
3. In the right window of TC open directory : /data/data/com.buak.Link2SD/files/
4. Copy the file init-link2sd.sh from right to left window. (If this file does not exist , create your own text file and paste the content from the example)
5. Change name of this file in the left window (/system/su.d directory) to 11link2sd
6. Copy renamed file back to right window and open it in Totalcmd-Editor (installed with TC)
7. Remove not needed text , the result should be:
Code:
#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2
8. Write changes and leave editor.
9. Copy changed file back to /system/su.d (left window). Overwrite existing file.
10. Set 700 (RWX) permision for this file . /system/su.d/11link2sd
11. Restart the device.
The new created script will mount partition needed by Link2sd for manage second partition on your external sd card during the booting phase of device/system .
This is not 100% sure if /su.d solution will work in every ROM. If you will find one not working, please comment here.
Help
Tomek0000 said:
Hi.
I suppose many samsung and some sony devices have the problem "mount warning" displayed by Link2sd after installing it for manage second partition on external sd card. You do not have to generate mounting scripts again and again and restart system by Link2sd's own menu option to fix this. This solution lets to mount second partition automatic in boot phase.
Thank you to Warre101 for the idea.
If you want to use Link2sd you have to have rooted device. I did it on samsung galaxy tab 4 with stock ROM 5.1.1..
The best application for make all operation is Total Commander (TC).
1. Create subdirectory su.d in directory /system where you store your script, do it in left window of TC.
/system/su.d
2. Set 700 (RWX) permision for new created directory in Propertis TC's menu option . (Long tap directory name)
3. In the right window of TC open directory : /data/data/com.buak.Link2SD/files/
4. Copy the file init-link2sd.sh from right to left window.
5. Change name of this file in the left window (/system/su.d directory) to 11link2sd
6. Copy renamed file back to right window and open it in Totalcmd-Editor (installed with TC)
7. Remove not needed text , the result should be:
Code:
#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2
8. Write changes and leave editor.
9. Copy changed file back to /system/su.d (left window). Overwrite existing file.
10. Set 700 (RWX) permision for this file . /system/su.d/11link2sd
The new created script will mount partition needed be Link2sd for manage second partition on your external sd card during the booting phase of device/system .
This is not 100% sure if /su.d solution will work in every ROM. If you will find one not working, please comment here.
Click to expand...
Click to collapse
in the directory : /data/data/com.buak.Link2SD/files/ , i cannot find the file init-link2sd.sh, only 2 files "link2sd_b and link2sd.log" and link2sd_b cannot be edited. My account haven't post 10 posts yet, so i cannot upload image for you to check.
can i creat the new init-link2sd.sh and continue your intructions ?
My device: Samsung galaxy A7 2016 (android 6.0.1 Rusia)
Hi _DoomD_ .
You should see this file if you installed current version of link2sd. If this file does not exist, you can use other text file or create new and copy the content from the example. If you use windows, do not use copy/paste. Linux uses different end line char. You does not do it on Tab 4 I suppose ... no mater , it will work on others if only your system will support new created /system/su.d/ .
Please let us know if it will work in android 6.0.1 .
Bye
Tomek0000 said:
Hi _DoomD_ .
You should see this file if you installed current version of link2sd. If this file does not exist, you can use other text file or create new and copy the content from the example. If you use windows, do not use copy/paste. Linux uses different end line char. You does not do it on Tab 4 I suppose ... no mater , it will work on others if only your system will support new created /system/su.d/ .
Please let us know if it will work in android 6.0.1 .
Bye
Click to expand...
Click to collapse
At step 8, i couldnot save changes. It gived me a writing error. I tried to change permission but it didnot work. I couldnot finish your intruction using totalcommand. I tried to use root explorer to edit and finished your intruction. But mount warning didnot fix.
I think your solution cannot work on android 6.0.1. Now i use apps2sd instead. Anyway, thanks for your help.
The problem with saveing exists in /system/... location. This is a reason i write abot coping renamed file back to link2sd's subdirectory and do all changes here. If your TC has root permision, it saves changes here. If this is not working, I do not know where is a source of problem.
File permision 700 lets the root do anything with file. TC with root permission uses root priv. for this operation. Maybe wrong owner of file, should be root...
A nifty thing one can do on a setup without built-in init.d, but recent SuperSU root with su.d, is to create and bind system/etc/init.d. I use a script in su.d to do this:
00000mounts:
Code:
mount -o bind,rw /su/su.d /system/etc/init.d;
In my case, I'm using systemless root, thus the '/su/su.d' location. Change it to your su.d folder location if it differs. This one line gives what amounts to standard init.d support, and any apps that create init.d scripts will see the /system/etc/init.d folder, use it, and their scripts end up in su.d and get executed on boot by SuperSU.
(And yes, this makes link2sd mounting work out of the box. Well, YMMV, but it worked for me.)
Filesystem for the second partition.
Code:
#!/system/bin/sh
sleep 4
mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2
The important thing is that if you are using different filesystem for the second partition you should change `ext2` after `mount -t` to whatever filesystem you use. Maybe someone has posted it already but I do not have a time to check it. In my case I use `ext4` so it looks like this:
Code:
#!/system/bin/sh
sleep 4
mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2
After this change Link2SD works perfectly on my Samsung Galaxy J3 (2016) aka SM-J320FN with stock Samsung ROM. Thanx.
@HostisSupremus
it has sense. I am always format it to ext2 on all my devices because of undelete support for ext2 and a lack of this support for ext4.
I found interesting fact on some of my devices . When you install link2sd, it wants to create initial script when you have to select your filesystem of second partition. I have always ext2, but some my devices works if I select ext2 and some do not. If do not, it works if I select ext4 , and it works with realy ext2 phisical partition. I do not know why .
dosent work for me, samsung galaxy tab a6 2016 android 5.1 rooted with magisk
This is what finally worked for me after three days of trying everything, thank you OP, you are my saviour
Difficult to believe after all these years of development link2sd does not verify init.d support.
I am using LOS 14.1 (Android 7.1) on my LG L70 and encounter the same mounting-failed problem.
I pull the file init-link2sd.sh out and it reads:
set +e
echo "$(date) mounting..." > $LOG
sleep 2
mount -t vfat -o rw,uid=1000,gid=1000,umask=133,dmask=0002 /dev/block/vold/public:179_66 /data/sdext2 1>>$LOG 2>>$LOG
mount -t vfat -o rw,uid=1000,gid=1000,umask=133,dmask=0002 /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
chmod 773 /data/dalvik-cache
Is there anything wrong? Why the 2nd partition can be mounted automatically at boot?
Also if there is a problem can I edit the file then push back directly?
I tried to edit the file init-link2sd.sh and pushed it back to phone. Not working...
thanks.
perfect..
my DEVICE J320G:good:
As a magisk user, I created a mount .sh script at /sbin/.magisk/img/.core/post-fs-data.d which seems to execute at boot time but not solve the issue