Develop Bugs

Fixed my phone :)

I had errors in my previous recovery which showed:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Also errors such as error formatting system and mounting system.
So i flashed a new recovery, amon_ra's recovery, this one included the option to move the recovery log to sd. Then re-installed my rom.
Here's how i did it.
Plugged in the phone, booted to fastboot.
I opened the cmd and typed:
cd C:\Users\Francis\Documents\ANDROID files\Android SDK Windows\tools
This is the path that contains the fastboot.exe. I then typed fastboot.exe.
Downloaded recovery-RA-desire-v2.0.0.img and cut n pasted into the tools folder.
I typed: fastboot oem enableqxdm 0
I then typed fastboot flash recovery recovery-RA-desire-v2.0.0.img
The recovery file was obtained from this link: http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-desire-v2.0.0.img
I then went into bootloader, then recovery and re-installed my rom.

If you use an EXT, you would be better off with 2.0.1

It is common problem with PVT4 and Clockwork recovery 2.5.0.7 which is installed during rooting with Unrevoked
I used AmonRa 2.0.1 but recently switched to 4EXTRecovery.

OP: Are you seriously that stupid you had to create third thread for it?!

I messed up the /data partition. "Partition table doesn't exist".

Hi people,
Today I decided to do a fresh start on my Redmi 1S. I erased all partitions (excluding the bootloader) with fastboot to then install CyanogenMod 12.1. For some whatever reason TWRP can't detect my SD card, so I can't flash any .zip from there (this is a problem I had before I had this idea of a fresh start, so it's not related). And, it says error mounting every partition I have erased with fastboot (edit: now it's only /data), so I couldn't store the .zip to flash in internal storage. I attempted to fix the /data partition using TWRP (Repair file system) and an error occurred and completely destroyed my /data partition. I'm glad I didn't do the same for the other partitions (I was testing it first with the /data).
Then I heard about "ADB Sideloading", which would easily solve my problems I guess, since I could flash the original MIUI and it would bring my partitions back (I think). Well, here's what happened:
Code:
Installing '/sideload/package.zip'
Writing image emmc_appsboot.mbn...
[I]blah blah blah[/I]
E:Unable to mount '/data'
With fastboot I can for example erase /system, but I can't erase /data, fastboot gives this error:
Code:
remote: partition table doesn't exist
How can I fix the /data partition? Am I screwed?
Thanks in advance!
Edit: I just fixed the SD card problem not being recognized. I had to use the tool SDFormatter instead of the built-in Windows Formatting Tool.
Edit 2: I tried to restore a nandroid backup, it stops with "Unable to mount /data" too... The other partitions work fine.

Nixtren said:
Hi people,
Today I decided to do a fresh start on my Redmi 1S. I erased all partitions (excluding the bootloader) with fastboot to then install CyanogenMod 12.1. For some whatever reason TWRP can't detect my SD card, so I can't flash any .zip from there (this is a problem I had before I had this idea of a fresh start, so it's not related). And, it says error mounting every partition I have erased with fastboot (edit: now it's only /data), so I couldn't store the .zip to flash in internal storage. I attempted to fix the /data partition using TWRP (Repair file system) and an error occurred and completely destroyed my /data partition. I'm glad I didn't do the same for the other partitions (I was testing it first with the /data).
Then I heard about "ADB Sideloading", which would easily solve my problems I guess, since I could flash the original MIUI and it would bring my partitions back (I think). Well, here's what happened:
Code:
Installing '/sideload/package.zip'
Writing image emmc_appsboot.mbn...
[I]blah blah blah[/I]
E:Unable to mount '/data'
With fastboot I can for example erase /system, but I can't erase /data, fastboot gives this error:
Code:
remote: partition table doesn't exist
How can I fix the /data partition? Am I screwed?
Thanks in advance!
Edit: I just fixed the SD card problem not being recognized. I had to use the tool SDFormatter instead of the built-in Windows Formatting Tool.
Edit 2: I tried to restore a nandroid backup, it stops with "Unable to mount /data" too... The other partitions work fine.
Click to expand...
Click to collapse
try to flash miui v5 or v6 rom via fastboot

unkown rockstar said:
try to flash miui v5 or v6 rom via fastboot
Click to expand...
Click to collapse
I have MIUI here in a .zip file. Can you tell me the command to flash via fastboot? I tried "fastboot update" but it says that there's no android-info.txt in the .zip file.
To sum up, so far I have tried to ADB Sideload, I have tried to flash that MIUI .zip from TWRP and everything fails with "Unable to mount /data".
I probably need to recreate the /data partition. Any ideas?

Nixtren said:
I have MIUI here in a .zip file. Can you tell me the command to flash via fastboot? I tried "fastboot update" but it says that there's no android-info.txt in the .zip file.
To sum up, so far I have tried to ADB Sideload, I have tried to flash that MIUI .zip from TWRP and everything fails with "Unable to mount /data".
I probably need to recreate the /data partition. Any ideas?
Click to expand...
Click to collapse
there is a seperate rom for fastboot..your can check on miui downloads page for links and step by step guide.

