[s7270, s7272] [tut] unable to mount efs, how to fix ?? - Samsung Galaxy Ace 3

to the point
first, sory for my bad english
ok, go
prepare :
1. pc
2. usb cable
how to fix cant mount efs on samsung galaxy ace 3 s7270/s7272
1. flash cyanogenmod 11 , dont forget cwm and root your device, because we can use that for acces adb shell
2. go to the cwm and mount system, data and cache.
3. connect your handheld and pc
4. install driver adb
5. open adb in your pc and type this :
adb devices
adb shell
su
mke2fs /dev/block/mmcblk0p15
mount -w -t ext4 /dev/block/mmcblk0p15
reboot
Click to expand...
Click to collapse
credit :
- Allah SWT
- Muhammad SAW
- you
MY FACEBOOK : facebook.com/tankerstreet

Related

app2sd Step for step for any device (even 1.6 dount)

You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
I may need to edit something because I get this error on my M003 (Via8505) :
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
mount: mounting /dev/block//vold/179:2 on /system/sd failed: Invalid argument
busybox is /busybox/bin/busybox
tet
rm: can't remove '/etc/mount_sd.sh': No such file or directory
Partitioned SDcad with three partitions 1. 7gig Fat32 2. 96MB Swap 3. (1GB-96MB) as ext2
System will not complete boot now. Sits at initial boot screen then goes dark. Never get to animated logos.
Time to reflash ROM
Wanted swapfile. If it's the issue I'll remove it and try again
wolfilein said:
You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
Click to expand...
Click to collapse
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
i would like to know as well...
jcaf77 said:
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
Click to expand...
Click to collapse
i've been looking into this as well and was wondering the same thing as jcaf.. i have 0 space on this phone and would love to be able to install stuff onto sd card, thanks in advance
please help me..I got on Xperia X8..
busybox: not found
mkdir failed for /system/xbin, file exists
[2]
rm failed for /etc/mount_sd.sh, No such file or directory
sed: cannot create temp file /init.rccfoXyj: Read only file system
:::finished going reboot now:::
and he keeps restarting after SE logo..
Does it work on i5800 with ROOT?

[Q] Help setCPU on boot

Hello community,
Earlier I was messing with the voltages on setcpu, and I guess I ticked the box "set on boot" and now my phone wont boot pass the lockscreen. I don't want to wipe my phone if i don't need to.
I tried removing it via adb shell with these instructions i found:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
but i can't mount data. any help would be great. Thank you
Hello,
The SetCPU program can generate a "safe mode" script in case that happens.
It puts it into the root directory of the sdcard.
You have to generate it from within the program, it does not do it automatically.
I have attached the file I generated on my phone, I hope it can help you.
I think the instructions will be to boot in "red recovery" then flash the safe mode file to remove the "set on boot" flag.
Do not set on boot until you are sure the OC/UV settings do not crash your phone.
Good luck!
jayson94538 said:
Hello community,
Earlier I was messing with the voltages on setcpu, and I guess I ticked the box "set on boot" and now my phone wont boot pass the lockscreen. I don't want to wipe my phone if i don't need to.
I tried removing it via adb shell with these instructions i found:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
but i can't mount data. any help would be great. Thank you
Click to expand...
Click to collapse
A lot of the time the recovery isn't setup to properly use adb but maybe you just need to try a different command.
First see what is mounted and
ih what mount options by simply typing 'mount' in adb shell
Normally about halfway down you will see /dev/block/mmcblk0p2 /data make sure it is there and mounted read write. If it's not mounted try mounting it with 'mount -o rw /dev/block/mmcblk0p2 /data'
Or if it is mounted read only (which would be weird) try mount -o remount rw /dev/block/mmcblk0p2 /data
If that doesn't help you might need to do a nand droid backup, wipe data, reboot, create a safemode script like mentioned above, restore the nand backup and run the script in recovery.
Thank you very much for your replies. Helped me a ton. I got it fixed thanks to you guys.
Sent from my SAMSUNG-SGH-I997

help Root lenovo A60+

