Develop Bugs

Phone stuck in reboot recovery... Help!

I was trying to follow the steps below to install the optical trackpad wake-up. I did the first step "adb reboot recovery". Couldn't get past there. Now my phone is stuck in reboot recovery. How do I get it out and can I do this without reformatting the phone?
zerf said:
I installed this and it worked perfect. Download the file and put the qwerty.kl file in your directory that adb is located. Then follow the commands below.
while phone is powered on plug it in and then do
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
(it will give error saying it couldnt mount curtain things. This is OK)
Looks like this
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
Now run
Code:
df
to make sure that /system is in the list that it outputs.
Should look like this.
Code:
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted
tmpfs 206848 0 206848 0% /dev
/dev/block/mmcblk0p2 198337 7453 190884 4% /cache
/dev/block/mmcblk0p1 765992 153464 612528 20% /data
/dev/block/mtdblock6 152576 122712 29864 80% /datadat
/dev/block/mtdblock3 253952 180320 73632 71% /system
then
Code:
cd /system/usr/keylayout
cp qwerty.kl qwerty.kl.old
(do this so we have a backup incase we need to go back)
now type exit and then run this
Code:
adb push qwerty.kl /system/usr/keylayout
adb reboot
once booted you should be able to power the screen on with your trackpad.
**** I have noticed that if your phone isn't waking by the trackpad try pressing a little harder or holding the button down for a little longer and then it usually works fine****
Click to expand...
Click to collapse

Sorry MODS for making this thread! I figured it out.

Can't mount /system as read-write

Hello folks,
on my HTC Desire with OpenDesire 3.5.2 I'm trying to install the dropbear ssh-deamon according to a german tutorial (I'm not allowed to put the link here... ).
It is on www and then android-hilfe.de and then, go /root-hacking-modding-fuer-motorola-milestone/14241-per-ssh-auf-den-milestone.html
I'm connected to the phone using adb and shell'd into.
Now, they say that I have to mount /system as read-write to put a file (dropbear) into /system/bin. The command is
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
and results in no errors. mount then says:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
so in my opinion, /system shoult be writable.
But everything I try results in an "Out of memory" error: Creating directories, copying files - anything.
Only deleting files is possible: I backed-up and then deleted some ringtones from /system/media/audio/ringtones, and I'm also not able to copy the backup of them I did before onto the sdcard back into the directory again
I read in another thread, that the error "Out of memory" itself is a bug and should mean "No permission". But why don't I have permission?
df -h gives me
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 203.4M 0 203.4M 0% /dev
tmpfs 203.4M 0 203.4M 0% /mnt/asec
/dev/block/mtdblock3 250.0M 106.4M 143.6M 43% /system
/dev/block/mtdblock5 147.6M 53.9M 93.8M 36% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
/dev/block/vold/179:1
3.7G 2.9G 744.3M 80% /mnt/sdcard
/dev/block/vold/179:1
3.7G 2.9G 744.3M 80% /mnt/secure/asec
so there definitively IS enough memory for a 720kB file.
Any ideas?

You can only write to system on the desire via adb from recovery.

If above post didn't explain it enough...
There is no write access to /system partition yet, except via a overlay file system. Have a search and you'll find, like everybody else.

thank you! Yes, that is the problem. I read this also somewhere, but didn't remember it.

I still cant write files even though im in recovery?

zoltrix said:
I still cant write files even though im in recovery?
Click to expand...
Click to collapse
Type "adb remount"
(Without "")

zHk3R said:
Type "adb remount"
(Without "")
Click to expand...
Click to collapse
Im trying to relfash my recovery and i keep getting the no space issue.
If i type in adb remount, i can no longer mount my sd card that is holding my image..
http://forum.xda-developers.com/showthread.php?t=805141
EDIT: If i figure out how to s-off my phone, will that fix it?

