Hi!
My device was shutting down while I stay on recovery and the cache partition now is corrupted. (seems only read partition)
I try deleting cache on fastboot, reinstall rom, stock, an old twrp work but new twrp not, e2fsck on adb shell (only on loop boot),...
I can see the filesystem white loop boot, but e2fsck can't repair permisions or block (bigblock problem).
And I don't know why can't run on download mode.
Thanks
Did you do "fastboot erase cache" or "fastboot format cache"? If you did the former, try the latter instead.
Related
Hello everyone,
i bricked my a511 because i had the stupid idea to set go back factory defaults with the old cwm.
so, i know that the problem is the damaged data partition, is it possible to recreate this partition ?
I had the same Problem. I flashed a data.img. This works. you can even mount the system partition? and the cache?
The Fastboot commands are "fastboot flash userdata C:\[your path to the data.img]" and "fastboot flash system C:\[your path to the data.img]"
and "fastboot flash cache C:\[your path to the data.img]"
Webitu
No, it's not the partition that's damaged, but the NAND chip itself.
Hello,
I'm trying to erase cache using the stock recovery. But get stucks for ever at this point:
-- Wiping cache... -
Formatting /cache...
I'm using Recovery version: KOT49H
---
EDIT/UPDATE:
This is how i fixed this:
1) I flashed cache partition: Fastboot flash cache cache.img
2) I tried to format /cache until it get stuck for ever (again...)...
3) Manually rebooted and entered Recovery Mode again. (with a lot of fails regarding the mount of the /cache partition, can't mount cache blablabla).
4) Tried to format (the unmounted) /cache anyway...
5) Waited 1-2 minutes......
6) Format /cache is complete.
7) rebooted again to recovery mode and this time (like the 1st time) /cache is successfully mounted but now i'm able to format it without anydelays (Fixed)!
Hello, I have an issue that will hopefully be resolved with some help from you guys.
I have a tf300t, a 64gb class 10 sandisk card, and I was running cromi 5.3 with data2sd before switching to crombi-kk. I used gparted and formatted the second partition on my microsd to fsfs. I then did the following to start fresh on the tablet
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
fastboot -i 0x0B05 reboot
I then flashed twrp 2.7.0.1 omni version from the link on the tf300t crombi-kk page.
I then installed crombi with data2sd with f2fs. I used that kernel. Install went fine and went to the wipe dalvik,home, buttons were at the bottom and it said updating partioning details or whatever.
It then said e:unable to mount /sd-ext and a bunch more e: ones. I rebooted and the penguins showed up and it said
Well I couldn't remember what the first one had said but the second said
Data on i/data on microsd for data2sd/rom2sd
/system on microsd for rom2sd
And it booted up normally and I setup crombi.
I now keep getting freezes and I find myself having to hit the power button and enter my pin. Sometimes I will get the message systemui has stopped or something, do you want to wait? Or something along those lines.. I guess the only thing I didn't do is factory reset before installing crombi-kk. I am going to reformat the f2fs partition on the microsd in gparted again, then I will do all of this
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
fastboot -i 0x0B05 reboot
And flashed twrp 2.7.0.1 omni version. Then factory reset. Should I have anything extra checked off in the advanced section of the factory reset page?
Then I will install crombi with data2sd option with f2fs and use _that kernel in the aroma installer.
I will report back
Thanks for the help!
Hey guys,
I had previously encrypted my phone with the inbuilt android encryption, but it just didn't work (the PIN wasn't my password)
I tried to factory reset it but it didn't work either, from both fastboot or recovery.
So I reflashed my entire system from fastboot (which worked perfectly). Now I want to install the unofficial cm12 zip, but I can't erase userdata from my phone at all.. Either through fastboot or recovery, and I'm locked to the GPe image I am using currently.
The recovery error I get when trying to delete my data partition is:
Code:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
E:unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
I have no idea what to do help please?
Possible solution
Okay, so the CWM recovery is beyond stupid and seems to want to verify that it can read a partition before it lets you format it. But you can't do this if you've encrypted it. So you have to reformat it yourself. But first, you have to figure out the device name of that partition.
After you've booted the phone into recovery, you'll need to send commands to the phone with adb.
Type this to receive an error revealing a device name:
Code:
adb shell mount /data
Then type the following using the /dev/ name given in the error from the first command. That device name might be unique to my phone. I'm not sure:
Code:
adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name/
In any case, you want to find where userdata is pointing to. On mine, it is:
Code:
/dev/block/mmcblk0p36
Then to double check which type of filesystem is being used on that userdata partition:
Code:
adb shell cat /etc/fstab
Then to format it yourself (if f2fs is the filesystem) since CWM recovery won't bloody well do it and lets everyone think they've bricked their phone:
Code:
adb shell mkfs.f2fs /dev/block/mmcblk0p36
Disclaimer: this worked for me, but I can't make any guarantees. It got me past the error CWM was giving. After I formatted the partition on my own, CWM recovery was able to proceed as normal.
Worked for me atleast
1) You Need twrp recovery.
2)Select data partition.
3)Change file system to some other than f2fs.
4)Again change file system to f2fs (without rebooting recovery).
5)Repair Partition with twrp menu.
6)If Partition repair was successful then wipe the Partition.
7)? Good to go.
8)And yeah though it doesn't brick your phone if anything happens to your device then I am not responsible.
jlm0 said:
Okay, so the CWM recovery is beyond stupid and seems to want to verify that it can read a partition before it lets you format it. But you can't do this if you've encrypted it. So you have to reformat it yourself. But first, you have to figure out the device name of that partition.
After you've booted the phone into recovery, you'll need to send commands to the phone with adb.
Type this to receive an error revealing a device name:
Code:
adb shell mount /data
Then type the following using the /dev/ name given in the error from the first command. That device name might be unique to my phone. I'm not sure:
Code:
adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name/
In any case, you want to find where userdata is pointing to. On mine, it is:
Code:
/dev/block/mmcblk0p36
Then to double check which type of filesystem is being used on that userdata partition:
Code:
adb shell cat /etc/fstab
Then to format it yourself (if f2fs is the filesystem) since CWM recovery won't bloody well do it and lets everyone think they've bricked their phone:
Code:
adb shell mkfs.f2fs /dev/block/mmcblk0p36
Disclaimer: this worked for me, but I can't make any guarantees. It got me past the error CWM was giving. After I formatted the partition on my own, CWM recovery was able to proceed as normal.
Click to expand...
Click to collapse
@jlm0 Hope your post will help me. I have terminal emulator, with this how do I run these commands, because I'm not able to change the recovery also.
Regards
Janardhan TS
sent from Mi
i officially unlocked my moto g3 and flashed it with lineage os 14.1 nightly osprey , twrp 3.1.1-0-osprey and super su v2.79. i also had to change the format of data and cache to f2f. i cheared the cache and factory reset the phone too but the phone is stuck on bootloop.....recovery is perfectly fine , there is no problem opening it but the phone just won't stop booting up. ive waited for nearly 6 hours now
help
r4venfire said:
i officially unlocked my moto g3 and flashed it with lineage os 14.1 nightly osprey , twrp 3.1.1-0-osprey and super su v2.79. i also had to change the format of data and cache to f2f. i cheared the cache and factory reset the phone too but the phone is stuck on bootloop.....recovery is perfectly fine , there is no problem opening it but the phone just won't stop booting up. ive waited for nearly 6 hours now
help
Click to expand...
Click to collapse
Try this:
Go to recovery then wipe everything except internal storage and SD card
Install custom ROM
Don't install anything else(SuperSU or gapps)
Reboot
If above doesn't work, the problem is with custom ROM, download a different rom
ayush4261 said:
Try this:
Go to recovery then wipe everything except internal storage and SD card
Install custom ROM
Don't install anything else(SuperSU or gapps)
Reboot
If above doesn't work, the problem is with custom ROM, download a different rom
Click to expand...
Click to collapse
i solved it. found a thread which helped me. this was the procedure:
Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the os you want to your PC rename it to "os.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)(not required if you already have a recovery)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\os.zip /data/media/0/"(to push the os to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push os.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the os.zip or you can flash stock firmware through mfastboot.
This will work definitely.
r4venfire said:
i solved it. found a thread which helped me. this was the procedure:....
Click to expand...
Click to collapse
Thanks man, I tried only deleting cache and userdata from fastboot and worked too.