After having no issues with flashing ROM's, radios etc for over 6 months i've recently encountered a problem. When trying to update to CM7.0.3 from CM7.0.1 i had a system cannot mount error and was unable to flash any new ROM as a result. To try to fix this i formatted system and restored to a CM7 ROM and everything seemed fine. From here i can flash a ROM but when booting the new ROM it does not include gapps (even when selected to install from clockwork) and the system cannot mount error occurs again.
In short, everything seems to work fine currently but as soon as i flash a new ROM i get a system cannot mount error. The same thing happened with a CM nightly and so im thinking it is not just an isolated problem with a specific build.
Any help would be much appreciated. On a side note, on the restored ROM im currently using i have a LordMod Kernel installed, not sure if this would effect anything as when the problem was first encountered i did not.
Thanks.
Restore to a working ROM using your backups.
Boot into bootloader and then into fastboot.
Download ClockworkMod Recovery 3.0.2.8 from HERE
Unzip and run install-recovery-windows.bat. This will flash the latest recovery for you.
Now try again.
Yeh that worked perfectly, thanks alot.
Related
Hey Guys,
i have a big problem with my new S4 (i9505).
Ive rooted the Stockrom with Odin and then i flashed the Recovery, thats works well.
After this step ive tried to flash CM10.1.
The first boot works well, ive setup my phone, take a reboot and then i have a bootloop.
Ive go to the Recovery and i see that /data is destroyed.
Ive formating /data, flashed CM10.1 again, first boot works, second boot, /data is destroyed.
Then i flashed the prerooted XXUBF8-Firmware, flash the recovery, all works well. Then i flashed a alternative Kernel, my /data will be destroyed again. I have to format it, and to reflash the stock firmware.
My last try was to flash the minit-Framework. After this flash, i cant boot in my system, becaus my /data was destroyed.
I dont thought that my device is destroyed, because the Stock prerooted F8-Firmware (with custom recovery) works 2 weeks long without any problems (ive rebootet many times in the 2 weeks).
What i doing wrong?
And sorry for my bad english
Best regards
Just to follow you : what do you mean by "destroyed" ? Formatted partition ?
If so, try to do the following : flash stock ROM, then the recovery (I personally use Philz Touch based on CWM), do a factory wipe and then install the rom you want.
Hey,
thanks for answer.
When i have a bootloop and go to the recovery and want reflash a rom, the installer say: cannot mount /data, unknow partition. and then the setup breaks up.
After a format of the /data-Partition via Recovery, i can reflash the rom, and boot onetime.
Ive go "your way" and i have the some problem. After one Reboot my /data is destroyed.
Mmmm...in the Philz Touch recovery (based on ClockWorkMod but with a lot of improvements), there is an option called "wipe data for new rom install" or something similar... give it a try !
I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later
androidnoobi said:
I will try it
Ive tried it with CWM / TWRP and have the same error.
But i will try it ) *flash*
Till later
Click to expand...
Click to collapse
Good luck ! As you can normally flash stock rom, you don't seem to have hardware issues so don't worry
omg Oo
I dont believ it -.-
All the trouble are only fail from CWM and TWRP??
Now with Philz it works perfectly.
Ive installed Bobcat, reboot, flashed minit, reboot, flash another Kernel, reboot .. and it works Oo
Great )
Thanks
I tried flashing cyanogenmod's new nightly rom, then franco's kernel, then I flashed the .33/.84 hybrid radio (http://forum.xda-developers.com/showthread.php?t=2358931) and I now I am having problems.
When I go to twrp recovery to flash the CM rom I have on the internal storage the line does not move and it keeps saying updating partition. And for someone reason I cannot find the nandroid backup I did before doing this, it somehow got deleted. I can't access my internal storage to add another rom or the correct .48 radio to flash because I'm just stuck in the recovery. It also says I have no OS installed whenever I do a restart to recovery. It is even telling me that I am not root and that I need to install SuperuserSU sometimes.
I tried loading up the adb sideloader but don't know how that works.
Any help with this would be greatly appreciated.
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.
Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.
Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...
Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...
mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.
It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...
I don't know. It's worth a try.
If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.
So here is my problem i can't flash any custom rom i tried twrp cwm philz edition and the problem is the same i get stuck at* patching system image unconditionally at the very beginning of the blue line i tried with resurrection remix, slimrom, and other ROMs and when trying MIUI 8 i get an error couldn't mount system rw
Itried with adb sideload get stucked at 45%.
I e2fsck -y /dev/block/mmcblk0p23 wich is my system partition and fixed so many error but the problem stay the same ... i can flash a recovery or a kernel with no problem with TWRP the problem as i think when dealing with the system partition .. so im stuck with a stock rom that i flashed with odin btw who works great .. so is it my system partition messed up or the gpt table isnt right or is there a way to flash custom rom using odin
It could actually be the permissions. Other problem could be the recovery.
hi i know it's been a while since, but have you found a solution? I am getting exactly the same problem and tried everything possible. at the stage ready to sell it off ebay and upgrade if this doesn't work.
I had same problem with galaxy note 3 sprint variant and twrp 2.8.7.0 helped
If you are not getting twrp 2.8.7.0 try two or three lower versions
Don't use the latest twrp it won't work
1. Try to put custom rom to external storage microSD card or USB otg
2. If not helped 1. solution try older version TWRP 2.5.xx
This 2 solution help for me sometimes
You need to flash the latest TWRP.
Drhedphuk said:
You need to flash the latest TWRP.
Click to expand...
Click to collapse
Thanks, and I was on the latest already at the time of posting. Will try the two suggestions with getting the older versions of TWRP 2.8.7.0. Interestingly enough the CWM has done the same thing, as well as TWRP's sideload.
Will post back later.
tried all the possible versions of twrp, sideload, cwm, different roms, fixing permissions and formatting the partitions...no luck, still gets stuck at 45%. I guess it is time to give up and get myself a new xmas present.
So i was swapping roms: i booted into twrp, cleared cache and data and flashed my rom ( ResurrectionRemix-M-v5.6.0-20151213-wt88047.zip ) and Gapps.
i noticed flashing RR took just a minute and returned this message:
"unmount of /system failed; no such volume
script succeeded: result was [0.200000]"
after that the Gapps package flashed with no problem, but my phone does not boot properly.
Edit: i also tried different twrp versions, but i got the same result with each of them
It does still boot to fastboot, but i wasn't able to get into android.
i read something about cf.lumen drivers causing this kind of error while swapping roms, but i don't know if they were there in the first place or how to uninstall them.
ap29600 said:
So i was swapping roms: i booted into twrp, cleared cache and data and flashed my rom ( ResurrectionRemix-M-v5.6.0-20151213-wt88047.zip ) and Gapps.
i noticed flashing RR took just a minute and returned this message:
"unmount of /system failed; no such volume
script succeeded: result was [0.200000]"
after that the Gapps package flashed with no problem, but my phone does not boot properly.
Edit: i also tried different twrp versions, but i got the same result with each of them
It does still boot to fastboot, but i wasn't able to get into android.
i read something about cf.lumen drivers causing this kind of error while swapping roms, but i don't know if they were there in the first place or how to uninstall them.
Click to expand...
Click to collapse
Good night, try to flash miui. Then install twrp 3-1 and ROM. But first go to the Lineageos tag and download the modem and flash. Then try ROM again.
I had MIUI installed before the Rom flash, and i was using fastboot ti boot into twrp without actually flashing it.
I eventually solved my issue by flashing a different rom, so i think the one i was using was corrupted or Just bugged.
Thanks for the support.