zoltrix said:
Im trying to relfash my recovery and i keep getting the no space issue.
If i type in adb remount, i can no longer mount my sd card that is holding my image..
http://forum.xda-developers.com/showthread.php?t=805141
EDIT: If i figure out how to s-off my phone, will that fix it?
Click to expand...
Click to collapse
Just follow the thread in Desire Android Development and you'll have S-OFF easy.
PRO TIP: Use a flash drive rather than burning the .iso on a CD.

Yea but, will i need s-off to flash this recovery?
I know s-off lets you do stuff within fastboot, but im not too sure what taht really means

zoltrix said:
Yea but, will i need s-off to flash this recovery?
I know s-off lets you do stuff within fastboot, but im not too sure what taht really means
Click to expand...
Click to collapse
nevermind, ive done my research and s-off fixed my problem!

details
could you please describe in a little bit more details how you have managed to write the /system mount point ?
thanks in advance ...
btw, there are o bunch of guys that want this answer

What? and Why?
I too would like to know more about writing to /system.
adb remount appears to switch the mount point from "ro" to "rw" (as shown with mount command) but I still get the same "Read-only file system" response when I try to adb push files.
What exactly is the issue here? Is it related to S-ON / S-OFF ?
What do I have to do to be able to write to /system?
(other than reboot into recovery; when I copy files in Recovery, they are gone after a normal reboot)
Thanks

[HOW TO] Check your filesystem (a la 'fsck')

I've been having lots of trouble with my SD and local filesystems getting corrupted, which in turn has been causing the flush-179 process to go ballistic (100% CPU loop, reboot hangs, etc.). If only there was a way to run a quick FSCK(8) on my Android's unmounted filesystems to check for problems. Well, there is!
This may be old, old news to some of the more seasoned OS hackers, so please be kind with any negative feedback about it being intuitively obvious. It wasn't to me, but after some research and testing, I've come up with these simple steps:
Boot into Recovery
Connect via USB to ADB shell
Code:
C:\Scratch\Android> [B]adb devices[/B]
C:\Scratch\Android> [B]adb shell[/B]
Mount /system and /data to determine the /dev/block names, then umount each
Code:
~ # [B]mount /system[/B]
~ # [B]mount /data[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 308620 64 308556 0% /dev
/dev/block/mmcblk0p27
295509 121021 159231 43% /cache
/dev/block/mmcblk0p26
1184268 848052 276060 75% /data
/dev/block/mmcblk0p25
562384 461416 72400 86% /system
~ # [B]umount /system[/B]
~ # [B]umount /data[/B]
Run e2fsck against each /dev/block filesystem
Code:
~ # [B]e2fsck -n /dev/block/mmcblk0p25[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p25: clean, 4168/35760 files, 117605/142847 blocks
~ # [B]e2fsck -n /dev/block/mmcblk0p26[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p26: clean, 7173/75200 files, 216745/300799 blocks
~ #
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave

some help
ViperGeek said:
I've been having lots of trouble with my SD and local filesystems getting corrupted, which in turn has been causing the flush-179 process to go ballistic (100% CPU loop, reboot hangs, etc.). If only there was a way to run a quick on my Android's unmounted filesystems to check for problems. Well, there is!
This may be old, old news to some of the more seasoned OS hackers, so please be kind with any negative feedback about it being intuitively obvious. It wasn't to me, but after some research and testing, I've come up with these simple steps:
Boot into Recovery
Connect via USB to ADB shell
Code:
C:\Scratch\Android> [B]adb devices[/B]
C:\Scratch\Android> [B]adb shell[/B]
Mount /system and /data to determine the /dev/block names, then umount each
Code:
~ # [B]mount /system[/B]
~ # [B]mount /data[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 308620 64 308556 0% /dev
/dev/block/mmcblk0p27
295509 121021 159231 43% /cache
/dev/block/mmcblk0p26
1184268 848052 276060 75% /data
/dev/block/mmcblk0p25
562384 461416 72400 86% /system
~ # [B]umount /system[/B]
~ # [B]umount /data[/B]
Run e2fsck against each /dev/block filesystem
Code:
~ # [B]e2fsck -n /dev/block/mmcblk0p25[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p25: clean, 4168/35760 files, 117605/142847 blocks
~ # [B]e2fsck -n /dev/block/mmcblk0p26[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p26: clean, 7173/75200 files, 216745/300799 blocks
~ #
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave
Click to expand...
Click to collapse
on my phone i have a fiel called fsck.exfat and fsck_msod i think and im trying to run one (though not sure what the difference is) to fix some corrupted files in data internally. im trying to see if the file can be run through recovery without putting it through adb to unmount the data. im not too sure how to figure out what the data block is called because when i rum the mount i get a ton of different blocks (about 32 of them).
im trying to clean up the lost+found files i have and i have 3 of from a corrupted nandroid