Help Me how to root this device.
lenovo A60+.
i'm try used how root A60 can't use.
Tolong dong bagaimana root Lenovo A60+. sudah mencoba tutorial yg A60 blm berhasil. pakai Oneclik juga gagal. adakah kawan dan saudaraku semua yg pernah root.
android 2.3.6
A60+_row_s310_120823 (build NUmber)
baseband
MAUI.11AMD.W11.50.V13.p7 2012/08/03
terima kasih bantuannya.
Go to Kaskus. There is a lounge for lenovo a60 there.
iswanptr18 said:
Go to Kaskus. There is a lounge for lenovo a60 there.
Click to expand...
Click to collapse
driver A60+ its differrent with A60
if you have linux as your system, you won't need a driver, but please do it at your own risks.
for first step, download SuperOneClick from shortfuse.org *it's for windows? yes, but it have adb for linux
make your device debug-able: Settings -> Applications -> Development -> Check USB Debug then connect it using USB to your PC
open your terminal on linux, mount to SuperOneClick directory
follow this step:
Code:
linux:~$ cd ADB
linux:~$ chmod 755 adblinux
linux:~$ ./adblinux devices
and it will show:
Code:
List of devices attached
4257323032BC4C34385A device
back to terminal and follow this step to copy all file that needed to exploit your android:
Code:
linux:~$ ./adblinux push Exploits/psneuter /data/local/tmp
linux:~$ ./adblinux push Root/su-v3 /data/local/tmp
linux:~$ ./adblinux push Root/Superuser.apk /data/local/tmp
after all files copied to your device, use shell on the droid
Code:
linux:~$ ./adblinux shell
$ cd /data/local/tmp
$ chmod 755 psneuter
$ ./psneuter
after that step above, USB connectivity will restarting for a seconds.
back to shell using ./adblinux shell on your terminal, and there will displaying # symbol if your root process is successful.
on the adb shell, type mount and find the /system mount point, for example: /dev/block/mtdblock0 on /system type yaffs2 (rw)
and then on adb shell, use this command below to finish your root process
Code:
# mount -o remount,rw /dev/block/mtdblock0 /system
# cat su-v3 > /system/bin/su
# cat Superuser.apk > /system/app/Superuser.apk
# chmod 06755 /system/bin/su
# chmod 0755 /system/app/Superuser.apk
check your app drawer, if you found Superuser on it, it was completed and successful. Good Luck!
Root Lenovo A60+ successfully
You need these tool:
1. Flash Tool: dropbox.com/s/f7gfyqtwyn5qkpa/ISO-8859-1__Flash tool.rar
2. Firmware Upgrade: mediafire.com/?ehiyzbdmlauo7i7
3. ROM MOD S317 by MAKIS V1.3the best one so far)
mediafire.com/download.php?u3ehud5ttldijca
4. Recovery: mediafire.com/?bo12ktkrrn57314
5. Driver: 4shared.com/archive/pimdjzA8/MT6575_USB_VCOM_drivers.html
Follow these step by step:
Step 1: Copy zip file ROM MOD S317 ( downloaded link number 3) and 2 file Recovery (link number 4) into the SD card
Step 2: Turn off the phone, take the battery out, plug usb cable and install Driver for the device (link number 5)
Step 3: unplug usb cable, insert the battery (not turn on the device yet). Run Flash Tool
Click scatter-loading. Browse to the MT6575_Android_scatter.txt file locate in the Firmware update extracted folder (link number 2). Tick all 9 options. Click Firmware-Upgrade
Step 4: Hold volume + key and plug the cable until the process running, release the key. Wait around 5 minutes until the green circle appear mean success
Step 5: After turn on the device we notice the default language are Chinese.
Install file Mobileuncle.apk that you copied in step 1.
Run the application and choose FLASH RECOVERY FROM SD CARD > select Recovery.img
The device will be restarted automatically
Step 6: Press Volume + during the device turned on to enter Recovery and do the following:
+ Wipe data/factory reset
+ Wipe cache partition
+ install zip from sdcard
+ choose zip from sdcard
Browse to the zip fle that you copied on step 1. wait for 30 seconds
Finished. Enjoy!
maihuuluong said:
You need these tool:
1. Flash Tool: dropbox.com/s/f7gfyqtwyn5qkpa/ISO-8859-1__Flash tool.rar
2. Firmware Upgrade: mediafire.com/?ehiyzbdmlauo7i7
3. ROM MOD S317 by MAKIS V1.3the best one so far)
mediafire.com/download.php?u3ehud5ttldijca
4. Recovery: mediafire.com/?bo12ktkrrn57314
5. Driver: 4shared.com/archive/pimdjzA8/MT6575_USB_VCOM_drivers.html
Follow these step by step:
Step 1: Copy zip file ROM MOD S317 ( downloaded link number 3) and 2 file Recovery (link number 4) into the SD card
Step 2: Turn off the phone, take the battery out, plug usb cable and install Driver for the device (link number 5)
Step 3: unplug usb cable, insert the battery (not turn on the device yet). Run Flash Tool
Click scatter-loading. Browse to the MT6575_Android_scatter.txt file locate in the Firmware update extracted folder (link number 2). Tick all 9 options. Click Firmware-Upgrade
Step 4: Hold volume + key and plug the cable until the process running, release the key. Wait around 5 minutes until the green circle appear mean success
Step 5: After turn on the device we notice the default language are Chinese.
Install file Mobileuncle.apk that you copied in step 1.
Run the application and choose FLASH RECOVERY FROM SD CARD > select Recovery.img
The device will be restarted automatically
Step 6: Press Volume + during the device turned on to enter Recovery and do the following:
+ Wipe data/factory reset
+ Wipe cache partition
+ install zip from sdcard
+ choose zip from sdcard
Browse to the zip fle that you copied on step 1. wait for 30 seconds
Finished. Enjoy!
Click to expand...
Click to collapse
I finished root my lenovo a60+ but i have a problem with recieve the message, it don't display my friend's name in contact, it only display +849xxx . Can you fix it ?
--- sorry about my english is bad
Lenovo A60+ ROM MOD S317
maihuuluong said:
3. ROM MOD S317 by MAKIS V1.3the best one so far)
Click to expand...
Click to collapse
Hi,
can anybody write me some more details about ROM MOD S317 by MAKIS V1.3? What languages does it include? Does it have all Google applications, etc ...
I cannot find any "developer" of this ROM site in Google and I would like to know if after installing of this rom there will be more empty space for apps installation.
I found only a discussion of Philipines guys (I suppose) on symbianized forum...
Phyt0n said:
Hi,
can anybody write me some more details about ROM MOD S317 by MAKIS V1.3? What languages does it include? Does it have all Google applications, etc ...
I cannot find any "developer" of this ROM site in Google and I would like to know if after installing of this rom there will be more empty space for apps installation.
I found only a discussion of Philipines guys (I suppose) on symbianized forum...
Click to expand...
Click to collapse
It's only in English (default) and Chinese.
Is there any way to add more languages to an Android ROM?
Or any other custom rom (or a way to build it for this phone)?

