Related
So, my previous post was a bit too optimistic. I've managed to get TWRP onto my phone, but when I went to actually load a custom ROM into it, I found that it couldn't read anything from my sdcard.
I'm having what appears to be a common problem: when I boot into Recovery, TWRP asks for a password. When I cannot provide it (because I have no idea what it is), TWRP is unable to access the data partition. Apparently, the partition is encrypted and I have no way to de-crypt it.
I've found dozens of other posts by users having this problem and the solution everyone is giving is to fully wipe the data partition and start over. But I *can't* wipe the data partition, because TWRP can't access it and fails almost immediately. I have tried a multitude of options, including:
* Installing old versions of TWRP - same behavior; asks for a password, fails to wipe/format the data partition.
* Installing ClockWork's recovery - same thing; fails to format/wipe the data partition
* Flashing back to stock recovery, using that to format my data partition; this worked fine but as soon as I put TWRP back, the problem came back.
On my last attempt, I used the stock recovery to completely wipe the data partition, and made absolutely sure that it never booted into anything but Download or Recovery modes after that. I was hoping that would prevent the stock software from ever re-encrypting the data, but somehow, when I booted TWRP, it still can't read my partitions. Note that my phone itself is not "encrypted" as far as the Settings application is concerned, but apparently Android is doing something behind the scenes anyway. There doesn't seem to be any option in the stock settings to turn off this encryption.
Is there any hope for getting a custom ROM onto this phone?
Thanks for the help!
Any solution? I'm running into the same issue where TWRP is asking for a password.
My recovery unable to wipe data factory reset
its stuck on wiping data /formatting /data
what to do ?
i tried odin but still stuck on samsung logo recovery also hanging on wipe data option.
remove your battery and attemped again what you want install and reply your steps here
ahmetakin said:
remove your battery and attemped again what you want install and reply your steps here
Click to expand...
Click to collapse
i removed battery
boot into recovery
and click on wipe date/factory reset
it starts and stuck on wiping data.
wont go futher
i tried restore option but showing error.
http://forum.xda-developers.com/showthread.php?t=1555679&page=3 follow that thread you need install
stock rom or recovery cwm with your pc with odin.
RazZzeR said:
My recovery unable to wipe data factory reset
its stuck on wiping data /formatting /data
what to do ?
i tried odin but still stuck on samsung logo recovery also hanging on wipe data option.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2669024
If it`s the same error via odin as well then you god the same corrupted partition like me... and you need to get to service to revive it with RIFF JTAG BOX ( rewrite the /data partition at low level)
install any other new Recovery
---------- Post added at 09:30 PM ---------- Previous post was at 09:20 PM ----------
and try from other sdcard
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
toiel said:
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
Click to expand...
Click to collapse
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Same problem here
gooniegoogoo2 said:
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Click to expand...
Click to collapse
Same problem here... I can't properly do some of the advanced wipes in the process of trying to install omni.
I did as you suggested and tried wiping them individually but to no success.
I am definitely not as fluent in this stuff as a lot of you on here are, but I am competent/confident enough to follow good instructions.
Somebody help please!
Cant install KitKat Roms
I am having the same issue and have done the same thing. Tried installing both CM and OMNI with no success. the recovery is telling me the came thing that it cannot mount E:\ 'cache' and other files i need to wipe.
Some one please help.
i was wondering...
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
But it worked before
ohDevious said:
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
Click to expand...
Click to collapse
I'm getting the same "can't mount cache" error when converting to Big Part - I had previously been running several Big Part roms, and had no problem with the conversion at that time - I then reverted back to stock (using VZW OTA's) for awhile, but want to give the Big Part roms another shot - I've tried several methods of reverting to stock, then coming back to install a 10.1 ROM, which is successful, but when I flash the Big Part TWRP and try the conversion, I get the cache mount error every time - I can revert to the "normal" TWRP, reformat, and re-install non-big part roms without a problem - help us Obi Wan! WTF?
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
Click to expand...
Click to collapse
I forgot to mention click the format data tab under wipe and type yes.
I just had this same experience. I think the directions are somehow missing a step or we're misreading it.
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
I forgot to mention click the format data tab under wipe and type yes.
Click to expand...
Click to collapse
A day not spent well
I am having the same issue all of you guys are having. I had 10.1 stingray (4.2.2) running well and thought it was time to try Kit Kat. Both the ROMs wind up the same way, a loooong running splash screen (over an hour before I manually rebooted). Over and over no mater how many ways I tried to wipe the XOOM I kept getting the Can't mount the cache message. I was able to revert back to 10.1 but I can't figure why others can make the install and we cannot. I have asked others on the forum but no one can answer the question?
Anyone? Thanks! Paddy
I was finally able to figure this out last night. I was looking at my cache and data formats and both were formatted as f2fs. I believe it's under wipe in the latest TWRP (2.7.1.0), there's an option on the left that shows you the format type of your drives. On non BigPart TWRP I changed the cache and data to ext4. Rebooted back into recovery, and followed the guide posted here to apply BigPart to my Xoom: http://forum.xda-developers.com/showthread.php?t=2506997 :: Then I was able to load Omni BigPart edition with no issues at all. I'd be happy to give more details if anyone wants. I'm in the office now, otherwise I'd post some snap shots. I'll update this when I get home.
has anyone recovered from the "unable to mount cache" error? I have followed all the information in this thread, checked out the relevant links all to no avail.
The only additional data I can provide is that when I go into the wipe menu (TWRP 2.7.1) / advanced / select cache / and "repair or change" I have all 0's for the cache size MBs. Repairing the cache or changing file system claims to be successful, but it's always 0 MBs. For grins I tried all of the above with TWRP 2.6.3 and had no better results.
Thanks in advance.
My "Galaxy Tab 2 P5100" constantly restarts. Has the stock ROM with root and cwm 6.0.1.
Only reboot if the tablet is in android system or power off.
In the recovery dont restart.
This is the problem:
If i make a factory reset, when the tablet restart, this fails.
In the CWM, wipe data/factory reset: data wipe complete successfuly. But when the tablet restart, the data dont wiped.
If i delete my pictures or unistall apps, when restart, the deleted pictures or apps are there again.
I flash TWRP or philz recovery whit odin: succesfully flashed, when restart cwm 6.0.1 is still there.
In the cwm i flash another custom rom: successfully flashed. When restart, nothing flashed, the tablet still in the stock original rom.
Odin back to stock fails at system write.
Something is really wrong
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Have you tried /system wipe?
shsagnik said:
Something is really wrong
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Have you tried /system wipe?
Click to expand...
Click to collapse
When i flash a custom rom , the installer format system, then write the new rom. In the recovery say successfully wiped and flashed, but when restart again, the original rom a data still there.
Odin start to write system, fails at the write, but the tablet boot to the original android system and data.
Try using adb to install recovery
shsagnik said:
Try using adb to install recovery
Click to expand...
Click to collapse
CWM v6.0.1.0 dont have the option to enable sideload.
ADB error: closed
[emoji51]
¿?
Maybe we must call someone by spamming other threads
I have the same problem :crying:
when in recovery mode, it says something like
"did not match sized '/system/csc/common/system/csc/....."
about wallpaper thing, with red font.
already wipe chace also factory reset, but after reboot, the internal memory still the same. the pictures, the apps.
flash via odin stuck at nand write, then failed.
I can enter the homescreen, but just for 5-7 seconds, then it will restart. then do the same cycles.
How to solve this? is this a hardware problem?
someone said about emmc bricked, he replace the mainboar with the new 1. its too expensive for me, especially for now, this tab no longer up to date compare to newest devices nowadays.
sorry for my english, my brain also got some brick :silly:
no power button problem
without any reason the phone rebbot itself and stuck in boot loop animation....stock MMB29V Marshmallow , no root, only unlocked
tried:
-wipe cache and data
-reinstalling all singles images files
-reinstalling with flash all bat and finally it works...
what's the problem???
and now? there is something to check? have to change the phone???
tnx
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Ok but i need ti know if is possible to check the health device status
What do you mean by health? You mean each component?
I mean if is possible that something hardware is defective or going to be defective.
can I run some tests?
I know of no tests that are available to the public.
Ok
audit13 said:
Manually flash each partition again, including userdata.img partition. After flashing the last partition, boot directly to recovery using the power and volume keys (don't reboot the phone at all after flashing the last partition), perform a factory wipe, and reboot.
Click to expand...
Click to collapse
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
WallaceLau said:
I have a similar problem with my N5, it was originally a power-button issue, and after some "whacking" the phone no longer "repeatedly reset" but now it just sits on the "Google" boot screen forever. Probably something got messed up during all the unintended reboots. I already went into recovery and did a factory reset, no luck. Tried flashing to older ROMs, no luck. Started hitting up forums, saw this post, tried your suggestion (flash each partition manually, did a "fastboot reboot-bootloader", enter recovery, wipe, and reboot), and still no luck.
I can get into fastboot/recovery, and even tried loading custom ROMs (CM13 to be exact). No matter what I tried, the phone will power-up, and stuck at the "Google" screen. Note that I've always waited at least an hour after flashing each version before I reboot from the "Google" screen.
I've read somewhere there is a "persist(?)" partition which will throw some error if corrupted, but it will require USB debugging enabled to fix. Unfortunately, I can't boot into any ROM to enable USB debugging...
Am I SOL or is there anything else I can try?
Thanks,
Wallace
Click to expand...
Click to collapse
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
audit13 said:
Are you getting any errors when performing a factory wipe? Does the factory wipe happen very quickly? You flashed the userdata.img partition too?
Click to expand...
Click to collapse
First time I did a wipe it took over an hour, then the phone rebooted to the dead android screen. So I tried to wipe again, and it seems like all subsequent wipe took anywhere between 3-5 minutes. No error on each wipe (can't say on the first one, since by the time I got back to the phone it has already rebooted). And yes, I did flashed everything - boot, cache, recovery, system, userdata, bootloader, radio - not exactly in that sequence, but all of those partitions are flashed with the image that comes with the Google download package. Then factory reset and reboot.
Thanks,
Wallace
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
audit13 said:
Maybe try erasing cache and data using fastboot commands? If this doesn't work, it's possible that there is a hardware problem with the phone's internal memory.
Click to expand...
Click to collapse
Did a "fastboot format cache" and "fastboot format userdata", no error. Still won't boot... are those the commands you are referring to?
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
audit13 said:
Yup, or fastboot erase cache or fastboot erase data.
Sounds like the emmc may be messed up.
Click to expand...
Click to collapse
Tried all those, and yes same result... also, I flashed a different recovery (TWRP) and thereafter I can't even flash new ROMs anymore. ADB Sideload error our (forgot to write down the error message), and if I copy the file to internal storage and flash from there, TWRP will get stuck for hours.
How common are eMMC corruptions?
W.
The emmc problem is not that common, but it does happen. I'm not sure if it is partition or software corruption or a physical defect.
Other xda members have encountered emmc problems too that could only be fixed through a motherboard swap.
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Sarvesh.huddedar said:
I am running into a situation emmc. the problem is I tried below action so far
1. Attempted to flash recovery partition which failed immediately after first reboot . it never got flashed correctly
2. Attempted to format all the partitions but I could format boot partition I could format no other partition it clearly says that can't mount
3. Then I tried to boot using fastboot command into recovery partition my command is
Fastboot boot recovery.img
I tried cwm I tried TWRP . only 2.6 dot x x worked in twrp. Cwm was not so helpful because it does not give me many features likewise TWRP
Once I boot in the recovery it asks for password if I click cancel it shows me all the interfaces but nothing works I don't have any local storage available it clearly fails to read it and everything shows is encrypted I don't know not sure what is going on there
When I attempt to format I get a error message as no partition available for this operation. No file system available
About phone but I think I am still searching for options but so far I could see that this is e MMC issue and there is no partitions available on this memory I am not able to format this internal memory I am new to the Linux environment and not sure what to do to format this internal emmc...
Can someone suggest any options to format and Re partition the emmc?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
The constant boot looping could be a power button problem?
kenbrownstone said:
The password thing means your encrypted...Unencrypt and you can see all your storage..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
My friend as a n5 that kerps bootlooping too..No roit but unlocked..Never rooted and has no clue how to root or mod a phone...It keeps bootlooping foe no resean 100% stock..It will only stop when i get it to go into bootloader mode and that takes a while...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Sarvesh.huddedar said:
I dont think anyone has encrypted the phone ever.
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Maybe im mistaken but evertime i had to put in a password in ttwrp i had gotten encrypted...you get it fixed? My friends started bootlooping for no reason and wouldnt stop til the battery was dead.. Never seen a stock phone do that..
Sent from my Nexus 6P using Tapatalk
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
Reasearch it.... It totally sounds like what happened to me...
Sent from my Nexus 6P using Tapatalk