robcop19 said:
on my phone i have a fiel called fsck.exfat and fsck_msod i think and im trying to run one (though not sure what the difference is) to fix some corrupted files in data internally. im trying to see if the file can be run through recovery without putting it through adb to unmount the data. im not too sure how to figure out what the data block is called because when i rum the mount i get a ton of different blocks (about 32 of them).
im trying to clean up the lost+found files i have and i have 3 of from a corrupted nandroid
Click to expand...
Click to collapse
Hi Rob.
I'm not sure if I can be of any specific assistance. exFAT is a type of filesystem format, like UNIX/Android ext3 and ext4, but beyond that, I couldn't tell you what those programs do. I do know that on some operating systems, the only way to fix the file chains and blocks is to make sure it's unmounted in single user mode. ADB is the closest we Android guys can get to UNIX single user mode without some clever Recovery Mode ZIP file programming.
– Dave

alrighty
ViperGeek said:
Hi Rob.
I'm not sure if I can be of any specific assistance. , but beyond that, I couldn't tell you what those programs do. I do know that on some operating systems, the only way to fix the file chains and blocks is to make sure it's unmounted in single user mode. ADB is the closest we Android guys can get to UNIX single user mode without some clever Recovery Mode ZIP file programming.
– Dave
Click to expand...
Click to collapse
well thank you for at least writing back on it. im not sure how to run adb let alone run the progrma to try and fix this but i will be learning up on it

robcop19 said:
well thank you for at least writing back on it. im not sure how to run adb let alone run the progrma to try and fix this but i will be learning up on it
Click to expand...
Click to collapse
ADB isn't all that difficult to use. Here's a good primer on it:
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
Once installed, just boot your phone into Recovery (power off completely, then power on with the Vol Down key held, then select RECOVERY). Once it's sitting there, connect your phone to the PC via USB, wait for Windows to find the right drivers, and you're connected. 'adb devices' should list your phone in the "List of devices attached", after which you're good to go.
– Dave
ps. I've not tried it personally, but there's supposedly a "universal USB driver" available here:
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

wow
ViperGeek said:
ADB isn't all that difficult to use. Here's a good primer on it:
Once installed, just boot your phone into Recovery (power off completely, then power on with the Vol Down key held, then select RECOVERY). Once it's sitting there, connect your phone to the PC via USB, wait for Windows to find the right drivers, and you're connected. 'adb devices' should list your phone in the "List of devices attached", after which you're good to go.
– Dave
ps. I've not tried it personally, but there's supposedly a "universal USB driver" available here:
Wow thank you very much for the help youre giving me I will see if i can go and start finding a solution
Click to expand...
Click to collapse

ViperGeek said:
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave
Click to expand...
Click to collapse
I figured this out about a week ago now I guess and did indeed find that there were corrupted partitions. My phone had been acting up for several weeks before and it pretty much unusable now. I do manage to clean system and data up, and was even able to flash a new ROM which I hadn't been able to, they'd always abort.
I have a question though, is this only good for ext2 partitions? I have the same version as shown in the tutorial and if you run 'e2fsck -V' the output makes me think that maybe it's not happy checking ext3 and ext4 partitions and that's why i was popping up errors, or at least that's why even when i fixed errors it maybe wasn't really fixing the issue.
Thanks.
I've got a different phone, but a search brought me here to this thread. I think my issues though are more corrupted memory rather than device specific so hope you don't mind my post here.