unkown rockstar said:
there is a seperate rom for fastboot..your can check on miui downloads page for links and step by step guide.
Click to expand...
Click to collapse
It worked! Thanks, I didn't know there was a separate ROM for fastboot.

Nixtren said:
It worked! Thanks, I didn't know there was a separate ROM for fastboot.
Click to expand...
Click to collapse
glad to know it worked..now follow all steps correctly

Spontaneous issue no longer allows /cache or /data to mount

So last night, my kindle was working normally with my self-compiled CM13 build (7/1/16 version), 7/16/16 opengapps, and other miscellaneous tweaks I use to refine my experience. Anyway, I was using my device normally and set it down to charge earlier. When I came back to it, I noticed it was booting CM. A few minutes later, I see that it's rebuilding cache for all the (system?) apps. I check back in a little bit later, and it reboots again. Suspecting an issue, I typed fastboot -i 0x1949 erase cache to try to erase the cache, and it doesn't work. The terminal window just hangs until I unplug the device. I tried rebooting into TWRP before doing the cache wipe, and it ends up not fully booting into TWRP. After that /cache wipe command fails, I suspect that my /sdcard or /data partitions are full somehow, so I kick the device into TWRP via fastboot -i 0x1949 oem recovery. TWRP boots that time, but asks if it can remount /system as R/W, so something's amiss. I plug the kindle into my Ubuntu machine, and I don't see any files or anything. I don't even see the "Internal storage" icon that usually shows up. I find it really baffling. I try to browse /sdcard from TWRP's file manager, and nothing shows up there either. I check the TWRP log, and it says "Failed to mount '/data' (Invalid argument)" and "Unable to recreate /data/media folder." For /cache, it says "Failed to mount '/cache' (Invalid argument)". Note that I didn't flash anything or otherwise modify the device leading up to this. I checked the battery via TWRP, and I have a decent level of around 48%. The kindle's 3 years old (got it in 2013 as a birthday present, so I know it's at least 3). Any ideas, or is this the last leg for my 8.9"?

I just wanted to post a couple updates. First off, I wiped /cache in TWRP by switching it over to ext4 from f2fs (both /data and /cache were f2fs-formatted), and that resolved the "failed to mount /cache" issue. I later did a raw backup of the data partition, tried to mount it, and couldn't. I ran fsck.f2fs on it, and it said it couldn't find a valid F2FS superblock at 0x0 or 0x1. I figured the partitions both corrupted, which makes sense considering that cache and data were both formatted under f2fs, and they were the only partitions affected. I did some research, and I discovered that f2fs can indeed go ballistic. I reformatted the data partition as ext4 as well, and now CM's working again.
The moral of the story: backup early and often.

[solved] TWRP - could not mount /data and unable to find crypto footer

Hi,
Nice to be here after so much years of reading !
My LG G3s (d722) was fine with Cyanogenmod 13 and encryption enabled. I've made a Titanium backup for my apps (& cie...) on the SD card, and reboot in TWRP 3.0.2-0, enter my password to mount storage, and I've wiped all partitions exept the SD card.
Then I've flashed the CM14 zip file, and get these error in the process :
"could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4 mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Unkown error 200 unmount of /data failed; no such volume"
"Failed to mount '/data' (No such device)"
Since then :
- if I reboot into recovery, TWRP doesn't ask me the password to decryp the partition
- if I reboot in CyanogenMod ask me the password, but the tells me :
Decryption unsuccessful
The password you entered is correct but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.​Then it reboot into TWRP
Any ideas ?
How could I mount ext4 partition in TWRP ? Or restore stock recovery ?
Thanks a lot for your advices

resolving !
Hi myself and everyone from another time,
I've resolved this mess by :
- installing LG drivers
- downloading kitkat stock-rom D72210d_00.kdz
- open LG Flash Tool 2014 and load D72210d_00.kdz, and start a CSE Flash
Then stard android 4, root it... etc
Best

Can't boot and strange problems in TWRP: "Device Storage Corrupt"

When I boot my phone I get the message "Device storage corrupt" and it prompts me to reboot into recovery. However TWRP doesnt automatically fix the problem. In TWRP most operations terminate with the message "Unable to mount /data". I cannot wipe /data because it gives me that error.
Is it a problem with the partition table? Should I be trying to flash a PIT file using Heimdal? (I am new to Samsung sorry.) If it is a problem which can be sorted out by manually partitioning, I'm a pretty deft hand with the linux shell and maybe the adb shell isnt too different.
TIA

Oh no ! You have updated your phone to an locked bootloader ! You can't flash now something.

Word to the wise: I was able to fix this problem by reformatting the /data partition. For some reason twrp was not able to do this.
0. Reboot into twrp and if necessary disable MTP in the mount menu.
1. Then I found out the name of the partition block device which holds the /data partition. I found this out by trying to wipe the data partition using TWRP and noting the error message. For me that was mmcblk0p24.
2. Run adb shell mke2fs -T ext4 /dev/block/mmcblk0p24
Problem solved!