I recently noticed a problem in the red cwm I am running. I flashed the gtg community kernel over stock to get access to cwm and be able to flash a custom rom like I normally do. I have flashed a few custom roms recently and noticed that when i boot into cwm recovery I cant mount / unmount the system. I always get Error mounting system. What can be the problem. I have tried different roms and kernels and keep getting this error. Thanks for the help.
Does any one have any suggestions as it does this with everyrom I try. I cant unmount/mount the system in cwm . I like to try things from uot kitchen but with out doing this some things go unthemed.
Related
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to restore my phone. After trying different tars and making tar with nandroid images I found a tar file of {EI20} 2.3.5. I tried it an it boot up well. I install a voodoo CWM and let me restore! Though the phone is not activated on the cdma network, at least its on factory state with the own carrier's software. Its only a matter of them activating the phone back.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
lilizblack said:
I've just rooted a Showcase and I followed Cyanogen mod guide for installing their rom. Everything went smooth. Minutes later I started having problems with signal. Since I did a nandroid backup I decided to restore. Everything said completed successfully. When I reboot it stuck into boot loop.
I went back into recovery and tried to wipe cache and dalvik. Error mounting cache. Error mounting system. Error mounting /datadata
I tried to go back to cyanogen and the same Error mounting cache. Error mounting system. Error mounting /datadata. I changed into various clockwork mod versions and the same.
I tried restoring on two versions with Odin and I dont get any logo at all but straight into recovery. saying invalid argument and the same Error mounting cache. Error mounting system. Error mounting /datadata
Did cyanogen changed partition ext (MTD/BML?)? Im out of ideas. I spent the entire day yesterday checking different forums and trying out anything within the showcase area to make this phone boot.
I even tried to find a way to manually restore with the nandroid backup but the partitions wont mount. The only ones that does are /boot and /data and the /sdcard.
The nandroid backup is there. All i need is to be able to restore. The clockworkmod 4 I have now doesn't activate adb so I cant access the phone via command prompt.
UPDATE: I managed to boot it up with a Verizon Odin tar but the Phone is from another carrier so it wont go past the activate screen. I tried flashing the clockworkmod and restoring but im getting the same error mount on system. Any ideas?
Click to expand...
Click to collapse
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
jbreakfield said:
Which carrier is the Showcase from? You are correct, CyanogenMod changes the partition ext to MTD.
You're probably going to need stock Odin files for your carrier, so that you can repartition back to stock.
Did you take a look at the guide HERE? A lot of info, but explains everything.
Click to expand...
Click to collapse
I already tried it and get the invalid argument error. no boot image and straight to recovery
lilizblack said:
The carrier is Open Mobile; its a local carrier on PR. The is no way to get an odin tar of this company unless you take another showcase and via command prompt extract it directly from the phone or another user who did it share it over the internet. The only way I can make the restore say completed is flashing verzon odin tar, flashing CWM 4, flashing cyanogen and rebooting into recovery via cyanogen. I noticed the flashed CWM via odin is only good for flashing cyanogen. It would give allot of error. If I boot into recovery via cyanogen rom I get a CWM 5.0 instead of 4 (when booting on key commands). The CWM 5.0 allow me to restore nandroid and mount partitions but when i reboot device Im stuck at the samsung logo. I left it a few minutes and nothing.
Do you think an MTD to BML converter in a flashable zip will help booting my restore?
Click to expand...
Click to collapse
When you flash the verizon odin tar file, are you using an .pit file, and checking repartition? This will get you converted back to BML. The tar file must be a full flash for the repartition to work.
So I am probably breaking a rule but you need help go over to www.rootwiki.com . Go to there forums and look there they have a bunch of people over there developing for the showcase.
Sent from my SCH-I500 using Xparent Blue Tapatalk 2
Hi, i'm a relative noob to rooting and rom flashing but i know the basics and have successfully installed cyanogen on other phones and devices in the past. So essentially I am trying to install jellybean on my infuse 4g (on rogers). I begun with this guide (http://forum.xda-developers.com/showthread.php?t=1776129) but and gotten stuck trying to install entropy's cm9 (http://forum.xda-developers.com/showthread.php?t=1601844). i flashed the rom and then formatted the data, system and cache, but then realized forgot to put the ICS gapps bundle on the sd card before i started. So i flashed once, did the formatting of data, system, cache, then attempted to boot and now im stuck at the samsung screen. It just hangs at that screen every time i try to boot. I have the red CWM screen and can get to CWM, but whenever i try to mount the SD it does not show up on my PC (Mac too) so i can't put any thing on it to flash and fix it.. when i attempt to flash the cm9 rom again it says [bad] and aborts. If anyone could help me out in where to go from here. I have done some reading about setting up ADB to push a rom to it, but will that work if i cant even mount the sd in the first place. CWM allows me to mount and say it should be active but i get nothing on the pc. Also which rom should i use to fix it.. also i follwoed the instructions and have Qksters IMEI backup script run (I'm not exactly sure what this does).
Thanks
phillyjevs said:
Hi, i'm a relative noob to rooting and rom flashing but i know the basics and have successfully installed cyanogen on other phones and devices in the past. So essentially I am trying to install jellybean on my infuse 4g (on rogers). I begun with this guide (http://forum.xda-developers.com/showthread.php?t=1776129) but and gotten stuck trying to install entropy's cm9 (http://forum.xda-developers.com/showthread.php?t=1601844). i flashed the rom and then formatted the data, system and cache, but then realized forgot to put the ICS gapps bundle on the sd card before i started. So i flashed once, did the formatting of data, system, cache, then attempted to boot and now im stuck at the samsung screen. It just hangs at that screen every time i try to boot. I have the red CWM screen and can get to CWM, but whenever i try to mount the SD it does not show up on my PC (Mac too) so i can't put any thing on it to flash and fix it.. when i attempt to flash the cm9 rom again it says [bad] and aborts. If anyone could help me out in where to go from here. I have done some reading about setting up ADB to push a rom to it, but will that work if i cant even mount the sd in the first place. CWM allows me to mount and say it should be active but i get nothing on the pc. Also which rom should i use to fix it.. also i follwoed the instructions and have Qksters IMEI backup script run (I'm not exactly sure what this does).
Thanks
Click to expand...
Click to collapse
the samsung boot loop is to be expected when flashing cm9. If CM9 is not your target Rom, then having GApps on your SD card or not doesnt matter. Carefully refollow the step in CM9 then continue onto cm10. After you do the three finger salute, your cwm will be blue. if all else fails, odin back to stock and start over..just make sure you have GApps when you reach the time to flash cm10.
You need to go to mount then unmount the first set. Then re flashee infinitum.
Sent from my SGH-I997 using xda premium
Hello, I know I am an idiot for this.
But I tried to create my own rom, following a guide carefully.
It was a miui rom and I skipped only one thing, because I couldn't find it. I don't think it was anything important that could have caused my dilemma.
To get to the point.
I have the Nexus S 4G
Using TWRP Recovery
I made a backup of my stock rom
I flashed the Rom(I created) and it failed to flash.
So I tried to restore my Stock rom. Once it said it completed.
I tried to reboot and it just brought me back to bootloader screen.
I'm panicking now.
So I use my root toolkit to flash CWM recovery and tried to install a
new rom on my phone, but it's not working
when I try to boot up into a new rom, all I get is a black screen.
HELP PLEASE. ((
edit: when I went back into TWRP to check the log, it said "can't mount SD"
and I went to MOUNT and Sdcard was mounted..
So here's what happened : I flashed the SlimKat 4.4.2 on this phone (SGS4G) using CWM, everything worked, and CWM changed to TWRP. But I didn't like the performance so I decided to go back to CM 10.1 which I have backed up. To restore it I had to re-install CWM, so what I did is installing AntonX Basic with a twist BML/Stock Rom, using the Heimdall one-click package, and I was presented with a red CWM -Vodoo lag fix- 5.0-. and some commands that says cannot read -I can't remember exactly but it has to do with the SD card-. So I went to restore, restored the CM 10.1, and then every time I boot, I get the Galaxy S 4G screen, then Google, then it loops back again from the Galaxy screen. I tried booting up to recovery, but all that happens is I get the orange (6.0.-) CWM with it's logo in the center, and before it loads it starts looping again.
Please help guys !
EDIT :
The things that appear on CWM are :
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
hope this helps !
red cwm? you need Blue CWM to restore.
Oh right. I've just fixed it, flashed the stock KJ6 Rom via Odin, then flashed AntonX kernel with the heimdall one-click to get CWM, flashed the Beanstalk ROM, and things are going great so far !
But the FFC is screwed up (see the attachment)
Tried flashing a different kernel but no luck. Any ideas on how to fix that ?
Hi,
So I have TWRP from the toolkit. And I previously had Mokee latest, then I switched to MIUI7 5.11.14(latest).
Now I downloaded Resurrection Remix, and before flashing it I tried to flash MIUI V6.6.10.0.LXIMICF, which failed spectacularly displaying the error below:
mount : failed to mount /dev/block//bootdevice/by-name/userdata at /data : Device or resource busy.
mount : failed to mount /dev/block//bootdevice/by-name/system at /system: Device or resource busy.
the updater script failed to execute
This happens with me quite often when I try to switch between MIUI and CM based ROMs.
And I dunno how this happens but I keep trying to flash MIUI and then reboot if it fails and then wipe "Cache, data, dalvik cache, system" again and flash MIUI again, and sometimes it takes 2-3 tries and it flashes., the script succeeds.
The same happened today
-had MIUI 5.11.14, rebooted to recovery(TWRP)
-wiped [system, data, dalvik cache, cache]
-tried to flash MIUI 6.6.10, it failed
-tried to flash RR, it succeeded but the ROM acted weirdly. The screen would turn off and the phone won't respond. So no luck
-rebooted wiped [system, data, dalvik cache, cache]
-tried to flash MIUI 6.6.10, it failed
-rebooted and factory reset performed. Tried to flash MIUI 6.6.10, it failed
-rebooted again and factory reset performed. flashed MIUI successfully, then performed factory reset, and flashed RR, and successfully booted up the ROM. Finally
This type of flash failure is not limited to the 6.6.10, it happens with 6.7.2 and also 5.8.11(dev version)
Can someone tell me why this happens, and does it happen on everyone's Mi4i? Or am I doing something wrong?
I know its long but I had to explain what I did properly.
Friend, same situation here!
I have my mi4i since august and i try every custom and official/developer rom. Every time i try a rom i have the same problems as you. I never posted because i thought i m doing something wrong but i am very experienced guy, doing such stuff many years, and i couldn't beleave that. Btw, i have the same strange behavior from twrp & flashing roms on my mi4i, and i can't understand what's wrong...
anurox2 said:
Hi,
mount : failed to mount /dev/block//bootdevice/by-name/userdata at /data : Device or resource busy.
mount : failed to mount /dev/block//bootdevice/by-name/system at /system: Device or resource busy.
the updater script failed to execute
Click to expand...
Click to collapse
Thats because you tried to flash miui recovery rom using TWRP. You must flash miui rom with miui stock recovery only. This is why I highly recommended people who wants to try custom ROM to only 'fastboot boot twrp.img' rather than installing it permanently because you can easily flash the miui stock rom again next time u want to back to miui rom.
Unlike twrp, miui 6 recovery is not the same with miui 7. If you tried to flash stock recovery using fastboot flash recovery for different version of miui, it will not work.
Unless you prefer to stay under custom ROM, I highly recommend that you keep your stock recovery intact.
yumm91 said:
Thats because you tried to flash miui recovery rom using TWRP. You must flash miui rom with miui stock recovery only. This is why I highly recommended people who wants to try custom ROM to only 'fastboot boot twrp.img' rather than installing it permanently because you can easily flash the miui stock rom again next time u want to back to miui rom.
Unlike twrp, miui 6 recovery is not the same with miui 7. If you tried to flash stock recovery using fastboot flash recovery for different version of miui, it will not work.
Unless you prefer to stay under custom ROM, I highly recommend that you keep your stock recovery intact.
Click to expand...
Click to collapse
Thank you
I will remember to flash the stock recovery using the toolkit next time I switch back to MIUI.
But
If the MIUI rom[6.6.10] or the latest dev[5.11.14] rom needs stock recovery to flash properly, why did it work on the third try? What made it work?
I mean if we find out what makes it flash without error on TWRP we could avoid using stock recovery na?
And btw I was trying MIUI, not the custom ROM, I always stay on them, just wanted to see what MIUI had changed since September.
BUMP!!
Seriously!! someone??
You need to extract the stock recovery from the firmware, then flash it via fastboot, then flash the stock zip