Hey there
I have a pretty serious problem with my I9100... I had installed the Paranoid Android 2.52 ROM and I was trying to switch to a different kernel. Which wasn't working for me, I'm guessing due to the Fastboot feature in that ROM.
The last kernel I tried was the Andromeda one. While trying that, I thought I might try to do a factory wipe using its recovery software, hoping that that might get Paranoid Android to boot.
Unfortunately, it would hang while doing the wipe, and I eventually (after about 20 minutes) power-cycled the device. I tried getting back to my working kernel, but Andromeda's recovery would either error out with mount errors, or it would hang altogether.
Eventually, I tried flashing a CF-Root kernel using Odin, and since then I was unable to get past the Samsung boot splash screen. I could no longer access the recovery software, but I could get into download mode and flash stuff via Odin (Kies won't recognize the device).
I've tried a variety of kernels and firmwares (including the stock one for my phone (GT-I9100_XEF_I9100XWKJ2_I9100XXKI4_I9100XEFKJ1, which I've previously flashed successfully to get it back to a non-rooted vanilla state)), but nothing I did would get the phone to boot.
Thinking the partition table might've been damaged somehow, I attempted the stock firmware from the first post here, including the PIT file and re-partitioning. This process would eventually hang when flashing datafs.
Thinking the bootloader might be damaged, I tried partitioning again, flashing the original bootloader from here, and again flashing the stock firmware that I've used successfully in the past.
I can now actually get past the boot splash! However, the phone boots directly into stock recovery, which looks like it's trying to do some post-update maintenance-type stuff, but fails horribly at it. Some of the output from it scrolls past the viewport, but this is the last lines that I can read:
Code:
[COLOR="Orange"]Formatting /cache...
Cache wipe complete[/COLOR]
-- Updating application...
[COLOR="DarkRed"]E:failed to mount /data (Unknown error: 0)
E:install_application_for_customer:Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
[/COLOR][COLOR="Orange"]-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEF/system/'.
Successfully applied multi-CSC.[/COLOR]
[COLOR="DarkRed"]E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Unknown error: 0)
E:Can't open /cache/recovery/log
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Unknown error: 0)[/COLOR]
It definitely looks like a borked filesystem/partitioning to me. I tried doing a factory wipe in this recovery, but it would hang at formatting /cache.
Any ideas of what I can do to get this thing up and running again?
Thanks in advance,
Daniel
I successfully flashed a CF kernel, and can now access CWM.
I get these error messages, however:
Code:
CWM-based Recovery v5.0.2.7
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Wiping cache partition in CWM takes care of those errors. Trying a factory reset will give me "Formatting /data..." for a bit, and then the device automatically reboots.
I can format /cache and /system alright, but not /data... I'm fearing that NAND corruption bug I've heard of, except I don't see how I would've caught it...
All right, so I've now confirmed that the Andromeda kernel indeed has the hard-brick bug. Why on earth anyone in their right mind would release a kernel based on that broken leak is beyond my comprehension.
And, to add injury to insult, the devs know there's a problem, yet do not warn about it in the OP, but they mention it some thirty pages into the thread. Thanks, guys!
Anyway, I'm currently scanning my internal storage for damaged areas so that I can custom-PIT my way around it.
Useful posts for reference:
http://forum.xda-developers.com/showthread.php?t=1760107
http://forum.xda-developers.com/showthread.php?t=1667886
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Hopefully I'll see my phone booting tonight.
Using the patched PIT workaround, I now have my phone back up and running 2½ GB lost on the internal storage, though, but hey - beats being a paper weight!
Related
ok here is the problem i have a telus fascinate and here i tried to install the ics passion rom but i had to flash in an other rom first to get access to clockwork manager since it wasnt possible on my previous one then from there i formated the data and such then instaled this rom :
http://forum.xda-developers.com/showthread.php?t=1362961 so here what it did, first it installed correctly then got it to reboot and see that its stuck in boot loop for 15 min so im saying myself um not good so i decide to restore my backup but here when i flash back to stock i get this:
Code:
[COLOR="Blue"]Android system recovery <3e>
Enter: OK Key, Select: Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
---------------------------------[/COLOR]
[COLOR="Red"]E: copy_dbdata_media:Can'T mount /dbdata
your storage not prepared yet. please use UI men
u for format and reboot action[/COLOR]
[COLOR="SandyBrown"]Media files copy failed
Manual MODE
--Appling Multi-csc....
installing multi-csc
Can'T access to '/system/csc/tls/sys/'.
successfully applied multi-csc[/COLOR]{----this is yellow but was too flashy to put it in that color
[COLOR="Red"]E:failed to mount /cache (invalid argument.)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file:: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (invalid argument.)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument.)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument.)[/COLOR]
ok so here i am not knowing what to do i need help im not the best in these things can someone clearly point me to a solution or help plz
You need to flash a better recover than the stock recover, which you will likely need to flash with Odin. I'd try the Vibrant board to see if someone there could be of more assistance, but that's basically what you're looking at, as far as I recall from my TMO Vibrant.
Ok here are the updates of the problem, i did the a complete wipe of the phone then flashed the ice cream sandwich from passion from the phone and i loaded now where it bugs is there is no mobile network so im kinda stuck it detect telus under access point but in network operator it find nothing any idea guys?
You need to go back to eh03 via odin. Then flash as usual through cwm. It happened to me before. Without odin you wont get out of this.
Sent from my SCH-I500 using xda premium
Ok, so I have the icsv10 kernel... And I still can't back up ROMS.
I don't want to go through flashing stock, prerooting it, and installing a new kernel each time I want to try a new ROM!
So maybe you can help me:
When I go to recovery it says:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I format my cache it says:
-- Wiping cache...
Formatting /cache...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
Cache wipe complete.
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I have ubuntu in vmware, so I can use it if needed...
I want to try a new rom, plz help...
Fastboot erase cache.
Still not working, can't restore any ROMS, have not been able to pass the stage when it says that can't work with blocks 12, 13, 14...
What's wrong with my phone?!?!?
Well, I think I had all the problems ever!!!
I solved them, so I hope this post helps...
I had my phone soft bricked for an hour. The flashtool was starting to load, and then it would say error flashing.
So I fastbooted some prerooted ics.
Then it was working but it didn't have any space in the memory, like there was no internal memory (the two giga one). So that's why I couldn't flash.
There was nowhere to flash.
I did format from recovery a million times. Didn't do anything. No errors were encountered...
It would always return to german, didn't even retain settings.
Amd when I was really despaired, I wiped the phone via the phone settings menu: backup and reset -> factory reset.
And then the two giga reappeared in storage. Yay!!!
Then I flashed the nordic, fastbooted kernel ics10.elf and then flashed the Rom (modded ics 95 in my case, don't like miui) . All works fine. I'm the best...
Sent from my LT26i using xda app-developers app
Okay so last night I attempted to root my nook tablet 1.4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2037368. I downloaded all the files that were pointed to in that thread, and followed the instructions. Everything went perfect and soon I was setting up my google account, then following the final steps which involved downloading rom manager, and goo manager. All was well, until I decided to reboot the tablet.
After I rebooted the initial loading seemed fine (got the "n" screen"), then cyanobootloader popped up, then the Team B presents XDA logo popped up and then nothing. The tablet stayed frozen on the Team B logo, and rebooting did nothing.
So being the idiot that I am, I tried going into recovery from the cyanobootloder. This took me to TWRP where my dumbass ended up going to advanced and Wiping the system. After that I tried installing Cm-7-Team-B-Beata1-signed.zip and gapps-gb-20110828-signed.zip from TWRP. The log gives several messages that read:
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /emmc
E: Unable to mount /emmc
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
At this point I was freaking out, stopped using my head, and began trying desperately to go back to stock. I tried using this method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/, but it didn't change anything.
I decided then to try redoing the rooting guide again to see if that could solve the problem. It did not.
So now the tablet boots into TWRP when I turn it on. I can also enter CWM-based Recovery using the SD card I made from the guide. However, when I enter CWM-based-recovery I get these messages at the bottom:
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Can't Mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
That's pretty much where I'm stuck on at the moment. I figured I should probably stop messing with this tablet before I made a bigger mess.
Any help would be greatly appreciated.
I'd suggest that you try flashing afresh a CM10 or CM10.1 build using SDcard based CWM recovery, using a method such as described at http://forum.xda-developers.com/showthread.php?t=2056626.
In case you're considering using one of the so-called "unbricking" tools, read this post http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 first before you pick the wrong tool that would permanently wipe out your NT's individual device specific data like WiFi MAC address, security certificate, serial number, etc.
Nook needs a /recovery folder in /cache partition like /cache/recovery.
Somehow that folder is missing
Is so easy to fix that you will laugh
dd zero the cache partition after you make sure cwm/twrp is not have it mounted check by reading mount /cache if it says unmount cache select it first.
Then format cache in cwm/twrp and that's it. Folder will be created by it self and that error print out will stop.
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
Was charging my phone yesterday went to unplug and phone stuck at splash screen, pulled battery and left for a while on re-insert splash screen appears straight away. Pulled battery overnight and same thing happened.
Phone has been rooted and has latest (i think) CWM (v6.0.4.7) on it, was running CyanogenMod1! which updated yesterday to latest version (nightly 20140311 i think). I can get into recovery but can't install the rom i have on the phone just get the following messages:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Does anyone have any idea how if i can get a working rom back onto the phone
Thanks in Advance
jedathoss said:
Was charging my phone yesterday went to unplug and phone stuck at splash screen, pulled battery and left for a while on re-insert splash screen appears straight away. Pulled battery overnight and same thing happened.
Phone has been rooted and has latest (i think) CWM (v6.0.4.7) on it, was running CyanogenMod1! which updated yesterday to latest version (nightly 20140311 i think). I can get into recovery but can't install the rom i have on the phone just get the following messages:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Does anyone have any idea how if i can get a working rom back onto the phone
Thanks in Advance
Click to expand...
Click to collapse
I had a similar thing when I was changing between 4.3 and 4.4.2 in which my recovery struggled to mount storage after the system was flashed. In the end I had to flash an old version of Philz CWM, or alternatively flash TWRP and mess about with the settings as where it looked for files (something like that) I also found hat only zips on the internal card flashed for a while...
You may have to either:
1) Push the files to the internal card using ADB
2) Try various recoveries with various ROMS till you get on to sit nicely on your system
3) Or as a last option just reflash your phone with a stock rom through ODIN just to get it up and running, before reflashing a recovery and root using CF-AutoRoot and/or ODIN
pjcarrmole said:
I had a similar thing when I was changing between 4.3 and 4.4.2 in which my recovery struggled to mount storage after the system was flashed. In the end I had to flash an old version of Philz CWM, or alternatively flash TWRP and mess about with the settings as where it looked for files (something like that) I also found hat only zips on the internal card flashed for a while...
You may have to either:
1) Push the files to the internal card using ADB
2) Try various recoveries with various ROMS till you get on to sit nicely on your system
3) Or as a last option just reflash your phone with a stock rom through ODIN just to get it up and running, before reflashing a recovery and root using CF-AutoRoot and/or ODIN
Click to expand...
Click to collapse
Cheers pjc, gives me some idea of where to start. I'd just ogt everything the way i liked it as well, typical isn't it
Hi All
I had my phone on charge overnight (as usual), but when I got up this morning, I had an error "Device memory damaged" on screen, it says "The data partition has been corrupted. You need to reset the device to factory defaults. This will erase all your data" and has a button marked "Reset device"
When I tap the button, it boots to recovery, TWRP scrolls some text on screen, it then reboots back to the same error screen.
If I manually boot into recovery and try to wipe data, I'm told
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/. twrps when trying to read settings file.
E: Unable to mount '/data'
E: Unable to mount '/data'
E: Unable to wipe '/data'
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
I tried flashing recovery-clockwork-6.0.4.6-i9300 via heimdall to see if that had any more success, but that failed too (although I'm not sure if that was due to the phone or my heimdall set-up).
I've spent most of the day trying to find a fix, but I'm just going around in circles.
The Phone is an i9300, and it was running UltimaROM 17.1
Any ideas how to get my phone working again?
~S
First flash the latest stock firmware for your country then factory reset in recovery before first boot.
If that fails then try the rescue firmware thread in general forum, use the 4 3 version and pit file that thread contains.
If that also fails then it sounds like your memory is indeed damaged.
I wouldn't advise anyone charge the battery in their phone overnight, the processor and nand memory is then running 24/7 and will obviously fail sooner
Sanukk said:
Hi All
I had my phone on charge overnight (as usual), but when I got up this morning, I had an error "Device memory damaged" on screen, it says "The data partition has been corrupted. You need to reset the device to factory defaults. This will erase all your data" and has a button marked "Reset device"
When I tap the button, it boots to recovery, TWRP scrolls some text on screen, it then reboots back to the same error screen.
If I manually boot into recovery and try to wipe data, I'm told
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/. twrps when trying to read settings file.
E: Unable to mount '/data'
E: Unable to mount '/data'
E: Unable to wipe '/data'
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
I tried flashing recovery-clockwork-6.0.4.6-i9300 via heimdall to see if that had any more success, but that failed too (although I'm not sure if that was due to the phone or my heimdall set-up).
I've spent most of the day trying to find a fix, but I'm just going around in circles.
The Phone is an i9300, and it was running UltimaROM 17.1
Any ideas how to get my phone working again?
~S
Click to expand...
Click to collapse
I have same problem but phone is s7 edge. Did you found a solution.
Unable to mount is a twrp issue. I've seen it many times before.
I have solved it on a custom rom by flashing an official clockworkmod recovery.
I have solved it on a stock firmware by flashing a stock recovery
I have solved it by flashing back to stock completely.
*I have read that some people cannot recover their phone from that state.*