Hello.
This problem has appeared after i flashed the latest Dorimanx kernel (Kernel_Dorimanx-V9.43-[12-16]-[24-10]-JB-SGII-PWR-CORE). Today, after i flashed the latest ressurection remix ROM, i wanted to flash a kernel too. So i booted into recovery, flashed Dorimanx's kernel with no problems, rebooted, and noticed that my keyboard was lagging. So i decided to restore a previous backup from before i flashed the kernel, but when i got into recovery, and select to instal zip from sdcard, i got the following error: E: can't mount /sdcard. The thing is, when i restart my phone, i can acces my files with no problems (music, photos etc), but when i try to do it from recovery, i will not load the sdcard. Other than that, phone is working fine. No bootloops, no lag, just the mounting problem of the sdcard. I feel i should mention that i get an error even when trying to mount it directly from the recovery tab "mounts and storage". I hope you can get back to me and this soon, because this problem will prevent me from flashing any future roms/kernels or doing backups/restores.
cosminpislariu said:
Hello.
This problem has appeared after i flashed the latest Dorimanx kernel (Kernel_Dorimanx-V9.43-[12-16]-[24-10]-JB-SGII-PWR-CORE). Today, after i flashed the latest ressurection remix ROM, i wanted to flash a kernel too. So i booted into recovery, flashed Dorimanx's kernel with no problems, rebooted, and noticed that my keyboard was lagging. So i decided to restore a previous backup from before i flashed the kernel, but when i got into recovery, and select to instal zip from sdcard, i got the following error: E: can't mount /sdcard. The thing is, when i restart my phone, i can acces my files with no problems (music, photos etc), but when i try to do it from recovery, i will not load the sdcard. Other than that, phone is working fine. No bootloops, no lag, just the mounting problem of the sdcard. I feel i should mention that i get an error even when trying to mount it directly from the recovery tab "mounts and storage". I hope you can get back to me and this soon, because this problem will prevent me from flashing any future roms/kernels or doing backups/restores.
Click to expand...
Click to collapse
Put philz kernel into your internal sd card or the kernel which you were using previously and flash it from recovery then reboot to recovery again. Now try to restore your nandroid backup.
Hope it helps.
Good luck :thumbup:
Related
Hi all, this is my first time posting in XDA and I finally managed to brick my phone. Please help me The story goes as below :
1) I was using Slimbean 4.2.2 stable build 8, with the said CWM 6.0.4.7. and tried to reinstall the rom fresh from the original zip from slimroms website.
2) Did the usual wipe user data and cache partition
3) Wiped dalvik cache
4) I was curious and bravely decided to use the mounts and storage option. Browsed through the list and decided to format /system, /cache, /preload, /data, and /boot. Suddenly felt like something just went wrong, so stopped before the /modem section.
5) Thinking that I finally cleared my phone from all of the previous rom's files and such, went into install zip menu. Tried installing zip from sdcard1 (external).
6) CWM shows my external card properly. Selected the zip file. Wait. Phone reboots into CWM.
7) Thought I missed something, tried rebooting as usual. Directly went into CWM again. Pushed the button combination for download mode, went into download mode just fine.
8) Used CWM boot into bootloader mode menu, phone reboots into CWM again.
9) Tried using the "install zip from sdcard" menu. Phone reboots into CWM again.
10) Checked the log, it says
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.2/mmc_host/mmcl
Right now its 1 AM in the morning, and I have morning shift tomorrow. Please help me people The only probable solution left for me is installing Samsung original ROM using ODIN, hoping that everything will be set as usual again.
izhamznl said:
Hi all, this is my first time posting in XDA and I finally managed to brick my phone. Please help me The story goes as below :
1) I was using Slimbean 4.2.2 stable build 8, with the said CWM 6.0.4.7. and tried to reinstall the rom fresh from the original zip from slimroms website.
2) Did the usual wipe user data and cache partition
3) Wiped dalvik cache
4) I was curious and bravely decided to use the mounts and storage option. Browsed through the list and decided to format /system, /cache, /preload, /data, and /boot. Suddenly felt like something just went wrong, so stopped before the /modem section.
5) Thinking that I finally cleared my phone from all of the previous rom's files and such, went into install zip menu. Tried installing zip from sdcard1 (external).
6) CWM shows my external card properly. Selected the zip file. Wait. Phone reboots into CWM.
7) Thought I missed something, tried rebooting as usual. Directly went into CWM again. Pushed the button combination for download mode, went into download mode just fine.
8) Used CWM boot into bootloader mode menu, phone reboots into CWM again.
9) Tried using the "install zip from sdcard" menu. Phone reboots into CWM again.
10) Checked the log, it says
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.2/mmc_host/mmcl
Right now its 1 AM in the morning, and I have morning shift tomorrow. Please help me people The only probable solution left for me is installing Samsung original ROM using ODIN, hoping that everything will be set as usual again.
Click to expand...
Click to collapse
Your mistake was in step (4) you did everything right except format /boot you have wiped your boot img (bad mistake) connect to odin and flash stock again.
tallman43 said:
Your mistake was in step (4) you did everything right except format /boot you have wiped your boot img (bad mistake) connect to odin and flash stock again.
Click to expand...
Click to collapse
Thank you man. That did the job. I reflash stock rom using ODIN and it boot just fine. Gonna try flashing slimbean again tomorrow. Thanks for your help
izhamznl said:
Thank you man. That did the job. I reflash stock rom using ODIN and it boot just fine. Gonna try flashing slimbean again tomorrow. Thanks for your help
Click to expand...
Click to collapse
Glad to see it worked there was nothing wrong that you did apart from the last option /boot...I suggest you use PhilZ recovery it as a option in settings to "clean to install a new rom" which formats all the correct partitions for you..
tallman43 said:
Glad to see it worked there was nothing wrong that you did apart from the last option /boot...I suggest you use PhilZ recovery it as a option in settings to "clean to install a new rom" which formats all the correct partitions for you..
Click to expand...
Click to collapse
I used to use Philz recovery, touch version. But it seems to have something that I don't like back then, so I opted back to CWM. Maybe I should try Philz again. BTW, why does the mmcblk error comes out? Should I be worried. Because when I check the log now, it still occurs even though my phone is fully functional now.
Hi all
Dad's I9300 (international) started making problems booting up a week ago (sometimes it did and sometimes it didn't for a few hours). Begged him to bring it in for me to backup. Of course he didn't and today the device refused to boot permanently. It simply gets stuck on the logo screen.
When boot into recovery I got lots of E: failed to mount /cache. After wiping the cache and rebooting into recovery I now get only E: failed to mount /system (see attached image).
Download mode also seems to be working.
Device is 4.1.2 with stock ROM and stock recovery.
The main concern here is to recover all personal data. After that, I don't care if the device gets bricked. I searched the web and came up with two possible solutions:
1) Reflashing the same stock ROM I flashed a while ago (hoping that what I have stored on my PC is what is actually flashed on the device.....), and not wiping the data. As I understand, flashing a stock ROM without wiping data shouldn't cause the device not to boot.
2) Flash PhilZ Touch 6 Recovery using Odin and use Aroma file browsing to copy internal memory files (pics, mp3, WhatsApp data, etc.) to an external SD and then start messing around with the phone. (as described here)
What's my best option here? It sounds to me that the second one is better, but I'm not familiar with flashing a recovery and possible consequences.
Can someone kindly advise? I'll greatly appreciate any word of wisdom...
Solved.
Hi all,
I am on 4.4.4 and used TWRP in past, now I am on Philz Touch latest recovery.
I first cleaned data and system and tried to flash a different rom, it flashed fine but when I tried to flash 4.4.4 Gapps recovery restarted and it kept restarting if I tried to flash that Gapps so I cleaned again and only flashed the Rom this time, rebooted and my system restarted to recovery.
I manually tried to format all partitions but got
"E:format_volume: make_ext4fs failed on /dev/block/mmcblk0p10
E:Error formatting /preload!"
while formatting preload partition.
I google about this and search in xda too and found few threads suggesting to format /preload partition using TWRP recovery so I tried to flash TWRP but it stuck on it's flash screen. I tried to flash old version using Odin as well as new one but it keeps hanging on the it's flash screen. Flashing Philz via odin works every time but not TWRP.
So it looks like I am not able to format /preload partition, I am not able to flash any rom or gapps and not able to flash any version of TWRP recovery.
I am able to take a backup of my phone and restore it without any problem including my internal sd card using Philz Touch though just for the info.
So any suggestions friends?
Thanks.
Edit:
Flashing normal cwm and flashing TWRP after removing TWRP folder from internal memory helped to boot into TWRP. Also I was able to format /preload using normal CWM recovery however flashing anything using any recovery whether it's TWRP or Philz Touch simply boot my phone back into recovery itself and nothing works.
Even a clean flash doesn't work and flashing only a simply rom file will not work and boot my phone directly into recovery so it looks like my memory is corrupted or something similar.
I would appreciate any kind of suggestions related to my problem. Thanks.
Update :
Thankfully it was only my memory card which got corrupted and thus corrupted my rom files too so changing those files fixed my issue..
Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel
Fueled by 7000mAh ZeroLemon Battery
I had a NT that was running CM11 well.
It ran CWM 6.0.4.5 from internal memory.
Decided to try CM12.1
Wiped cache and delvik
Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip and GAPPS
CM12.1 booted but ran very poorly. Tried various things. Each time I installed
there was a message when exiting CWM "Root access possibly lost. Fix?".
At first I responded no, then finally Yes. Since them Android won't boot.
It always boots to recovery now.
Tried again after updating to CWM_6.0.4.8_chrmhoffmann.zip
No luck.
Installed TWRP 2.6.3.1 and tried to install various versions of CM.
During the install I get error messages, Unable to mount '/bootdata'.
If I try to mount /bootdata directly with TWRP it fails. Even tried to create
the folder with Terminal.
Guidance is appreciated.
So I got boot Android to boot again. Created a bootable SD with TWRP v2.8.5.2.
Replaced the recovery.img in a v2.6.3.1 .ZIP file with v2.8.5.2 image.
Loaded the zip so TWRPv2.8.5.2 now loads from Internal Recovery.
CM12.1 and gapps install and load with this TWRP but it behaves poorly.
Lots of pauses and a few spontanious reboots.
Reloaded cm-11-20141112-SNAPSHOT-M12-acclaim.zip and gapps. Seems to run
cleanly.
Wish CM12.1 would behave.
Boot loop with Nook Tablet Acclaim 16gb
I tried installing the latest snapshot: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip
I used this gapps: open_gapps-arm-5.1-pico-20150923
This is the recovery: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim-recovery
I first downloaded and used the tablet to install this snapshot. Continuous boot loop.
Then I tried the usual manual mode erasing everything that needed it and still continuous boot loop ???
Is there something that I am doing wrong ??????
I had to revert to the previous snapshot and everything is back to normal.
HELP ?!?!?!?!?!?
nandroid123-
I copied http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.8.5.2-acclaim-sdcard.img over the recovery.img of my bootable sd.
Wiped/FactoryReset and installed CM with it. It fixed my no load of Android problem for both CM11 and CM12.1 but CM12.1 was not stable so I reverted to CM11 (cm-11-20141112-SNAPSHOT-M12-acclaim.zip).
I then installed http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.8.5.2-acclaim.img internally.
Boot looping
So no resolution for the boot looping on this latest snapshot !??!?!?!
nandroid123 said:
So no resolution for the boot looping on this latest snapshot !??!?!?!
Click to expand...
Click to collapse
Is your device boot loop to recovery? If so, see http://forum.xda-developers.com/showthread.php?p=21381141#post21381141 for potential cause and solution.
Digimax my 16gb Acclaim will boot loop when this: "" cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip "" is installed.
When I revert back to the previous snapshot it works normally ??????
I will check out your link.
Thanks
Dennis
ETM said:
CM12.1 booted but ran very poorly. Tried various things. Each time I installed
there was a message when exiting CWM "Root access possibly lost. Fix?".
At first I responded no, then finally Yes. Since them Android won't boot.
It always boots to recovery now.
...
Installed TWRP 2.6.3.1 and tried to install various versions of CM.
During the install I get error messages, Unable to mount '/bootdata'.
If I try to mount /bootdata directly with TWRP it fails. Even tried to create
the folder with Terminal.
Click to expand...
Click to collapse
So here is the trick, I actually needed both.
Start with TWRP (SD version) to cleanup the system for clean install, etc...
Then, boot CWM, use its menu system to remount the bootdata partition <-- I think there was a typo thats tripping things up there
Then, boot with TWRP again, and get your installs in.
You can load a copy of Superuser from the SD while you're in there to be certain its rooted.
Hi guys,
Having a bad time setting up my S7 Edge (international model).
End goal is to have it rooted with a Lineage OS ROM.
Successfully flashed TWRP (3.1.1.0) using Odin3 (v3.12) and had no issues booting into TWRP and looking around.
Issues began when I tried to wipe the internal storage in preparation for a new ROM; I got errors along the lines of "unable to mount /data" invalid directory, "unable to mount /system" etc, and the wipe would fail.
Following another user's guide I formatted my /data partition to ExFat (plan was to then format it back to Fat4, which supposedly fixes the issue), however this froze the phone. I was able to reboot it after leaving it a few hours, however now the phone just freezes on the TWRP logo when I try boot into recovery.
I have reflashed TWRP to no avail.
From what I've read online, flashing a new ROM via Odin might recreate all required partitions (namely /data) ? Issue with this is I can only find .zip, not .tar ROM's as required by Odin.
Have I just turned my phone into a brick ?
Any suggestions on what to do next would be greatly appreciated !
Many thanks,
Pron