I think this will answer your question
http://linux.die.net/man/8/fsck.ext3
(It should be good for all ext partitions)
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

ahh the good old fsck
glad i found this thread
thanks a lot mannnn

One more helpful tidbit.
Even if you run 'e2fsck -n' and find a "clean" file system, it may be useful to force a scan via 'e2fsck -f'. This just happened to me. I had something funny going on, and so rebooted into recovery and checked my file systems. Everything was cool like Fonzie, which I didn't believe, and so I used 'e2fsck -f' and found lots of fuglies that got fixed.
Be careful running -f on a cross-linked file system like the /data partition on a Galaxy S3/S4. It can have the tendency to unlink the elfin magic Samsung used and make a mess.
- Dave

(Double-tap post deleted)

This will not work with stock Android - default boot to recovery doesn't enable adb - you have to have CWM for that.
So, the questions remains - how can I run e2fsck without rooting my phone (and possibly voiding its warranty)?

How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.

Can this be done in terminal? And would I need su?

PRose61 said:
Can this be done in terminal? And would I need su?
Click to expand...
Click to collapse
Yes, this can be done in terminal on the phone itself. You do need root/su.

ApTeM said:
This will not work with stock Android - default boot to recovery doesn't enable adb - you have to have CWM for that.
So, the questions remains - how can I run e2fsck without rooting my phone (and possibly voiding its warranty)?
Click to expand...
Click to collapse
Is this why I get can't read '/etc/fstab': No such file or directory?
I'm using a stock Samsung S2, but it is rooted and has superuser and busybox.

Code:
ViperGeek said:
I've been having lots of trouble with my SD and local filesystems getting corrupted, which in turn has been causing the flush-179 process to go ballistic (100% CPU loop, reboot hangs, etc.). If only there was a way to run a quick on my Android's unmounted filesystems to check for problems. Well, there is!
This may be old, old news to some of the more seasoned OS hackers, so please be kind with any negative feedback about it being intuitively obvious. It wasn't to me, but after some research and testing, I've come up with these simple steps:
Boot into Recovery
Connect via USB to ADB shell
Code:
C:\Scratch\Android> [B]adb devices[/B]
C:\Scratch\Android> [B]adb shell[/B]
Mount /system and /data to determine the /dev/block names, then umount each
Code:
~ # [B]mount /system[/B]
~ # [B]mount /data[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 308620 64 308556 0% /dev
/dev/block/mmcblk0p27
295509 121021 159231 43% /cache
/dev/block/mmcblk0p26
1184268 848052 276060 75% /data
/dev/block/mmcblk0p25
562384 461416 72400 86% /system
~ # [B]umount /system[/B]
~ # [B]umount /data[/B]
Run e2fsck against each /dev/block filesystem
Code:
~ # [B]e2fsck -n /dev/block/mmcblk0p25[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p25: clean, 4168/35760 files, 117605/142847 blocks
~ # [B]e2fsck -n /dev/block/mmcblk0p26[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p26: clean, 7173/75200 files, 216745/300799 blocks
~ #
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave
Click to expand...
Click to collapse
Thank you for your very well done post. I also realize that this thread is very old. Still it is the best I have found after days of looking. And finally, I have a different phone. Having said that perhaps someone might help.
My phone is a Galaxy S5 Verizon SM-G900V running KitKat 4.4.4. I have root on the phone, but am running stock Verizon Kitkat with stock recovery.
So I have used ADB by plugging in my phone via USB to my Windows computer. I can get root in ADB and find the /data filesystem and its /dev/block/... device. But when I try to
Code:
umount /data
I get a response that the filesystem is busy. This makes sense.
I have booted into recovery via VOL UP + HOME + POWER and it takes me to the RECOVERY menu. But the only option that connects with my ADB shell is "apply update from ADB". When you use the command
Code:
ADB devices
, my phone shows up, but as "phoneid" sideload, and
Code:
ADB shell
exits immediately.
I have also tried to use a terminal shell and then su to root. Again I cannot umount /data since it is busy. (Of course it is, I am using it...)
And finally I have tried
Code:
touch /forcefsck
to create that file in the root directory. This is supposed to force a fsck during boot up. But the root directory (/) is read only. So you can't write the file to it.
I am at my wits end. What I really need to do is mark the /data filesystem as dirty and have the system check it on reboot. But I can't find anyway to do it.
So if anyone can help, I would be very grateful
Joe