GT-n8010 (Wifi) Factory Mode

Hi,
Hope someone can figure this as its wrecking my brain.
I got an 8010 (wifi only version) a few days ago.
Did the clockwork and rooting and it was all working fine, until..
Booted it up this morning and it flashed a message 'Unfortunately, Factory Test has stopped. Factory Mode is ON!!' and gave me the 'calculator' program for putting in service codes.
I've checked the efs folder and its blank, no files. (I do not have a backup, yes I know I'm an idiot)
I've since tried flashing a number of roms, including stock. None of which have resolved the issue.
When using the stock recovery it gives me an error about being unable to mount /efs
From google it appears that the efs folder is to do with the imei and other areas. As mine is wifi only version should I even have this folder?
The note appears to work fine with the exception of having a lock screen, power off options etc.
thanks
BB
Have you tried to flash it over the PC with Odin and the Files from sammobile.com ??
Have you tried to repair the EFS with this Tool: http://forum.xda-developers.com/showthread.php?t=1308546 ?
update
Darkman_RS said:
Have you tried to flash it over the PC with Odin and the Files from sammobile.com ??
Have you tried to repair the EFS with this Tool: http://forum.xda-developers.com/showthread.php?t=1308546 ?
Click to expand...
Click to collapse
Hi,
I have tried with the N8010XWALG4_N8010XSAALG3_XSA from sammobile but am currently running the N8010-XXALH2-XAALH2-DBT-deodexed
Strangely enough I have just tried to connect with Kies, and it wont connect gives an error of 'No Sim Card inserted unable to continue communication'
I'm wondering if I've somehow confused my device into think its a 8000, when it is in fact an 8010.
I've tried the EFS Repair, it states that Locate /efs partition failed and can't locate any backups ;-((
I've just tried reflashing a stock rom via odin, selecting the re-partition and format efs section (got nothing to lose at this stage I guess)
I've also removed clockwork mod and gone back to stock recovery, which reads E:failed to mount /efs (Invalid arument)
would anyone have the .pit file / bootloader files? or are they built into the the pda rom?
thanks
BB
Pit file
Further testing has shown that the /efs partition does not exist or has become corrupt.
Would anyone have / or could make a pit file for a 32gb gt-8010?
Failing that would anyone know the terminal commands and dev location for making the /efs partition (make2fs ??)
Did you fixed the issue?
blue_bear said:
Further testing has shown that the /efs partition does not exist or has become corrupt.
Would anyone have / or could make a pit file for a 32gb gt-8010?
Failing that would anyone know the terminal commands and dev location for making the /efs partition (make2fs ??)
Click to expand...
Click to collapse
I have the same problem please advise?
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Hello
I am getting the same problem.
Odin can not find partition. But I cant go to CWM, only download mode is possible. Any other way to start, it goes to a white screen...
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
You made my day bro a lot of thanks its works for me thank u
ques
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
hi, I sent u a msg, if u dont read msgs on private, qoute me her so i can ask ya her.
bless
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
perfect
thx a lot
thank you sir, good job.
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
Hi,
how is the zip to be used?
YOSEFE said:
Hi,
how is the zip to be used?
Click to expand...
Click to collapse
it is just factorymode file set to on
use root enabled file manager and copy to /efs over writing current one. but it's just as easy or easer to just edit current file and change OFF to ON
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
@YOSEFE and @carl1961
hello
where I find this CWM and ANDROIDSDK ,,,??? ...she said " Assuming you have CWM installed on device and have androidsdk store on computer C: drive "
CWM what exactly is and where to find it ?
same for androidsdk where I find it ??
can you give me the real or good link plz ?? thanks
Hello,
CWM Recovery is found on www.clockworkmod.com
You need the one for your device.
You can Google search this and other file too. Be sure to read about CWM Recovery. It will trip knox on Samsung phones.
Sent from my SM-N910F using XDA Free mobile app
YOSEFE said:
Hello,
CWM Recovery is found on www.clockworkmod.com
You need the one for your device.
You can Google search this and other file too. Be sure to read about CWM Recovery. It will trip knox on Samsung phones.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
@YOSEFE
I'm sorry but what this i don't understand where is the link plz direct links for download ?? thanks
I can not go and install apps because the tablet does not open
my device is GT-8010 WIFI ONL
edits
i have downloaded this "recovery-clockwork-6.0.4.6-n8000 ' and "recovery-clockwork-6.0.4.6-n8013" it's ok or no ?? here http://www.clockworkmod.com/rommanager
if yes how to install ??
joan62 said:
@YOSEFE
I'm sorry but what this i don't understand where is the link plz direct links for download ?? thanks
I can not go and install apps because the tablet does not open
my device is GT-8010 WIFI ONL
edits
i have downloaded this "recovery-clockwork-6.0.4.6-n8000 ' and "recovery-clockwork-6.0.4.6-n8013" it's ok or no ?? here http://www.clockworkmod.com/rommanager
if yes how to install ??
Click to expand...
Click to collapse
your best using one for 8013
https://goo.im/devs/Darkman/Recoverys/N8013-CWM-noTouch-6.0.3.6-ODIN.zip/
carl1961 said:
your best using one for 8013
https://goo.im/devs/Darkman/Recoverys/N8013-CWM-noTouch-6.0.3.6-ODIN.zip/
Click to expand...
Click to collapse
+1...
Sent from my SM-N910F using XDA Free mobile app
@YOSEFE @carl1961
please help with the screnns is possible I'm sorry but i don't understand
I enter the ligne but the command not working
he said not find
the ANROIDSDK IN c : drive /android /android-sdk.... it's ok the intallation ?
Install on C:\. Use ODIN to install Recovery. Make sure your device is in download mode.
Sent from my SM-N910F using XDA Free mobile app

[Q] S4 Mini wont install ROMs

Hey.
I got a Samsung Galaxy S4 Mini (I9190 3G version) and the device is rooted. Unfortunately, I wiped all my roms from the SDcard and no:crying:w I cant access my device.
I trıed to connect my device to the PC, but the PC detects the device; but not the storage. Therefore, I cannot transfer files from the computer to the device. I tried mounting the /system, /data and /cache. I got CWM recorvery v6.0.3.5.
I searched a bıt on the internet and I found out that I were needed to use ADB. I downloaded and placed my ROM ın the MODDED_FILE folder. I open the CMD and change the ADB to recorvery. When I have changed it, I choose the file and I push the file from MODDED_FILE to the /sdcard section. When I push it, it give me this message:
" daemon not runningç starting ıt now on port 5037 "
" deaemon started successfully "
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /data
mkdir /data/media/rr
exit
exit
" # su
/sbin/sh: su: not found
" # mkdir /data/media/rr
" # exit
C:/Users/XXXX/Desktop/ff/tools/tmp1
----------------------------------------------------
pushing cm-10.2.1.3-serrano3gxx.zip to /data/media/rr ....
------------------------------------------------------
The ADB tool is stuck here. I have waited many hours and tried again and again.
The PC wont detect my storage.
I tried to set the external sdcard onto my computers SDCard slot, and placed the ROM in the external sdcard. I tried to install the zip, but it gives me the error;
(bad)
İnstallation aborted.
Thank you for fast answers.
needs
can921 said:
Hey.
I got a Samsung Galaxy S4 Mini (I9190 3G version) and the device is rooted. Unfortunately, I wiped all my roms from the SDcard and no:crying:w I cant access my device.
I trıed to connect my device to the PC, but the PC detects the device; but not the storage. Therefore, I cannot transfer files from the computer to the device. I tried mounting the /system, /data and /cache. I got CWM recorvery v6.0.3.5.
I searched a bıt on the internet and I found out that I were needed to use ADB. I downloaded and placed my ROM ın the MODDED_FILE folder. I open the CMD and change the ADB to recorvery. When I have changed it, I choose the file and I push the file from MODDED_FILE to the /sdcard section. When I push it, it give me this message:
" daemon not runningç starting ıt now on port 5037 "
" deaemon started successfully "
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /data
mkdir /data/media/rr
exit
exit
" # su
/sbin/sh: su: not found
" # mkdir /data/media/rr
" # exit
C:/Users/XXXX/Desktop/ff/tools/tmp1
----------------------------------------------------
pushing cm-10.2.1.3-serrano3gxx.zip to /data/media/rr ....
------------------------------------------------------
The ADB tool is stuck here. I have waited many hours and tried again and again.
The PC wont detect my storage.
I tried to set the external sdcard onto my computers SDCard slot, and placed the ROM in the external sdcard. I tried to install the zip, but it gives me the error;
(bad)
İnstallation aborted.
Thank you for fast answers.
Click to expand...
Click to collapse
have to installed cwm?
is odin able to detect your device?
[email protected] D€\/¡! said:
have to installed cwm?
is odin able to detect your device?
Click to expand...
Click to collapse
Hey.
Thank you for fast answer.
No, I do not get any message in Odin saying "Added" when plugging in my device. I have installed Samsung USB drivers too.
get it into download mode then try as odin work in download mode only

Categories

Resources