Hello,
I've tried time by time and i can't make a backup on any rom
ive tried the squadzone's recovery and anothers as THIS and had no success
Everytime
Backing up system...
Can't mount /system!
Click to expand...
Click to collapse
whyy? its possible to backup any rom on SGM ?? (ive tried with stock and custom too)
Thanks for help,
hreyit said:
Hello,
I've tried time by time and i can't make a backup on any rom
ive tried the squadzone's recovery and anothers as THIS and had no success
Everytime
whyy? its possible to backup any rom on SGM ?? (ive tried with stock and custom too)
Thanks for help,
Click to expand...
Click to collapse
the error is stating that while backing up recovery is not able to mount /system
try to mount /system before backing up rom. it can be mounted from mount and storage option
try to reflash latest cwm which is 5.0.2.8
try to wipe cache and dalvik cache before backing up
I think this problem is with stock ROM Or GB.
I was Flashing Emanom v5
I want to backup GB to restore when in need but, CWM v4 throws this errorBackup error
E: Can't open /cache/recovery/log
I Prepared:
1, Flashed GB through odin without SD mounted and android booted.(with sound in Samsung Logo)
2, Changed some Settings in Android
2a, Rebooted again with Mounted SD(to check if booting ssuccesfully with partitioned SD)
3, Now Rebooted to downloading mode
4, Flashed CMW Recovery v4
4a, Here Android succesfully booted, then I Rebooted in CWM.
5, In CWM, it show the error- E: Can't open /cache/recovery/log
6, when I tried to backup it doesn't
7, Wiped data + Cache
8, Re-tried to backup but it throws that err again.
9, Now I booted Android it does'nt boots(show Samsung Logo but no Sound and boot loops)
So I left off and Flashed Emanom
with whole process skipping steps 5-9
Here With Emanom v5, in CWM Recovery
That Error Again but when I backed up successufully towing error again.
Now what Step I left or any wrong do I did.
If backup-ing GB is possible then we could just restore it to flash any custom ROM without flashing through Odin and requirement of computer.
Sent from xda premium
Stock ROMs can't be backed up right ?
Even if you backed up, its not able to restore.
coolsandie said:
Stock ROMs can't be backed up right ?
Even if you backed up, its not able to restore.
Click to expand...
Click to collapse
if it is backed up i think it can be restored easily.
but to make it compatible with stock rom the person(squad) who ported the recovery needed to make the recovery compatible with rfs partition but its compatible with ext partition
Related
Hello,
I flashed MIUI and it was very buggy for me, all apps were crashing and so on. Then i decided to flash Darky 10.1.
Followed the tutorial without any issues, but after this i got no signal. Snooped around the OS and found out it did not see my sdcard. After booting in recovery mode I saw that it could not mount the efs partition.
If i try to mount it via shell i get:
Code:
# mount /dev/block/stl4 /efs
mount: mounting /dev/block/stl4 on /efs failed: Invalid argument
I unfortunetly have no backup of the efs partition.
Did anyone else experience this problem or has a fix for this?
Push. I have that problem too... I was on Darkys ROM for some months without any flashing problems. Now i wanted to change from Darkys ROM 10.1 (Gingerbread 2.3.4) to Galnet MIUI. I had to downgrade to Froyo and then install the CWM zip in CWM. This was NOT succesful. It always says "Installation aborted (Status 7)". Then i tried to install CyanogenMod 7.1. Upgraded to Gingerbread Stock with CWM 3 and when i first flashed it via ODIN the phone first booted in the standart Android CWM display (dont know the name sry). The phone automatically formated cache etc. but then it showed me 2 times "/efs is not mounted". I was able to boot and to open CWM but ALWAYS when i want to install ANY CWM ROM it shows me the message with Status 7 ...
How can i mount /efs again and make CWM ROM Flashing able again?
Thank you.
I was using CM10.1 RC1 by bieltv.3. After he updated the the rom to RC2 I flashed it today after taking a back up.
I then restored the apps I used to have on my SD card, rebooted and moved to SD. Then I restored the remaining apps (twitter, swiftkey etc). The phone froze when i tried to set un check the notification for swiftkey. I waited for sometime and removed the battery.
On restart it loaded until my lock screen. I was waiting for dash clock to load but it didn't only to find out my phone had frozen again. Tried this twice without any success. So i reflashed the ROM after wiping cache/ data/ system/ dalvik cache. It now got stuck on the screen where i select the language.
I then decided to restore the backup taken from CWM 5.2.0.6. While restoring .android_secure it failed.
When i tried to wipe data it got stuck while wiping .android_secure.
Then I reflashed CWM and then wiped again. This time the wipe worked.
Then i tried flashing the RC1 that I had been running all this time. It too got stuck on the language selection screen.
Wiped everything again and now I'm trying to restore the CM10.1 Backup again. Currenly it's been waiting on restoring .android_secure for the last 15 mins. Not really sure what to do.
I'm currently out of ideas. Need help
Update: I tried to do an advanced restore and only restored the boot and system but it still gets stuck and then reboots/ or just stays stuck. it does unfreeze for a few seconds some times but then freezes again :/
after I wipe the dalvik cache if i select show log i get
failed to mount /dev/block/mmcblk0p2 (no such file or directory)
...
...
...
....
After reading about it I have come to the conclusion that my Internal SD partition is corrupt / damage since I can't mount SD-EXT
Am I correct?
iFeelYouJohanna said:
I was using CM10.1 RC1 by bieltv.3. After he updated the the rom to RC2 I flashed it today after taking a back up.
I then restored the apps I used to have on my SD card, rebooted and moved to SD. Then I restored the remaining apps (twitter, swiftkey etc). The phone froze when i tried to set un check the notification for swiftkey. I waited for sometime and removed the battery.
On restart it loaded until my lock screen. I was waiting for dash clock to load but it didn't only to find out my phone had frozen again. Tried this twice without any success. So i reflashed the ROM after wiping cache/ data/ system/ dalvik cache. It now got stuck on the screen where i select the language.
I then decided to restore the backup taken from CWM 5.2.0.6. While restoring .android_secure it failed.
When i tried to wipe data it got stuck while wiping .android_secure.
Then I reflashed CWM and then wiped again. This time the wipe worked.
Then i tried flashing the RC1 that I had been running all this time. It too got stuck on the language selection screen.
Wiped everything again and now I'm trying to restore the CM10.1 Backup again. Currenly it's been waiting on restoring .android_secure for the last 15 mins. Not really sure what to do.
I'm currently out of ideas. Need help
Update: I tried to do an advanced restore and only restored the boot and system but it still gets stuck and then reboots/ or just stays stuck. it does unfreeze for a few seconds some times but then freezes again :/
after I wipe the dalvik cache if i select show log i get
failed to mount /dev/block/mmcblk0p2 (no such file or directory)
...
...
...
....
After reading about it I have come to the conclusion that my Internal SD partition is corrupt / damage since I can't mount SD-EXT
Am I correct?
Click to expand...
Click to collapse
Did you try to fash a Stock via Odin, then flash root + cwn 5.0.2.6. fix and finally flash CM10.1 again and restore your back up?
I think your partitions are corrupted... Were you using sd-ext scripts? as int2ext? wel try with the first method
Viper The Ripper said:
Did you try to fash a Stock via Odin, then flash root + cwn 5.0.2.6. fix and finally flash CM10.1 again and restore your back up?
I think your partitions are corrupted... Were you using sd-ext scripts? as int2ext? wel try with the first method
Click to expand...
Click to collapse
I wasn't using any scripts.
I used odin and flashed the stock rom. Phone starts up goes to unlock screen and all looks fine. after about 1 min the phone starts to lag very very badly until it stops responding and then shuts down completely.
Didn't root or flash cwm still.
Maybe the files got corrupted somehow. Try downloading the ROM again and use another SD card.
That might fix it.
Good luck.
iFeelYouJohanna said:
I wasn't using any scripts.
I used odin and flashed the stock rom. Phone starts up goes to unlock screen and all looks fine. after about 1 min the phone starts to lag very very badly until it stops responding and then shuts down completely.
Didn't root or flash cwm still.
Click to expand...
Click to collapse
Try doing wipes after odin flashing
Viper The Ripper said:
Try doing wipes after odin flashing
Click to expand...
Click to collapse
I forgot to mention i did wipe data and cache after flashing via odin. So that didn't help
Edit- ok I noticed my sd card wasn't being detected so I removed it and rebooted and everything seems to be fine :/
Can a faulty sd card slow down/ make your phone become unresponsive?
iFeelYouJohanna said:
I forgot to mention i did wipe data and cache after flashing via odin. So that didn't help
Click to expand...
Click to collapse
And dalvik cache?
nikwen said:
And dalvik cache?
Click to expand...
Click to collapse
Yeah root it and flash cwm and then wipe dalvik cache if not try to flash a custom stock rom after odin fashing e.i. rooted and cwm installed after odin flash
Viper The Ripper said:
Yeah root it and flash cwm and then wipe dalvik cache
Click to expand...
Click to collapse
And afterwards do that: (also use a fresh downloaded CWM)
nikwen said:
Maybe the files got corrupted somehow. Try downloading the ROM again and use another SD card.
That might fix it.
Good luck.
Click to expand...
Click to collapse
Final Update:
The whole thing was caused by my SD card. I should have checked how the phone responds to with the SD card removed.
I'm suspecting it must have happened while using Titanium backup. Good thing I managed to get most of the titanium back up files copied to my PC so I can restore them later.
Things I overlooked: the phone only locked up a few seconds after it starts (i.e. gets to the lock screen). That's when the phone detects the SD card.
I need to figure out how to format the card now since I don't have another method to connect to the PC and the phone isn't detecting the card.
Thanks for all the help.
Is it detecting the card in CWM? If so, you could format it that way.
I got a miniSD card adapter with my phone? Did you not?
iFeelYouJohanna said:
Final Update:
The whole thing was caused by my SD card. I should have checked how the phone responds to with the SD card removed.
I'm suspecting it must have happened while using Titanium backup. Good thing I managed to get most of the titanium back up files copied to my PC so I can restore them later.
Things I overlooked: the phone only locked up a few seconds after it starts (i.e. gets to the lock screen). That's when the phone detects the SD card.
I need to figure out how to format the card now since I don't have another method to connect to the PC and the phone isn't detecting the card.
Thanks for all the help.
Click to expand...
Click to collapse
so your Sd card was corrupted, use a micro sd reader
Managed to format the SD by mounting USB using CWM.
CWM refused to format saying the card was read only. but the pc did a quick format
iFeelYouJohanna said:
Managed to format the SD by mounting USB using CWM.
CWM refused to format saying the card was read only. but the pc did a quick format
Click to expand...
Click to collapse
Great. :good:
Hi!
I have a little problem with my SGS. I used from a month CM 10.1 ROM and Semaphore 2.9.3 kernel. Today phone start up and after a few minutes restart into recovery. I tried reinstall ROM, recover backup etc but has no effects. I tried also flash Samsung JVP ROM (3 files, with re-partition) but phone restart like boot loop problem.... After all that i tried wipe all data/factory reset, format every partition. No errors shows in CWM but all data still are on partition data :/
Summary i can't format/erase data from partition:
data,
cache,
datadata,
sdcard (internal)
In CWM all partition format show results "Done" but data still are there.
But I can flash new system into system or new kernel into boot partition.
Any idea without NAND is dead ?
got pic on error? maybe dbdata
Sent from my GT-I9000 using xda premium
Ok...
Actually a I have lastest CM 10.1 and Semaphore kernel 3.0.0
When I tired CWM/Mounts and Starage Menu/format /data
See first attachment
After I go to CWM/advanced/show log:
See second attachment
And data on partition /data are still there...
Hi,
could the warning in the second screenshot be the Problem????
Okay it's only a warning not an error...but maybe that is the prob...
I searched about this warring "Wipe via secure discard failed, used discard" but I not found anything useful.
That's Bad :crying:
Another idea: Flashing back to an older Version of CWM-Recovery and then testing if data partition can be cleaned up...
Another question is : what means the Option "Wipe via secure discard"??? what is the effect, anyone knows???
freakymod2120 said:
That's Bad :crying:
Another idea: Flashing back to an older Version of CWM-Recovery and then testing if data partition can be cleaned up...
Click to expand...
Click to collapse
I tried that method clean up, factory reset/format with stock JPU and CF-Root-XX_OXA_JVP-v3.7-CWM3RFS, but no effects
I tried also with another Samsung ROM 2.1, 2.2 and 2.3...
Hi i have a problem with my galaxy note, i rooted my phone with philz touch 5 and i was trying to install a kitkat rom
and it was giving me an error, after a lot of research i found that i needed a newer version of cwm so i found philz touch 6.25
i went to my sd card and dropped the thing there and i installed it with install zip from sd card.
after that i installed asylum rom and when i rebooted it stuck on boot screen,went back to cwm and did factory wipe started again nothing ,
installed new rom this time slimkat again stuck on boot screen after that lightning rom nothing stuck tried stock rom with odin nothing agin when i start my phone it stays on cyanogenmod boot screen.
can anyone help me im new to this stuff
sorry for my english
and thanks
Flash raw r4 kernel from recovery. Then reboot into recovery. Go to mounts and storage and format system, data and cache. Then flash the new rom.
nokiamodeln91 said:
Flash raw r4 kernel from recovery. Then reboot into recovery. Go to mounts and storage and format system, data and cache. Then flash the new rom.
Click to expand...
Click to collapse
here is what i did
1.downloaded raw r4 kernel and add to sd card
2.boot to philz recovery install raw r4 kernel
3.reboot to recovery now is CWM-BASED RECOVERY V6.0.4.4
4.went to mounts and storage and format system data cache
5.installed sweetrom v11.1_LTA rebooted
6.stuck on boot screen
7.tested omni rom again the same it stays on boot screen
when i try to install from the sd card i see that there is an extra partition sd card0 and sd card1 on the first partition it contains lost dir,twrp/,clockwokmod and the other one my roms shouldnt be only one????
any other idea?
One is your internal and other is external sd. When you say stuck on boot screen? What exactly do you see? The Samsung flashing logo? Of that then it takes a while to boot.
tsehos said:
here is what i did
1.downloaded raw r4 kernel and add to sd card
2.boot to philz recovery install raw r4 kernel
3.reboot to recovery now is CWM-BASED RECOVERY V6.0.4.4
4.went to mounts and storage and format system data cache
5.installed sweetrom v11.1_LTA rebooted
6.stuck on boot screen
7.tested omni rom again the same it stays on boot screen
when i try to install from the sd card i see that there is an extra partition sd card0 and sd card1 on the first partition it contains lost dir,twrp/,clockwokmod and the other one my roms shouldnt be only one????
any other idea?
Click to expand...
Click to collapse
update
i tried again flashing a stock rom usin odin once it finished it went to boot logo and after 20 seconds the logo restarted all it does is restarting the samsung logo,i went to recovery and it shows a dead android and with red letters E: failed to mount /efs (invalid argument) tried factory reset nothing.
Failed to mount efs? Hmm.. Check in your internal sd card if you have any file named efs backup or efs auto backup of 20 MB in size?
nokiamodeln91 said:
Failed to mount efs? Hmm.. Check in your internal sd card if you have any file named efs backup or efs auto backup of 20 MB in size?
Click to expand...
Click to collapse
how do i do that i can only mount ext sd card in cwm and and when i go to mounts and storage and try to mount efs i get error mounting efs and i dont have a back up for that
tsehos said:
here is what i did
1.downloaded raw r4 kernel and add to sd card
2.boot to philz recovery install raw r4 kernel
3.reboot to recovery now is CWM-BASED RECOVERY V6.0.4.4
4.went to mounts and storage and format system data cache
5.installed sweetrom v11.1_LTA rebooted
6.stuck on boot screen
7.tested omni rom again the same it stays on boot screen
when i try to install from the sd card i see that there is an extra partition sd card0 and sd card1 on the first partition it contains lost dir,twrp/,clockwokmod and the other one my roms shouldnt be only one????
any other idea?
Click to expand...
Click to collapse
Sorry I think you are confused...You have flashed raw kernel for 4.4 roms, then you've installed sweetrom that is 4.1...I'm sure that you stuck on boot. Search for a 4.4x rom, flash raw kernel and you'll see will work. with raw, internal sdcard is /emmc. If you want to install sweetrom you have to flash Philz kernel. See roms threads.
jsdroid said:
Sorry I think you are confused...You have flashed raw kernel for 4.4 roms, then you've installed sweetrom that is 4.1...I'm sure that you stuck on boot. Search for a 4.4x rom, flash raw kernel and you'll see will work. with raw, internal sdcard is /emmc. If you want to install sweetrom you have to flash Philz kernel. See roms threads.
Click to expand...
Click to collapse
i tried with slimkat and asylum omni both are 4.4 and its the same problem somehow i messed up and now i flashed a stock rom with odin
and it stuck samsung logo and when i go into recovery it gives me with red letter e:failed to mount efs i read somewhere that i have to take to samsung service to fix if its possible
Flash PhilZ kernel again and then flash aroma file manager to check if there is an efs backup in the internal storage.
nokiamodeln91 said:
Flash PhilZ kernel again and then flash aroma file manager to check if there is an efs backup in the internal storage.
Click to expand...
Click to collapse
done but there a lot of files i can only look in root do you know where to look exactly?????
tsehos said:
done but there a lot of files i can only look in root do you know where to look exactly?????
Click to expand...
Click to collapse
Usually stored in the root of internal SD,, also in clockworkmod folder.
nokiamodeln91 said:
Usually stored in the root of internal SD,, also in clockworkmod folder.
Click to expand...
Click to collapse
internal sd 0 files
the clockworkmod is in sdcard and there is only a screenshots folder
i have searched a little bit but i dont see the file
tsehos said:
internal sd 0 files
the clockworkmod is in sdcard and there is only a screenshots folder
i have searched a little bit but i dont see the file
Click to expand...
Click to collapse
update i have followed this and tried it on my phone and it works but i have to check
if there is a problem with my imei i can make calls send messages and everything
here is the guide http://www.youtube.com/watch?v=xJMJLdzHaAY please watch and tell me if there
will be a problem with something
Try wipeing data and cache after flashing stock rom via odin
tsehos said:
update
i tried again flashing a stock rom usin odin once it finished it went to boot logo and after 20 seconds the logo restarted all it does is restarting the samsung logo,i went to recovery and it shows a dead android and with red letters E: failed to mount /efs (invalid argument) tried factory reset nothing.
Click to expand...
Click to collapse
after flashing with odin you should wipe data and cache then reboot!
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.
alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.