nexus with broken file system, cannot wipe

Hi everybody,
I'm in deep troubles with my nexus (maguro).
Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.
the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.
twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.
And then the weird part begins:
it's like every partition is read only, but from the mount command it doesn't look like it.
flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.
factory reset successful, and everything is like before.
wiping sdcard, nothing happens.
if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).
Try to fix or to change the partitions filesystem in twrp doesn't change anything.
I tried also to change the file system in parted, through the adb shell,this happens:
Code:
~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?
Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel? i
i
i
Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
...
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
...
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
and of course nothing changes.
so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?
If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.
this is my mount result:
Code:
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)
and remounting in rw the partitions has no effect.
Even the parted, e2fsck, etc files disappear from /sbin after each reboot.
thank you
edit:
Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.
I'm looking for a procedure to make them "ordered" as the other phone.
edit2:
Code:
/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12
/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*
/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
Stuck here at the moment, cannot set superblock flags..
edit3:
Tested every possible superblock position, no luck.
I'm starting to think that the internal memory could be dead, but the phone in fastboot and recovery mode works fine.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.

KF2 Soft brick - /data and /sdcard read-only

My mom has a Kindle 2nd Generation running 10.5.1 stock.
The other day, it started rebooting, but not in the traditional bootloop sense. The OS would load to the lock screen, you could swipe and use it (albeit sluggishly) for approximately 30 seconds before it rebooted again. So, it made it impossible to access the device via ADB.
I made a factory cable, accessed fastboot, and did the following:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
(if using a fastboot USB cable, swap to a normal USB cable before entering the next command)
fastboot -i 0x1949 oem recovery
Click to expand...
Click to collapse
This worked fine. I was able to get into recovery mode with TWRP and access ADB. I pulled all the data off the /sdcard partition. This was a big concern since my mom has been using this thing for a couple years now and she's collected quite a bit. Originally, my directive was to factory reset and reflash the stock firmware from Amazon: update-kindle-10.5.1_user_5174820.bin. It would be nice if they supplied a checksum, but they don't apparently.
Anyway, the more I thought about it, I thought I could clear some caches, uninstall some apks and that would resolve the issue without a new system image. Then I started to notice the problem:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 336.6M 136.0K 336.5M 0% /dev
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /data
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /sdcard
/dev/block/mmcblk0p12
639.8M 11.0M 628.8M 2% /cache
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p13 on /data type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p13 on /sdcard type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
~ #
Click to expand...
Click to collapse
Both /data and /sdcard are read-only. They also use the same block device. Maybe that's normal? I've already tried remounting the partitions read-write to no avail.
mount -o rw,remount /sdcard
mount -o rw,remount /data
Click to expand...
Click to collapse
Both commands execute as if they were accepted successfully (ala no output). However, rechecking mount's output, shows no change. It's still read-only.
I've tried sideloading in TWRP, but that resulted in a protocol fault. Also through TWRP, the factory reset succeeds, but actually does nothing. All of the data is still there. My other idea is to push the image onto the /cache partition (there's just enough room), and try to install that way, but I have a feeling that 1) won't work and 2) may exacerbate problems.
I'm stuck. Anyone have any ideas?

Solved
I was able to free the partitions.
fastboot -i 0x1949 erase userdata
Click to expand...
Click to collapse
It must have been some sort of corruption in userspace. I had previously tried a wipe through TWRP which was claimed to be successful. I still can't determine if TWRP doesn't check all their syscalls and handle the return codes or the Linux subsystem in Android is the root of the bugs. Either way, upon reboot, the device returned to factory "out of box" state.