so i decided to install safestrap to try out a rom. the install went fine and the recovery install went fine. i hit reboot recovery in the app to get to twrp. the first thing i did was try to make a backup of my stock rom. during the backup process twrp says it was unable to mount system so backing up /system failed. i tried to go into mount option and enable system mount but the check mark doesnt go into the box. it just hangs there highlighting the box. anyone know of a fix for this?
i figured it out. a use busybox pro. cant enable smart install in busybox pro. it doesnt play well with safestrap.
Related
Long story short: When restoring via Nandroid it hangs, when using advanced restore the data portion says
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Error mounting DATA:!
Click to expand...
Click to collapse
This afternoon I tried running the Voodoo zip, but the one I downloaded from their site isn't for the Captivate. I ended up with a phone that was constantly displaying 90 degrees off from what it should have been (holding it straight up had the phone thinking I had it on its side).
I decided to uninstall voodoo by creating the "disable lagfix" folder on my card. I rebooted and the phone hung and remained hung at the spinning progress wheel for an hour. I pulled the battery since I couldn't get out of that screen. Rebooting after that had me in what appeared to be the stock version and showed a few of my non-stock apps as "com.etc..." apps.
More reading on here and I found the Captivate-specific version of Voodoo. I figured I'd try to install that before restoring from the Nandroid backup I ran before installing the Voodoo. However, when in recovery mode I couldn't "click" anything with the power button. I tried using adb reboot recovery which didn't fix the problem and instead put me into a non-stop cycle of non-functioning recovery modes after boots.
So I used Odin to get back to stock. Now I'm trying to restore back to where I was before Voodoo. I tried to just run a simple Restore but it hung and after 90 minutes it hadn't completed. So I tried to run an advanced restore and all sections restored except for Data. When I try to restore Data i get the error at the top of this post. I've googled for an answer and everything I've read so far is Cyanogen specific and appears to require Cyanogen to fully fix it. Anyone know how to fix this on a Captivate? Anyone have a link that I'm missing?
Thanks!
If you can boot the phone, then go into android terminal emulator (you may have to download it from the market first) and type mount in the terminal. See what type of partition /data is. If it's ext 4, the disable lagfix was not finished before you pulled the battery. Your best bet then is to download the Captivate voodoo beta 4 kernel version 1.6, which is sticky post in the Captivate development forum here, remove the disable lagfix folder/file from /sdcard/Voodoo/ and let it boot. It will then get you to the point where you should have been at first without having rotation issues and with a kernel that understand ext4. After that, restore your phone to the way it needs to be with Titanium, or by manually downloading and reinstalling any apps that got deleted by your premature battery pull. When ready to do a nandroid backup, do a disable lagfix and let it fully reboot to convert the ext4 to RFS. Then you can do a nandroid backup of restore, as clockwork recovery does not understand ext4 (yet).
Thanks Rajendra! I'll try that and follow up with the results.
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Duplicate post (no way to delete I guess?)
RobertDeBord said:
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Click to expand...
Click to collapse
Try this - once the phone boots - then go to internal sd card and see if there is a Voodoo folder (which there still should be) inside the Voodoo folder make a folder called disable-lagfix - reboot and it should go through the reverse process of creating the lagfix (robot voice). After it finishes reboot go to rom manager and restore.
Hope This Helps....
I can tell you, I've never had a successful restore from rom manager/clockwork recovery. Not once! The only thing that program is good for is as a replacement recovery reboot, it lets you select which zip you want to install from, rather than having to manually name everything to "update.zip". I can't honestly think of anything else its good for. I've tried literally dozens of restores on my captivate and everyone of them has crashed or frozen at some point during the restore. Worthless!!
SO i was running nook color version 1.1.0 and i used the autonooter to get clockwork installed. I then tried to use the monster rootpack to install phiremod but after it says install is complete i rebooted but now every time i reboot it goes directly to clockwork and i cant get it to boot up normally. is there anything i can do besides a restore to stock to install phiremod/cm7 or exit recovery? BTW i did remove the monster sd card so thats not the reason its booting that way....
When booted to CWR, use adb:
adb shell
Check that rom is mounted with:
mount
You should see /rom somewhere in the returned result.
If it's mounted, do:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
If not:
mkdir /rom
mount /dev/block/mmcblk0p2 /rom
Then use previous command.
If that doesn't help, you can always flash my cwr remover .zip, found on my nook color restore to stock thread.
Sent from my HTC Desire using XDA App
thanks im going to try that right now.
So i am trying to run adb but it says device not found and i cant figure out how to get the device to mount
I had the same thing happen. In recovery, install the zip file in this post to remove recovery and keep it rooted. You will then be able to reboot normally.
http://forum.xda-developers.com/showthread.php?t=914690
I read that it does that with autonooter 3.0. What you need to do is reboot normally after flashing recovery (don't reboot into recovery immediately after flashing). Afterwards you can reboot into recovery.
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
krisslake said:
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
Click to expand...
Click to collapse
Not really sure what you are saying was your problem. But I have a lot of solutions to booting problems in my nook color tips thread linked in my signature. See items A8 and A12. And there is my partition repair thread.
Sent from my BNTV400 using Tapatalk
I am on rooted, locked bootloader, CE 12.1. A. 0. 266 (4.3). After rooting and relocking bootloader, I installed cwm and twrp. everything seemed fine. But, when I checked cwm, to backup, it showed ''can't mount system''. Then i opened twrp and saw that twrp performed backup correctly. but when i started restore to test my backup in twrp, it showed error, "can't unmount system". I did a fresh backup and again repeated the procedure, but still had no results. In short, my cwm and twrp isn't working. Please help me.
It happens like that on 4.3, try this:
http://forum.xda-developers.com/showpost.php?p=45095882&postcount=8
I had reboots in Folder Mount app every time it tried to mount folders. And after applying it it works like a charm, no more reboots.
If you don''t know how to aplly this, here you go:
1. Connect your phone to PC with debbuging ON
2. If you have SuperSU on your phone run supersu.bat, if you have Superuser, then run Superuser.bat.
3. Follow the instructions on the script, they're pretty simple.
4. Tell me if it worked
@Patrol619: Actually my phone doesn't suffer from any reboot problem after mounting folders. I am familiar with that method since we faced it in Xzisten rom. My problem is with CWM and TWRP. they simply can't mount the system.
No, it didn't work. I tried two times.
Sent from my C5303 using XDA Premium 4 mobile app
Good to know, thanks I thought it will work.
Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?
mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act
The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:
I have smtd GT-i9000. I was having error like /data, /system, /cache all were not mounting after installing Lineage OS - https://forum.xda-developers.com/showpost.php?p=70866902&postcount=51
Previously I had installed Marshmallow Rom using CWM Recovery and it automatically installed TWRP 3.0.2. From then on when I tried to flash the Nougat Lineage Untested Rom using ADB Sideload data got unmounted. But then I formatted the data to ext4 and it again got mounted but still when I flashed even Jelly Bean official rom error 7 was seen. I tried to remove the assert code but still it did not worked. Then after rebooting or something everything cache, data, system everything got unmounted and I cannot even change file system. I thought all the problem was because of twrp so I flashed philz touch 6.19.3 now it goes on bootlooping. I cannnot even go to download mode by pressing the buttons. Going to download mode was not possible even before. I am newbie so I do not know much about these. Please help!!! It is not my phone its my friends mobile so he will screw me up! Please help...
Edit: In short
1) Bootlooping Philz Touch 6.19.3
2) Cannot go to download mode by buttons (Even when phone was not bootlooping).
3) Cannot mount /data /system /cache file systems even though I tried formatting.
4) Previously while installed twrp 3.0.2 and all file systems were mounted and good I could not flash even jelly bean rom and it said error 7.
5) Please tell is there any force way of installing stock rom or anything and repair all these and get out of bootlooping. It is not my phone but my friend, he will screw me up for what I have done. Please help me. Please XDA Developers. Please....
Edit: Now I can go to download mode. Please guide me how to mount and install recovery and install any working rom for my device. Mine is from India.