I have a KF1 v6.x (I believe since it was stock). Installed KFU 1.4a. Installed TWRP. Following a post in the [ROM-AOSP] Stock Jelly Bean 4.2.2_r1 for the Kindle Fire [02-12 4.2.2_r1] thread I wiped factory reset then wiped system PRIOR to moving the ROM to the sdcard. Now, there is no OS. I was able to put the ROM.zip on the root of the SD card but when attempting to install it I get "Unable to mount '/data'". I've tried several commands for adb to do partition stuff but didn't get anywhere with that. Not sure if FastBoot is working via KFU due to the following message.
hxxp://imageshack.us/photo/my-images/547/37437819.png/
What's my first step here? I can get into TWRP so hoping this KF isn't totally hosed
Looks like Fastboot is working?
hxxp://imageshack.us/photo/my-images/14/75434412.png/
http://forum.xda-developers.com/showthread.php?t=1949372
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
SUCCESS! :victory: Thanks soupmagnet! Pic of partition table attached showing /data is not mounted. When doing umount cmd received message "can't umount /data: invalid argument" which I guess is good since /data is not mounted in the partition table.
After removing, making, then naming the partion and quitting I received a message: Information: You may need to update /etc/fstab. 2nd pic shows /data correctly mounted.
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
AnotherBrickedDroid said:
Questions:
1) How/at what point did the /data partition get messed up?
2) Is it necessary to "update /etc/fstab"?
3) Who's the happiest KF1-working-again-user?
Click to expand...
Click to collapse
1) It's hard to say really. For the sdcard, I always assumed it was from not "ejecting" it before unmounting, but I think that would be kind of hard to recreate with the data partition. If I were to speculate at this point, I would say it had to do with how certain versions of TWRP format those partitions, but I'm not sure. In either case it's pretty rare for it to happen.
2) From what I understand, you can't. Recovery is unpacked and run from active memory so any changes you make to fstab will be lost every time you reboot. But the filesystem should still be automatically checked every Nth mount.
3) Three guesses? The first two don't count?
Related
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
So I need to revert to stock because I have to send my KF back to amazon for some charging issues. Unrelated to the kernel stuff.
But I had dualboot, with gederom and modaco rom and it was great.
So I tried reverting back to stock using Kinfauns guide, but I wasn't savvy enough with the adb commands I couldn't push it through. So I used another guide and tried to flash the amazon stock update.zip with TWRP. It kept flashing and would fail. I had wiped cache/dalvik/system and did a factory reset.
So I assumed it's because of my dual boot, so I did fastboot oem (can't remember what it was) but it came back saying that it completed and finished. So I went back to TWRP and flashed update.zip.....and then my problem occured.
My problem is that I only have FFF and TWRP on the KF, and it won't boot into any rom because I'm suspecting it can't find it.
I hate to brick it before I have to send it back. I can get into all TWRP options and FFF works fine except it won't boot to a rom atm.
So if you can help me revert back to stock with only FFF and TWRP at the moment.
Thank you!
I don't have a whole lot of experience in this area so someone please correct me if I'm wrong.
In order to dual boot the KF, some repartitioning has to be done. The sdcard partition is split into (I'm guessing) 4 separate partitions: system2, data2, cache2, and a single sdcard for both systems. Each partition needs it's own formatting. System, data and cache partitions get an ext4 formatting while the sdcard gets fat32.
And while "fastboot oem format" restores the original partition table, it doesn't do anything about the formatting (I know this because formatting takes a while longer than the point whatever seconds it takes to reset the partition table). So, while your partition table is correct, your sdcard has two different formats.
Try reformatting your sdcard and I'll bet that does the trick.
Wow easy as wiping the SD card, and updating through kfu. Thank you so much for pointing me in the right direction!
Probably the easiest way would be to mount the sdcard manually...
Code:
adb shell echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
...which would cause Windows to say the drive needs to be formatted. If so, choose fat32 block size 4096
If that doesn't work you may have to use parted.
soupmagnet said:
Probably the easiest way would be to mount the sdcard manually...
Code:
adb shell echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
...which would cause Windows to say the drive needs to be formatted. If so, choose fat32 block size 4096
If that doesn't work you may have to use parted.
Click to expand...
Click to collapse
Thanks Soup! I didn't edit my previous post fast enough but you lead me in the right direction, thank you so much!
Cheshire.Love said:
Wow easy as wiping the SD card, and updating through kfu. Thank you so much for pointing me in the right direction!
Click to expand...
Click to collapse
Yeah that was way simpler than my suggestion lol. I just assumed that TWRP wouldn't have access to it like with a situation I experienced recently on one of my own KFs. I'm glad you figured it out.
Ok, here is the problem, i woke up today, my phone battery was empty, i connected the phone battery was loading, but i couldn't get to the system, after kernel load it stops, like there was no system installed. Everything worked fine day before,my configuration was: Doomkernel and Existenz_2.0.5 ROM.
So, i got to recovery (recovery works,CWM), and there i saw "can't mount cache" error. I got into shell with adb (this works too), and there is no way i can mount any system partition (/system, /cache, /data), what's more important /sdcard does not mount either. So, i'm in recovery, can't install or restore from sdcard,cause /sdcard does not mount.
I'v tried sideload, no go.
I've tried fastboot flash new kernel, and here's interesing thing, fastboot reported that flashing was ok, but i still have Doomkernel (i was trying to flash 6.0-TUX-Core-HD kernel. So seems like fastboot did not write anything at all.
I've tried flashtool with stock tft. It breaks with "final verification error", when i turn "final verification off" it goes all the way, says everything is installed, but when i restarted, still only Doomkernel.
Any ideas ? I take any advice.
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Szatyor said:
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Click to expand...
Click to collapse
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
qrto said:
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
Click to expand...
Click to collapse
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Szatyor said:
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Click to expand...
Click to collapse
Thank you for your ideas. Thing is, all i can start is cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
qrto said:
Thank you for your ideas. Thing is, Alp i can start iż cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
Click to expand...
Click to collapse
Then maybe it's a HW error really. But maybe just the partition table is corrupted. At this point, I don't know. I have only one suggestion left: Take the phone to the nearest SONY Center or GSM shop/service to investigation. But I think they will say you'll need to replace the phone's motherboard. Anyway, it's an too expensive solution I think, because this phone is a "retired" modell without any update, but with a "blacksheep (Snapdragon S3) SoC.
So, a few days ago I managed to root my kindle fire 1st generation. I've been playing around with it, and noticed that it was rather slow. I thought about trying a different ROM for it to see if it would run any faster. Not entirely thinking, I didn't make a recovery with TWRP before I did a wipe. And now I have a kindle with no OS, and it can't flash anything because it doesn't have a root anymore.
I've been hunting down information on what to do for six-ish hours so far, but I haven't had any luck with anything. Can anyone help me?
kingsmaug said:
So, a few days ago I managed to root my kindle fire 1st generation. I've been playing around with it, and noticed that it was rather slow. I thought about trying a different ROM for it to see if it would run any faster. Not entirely thinking, I didn't make a recovery with TWRP before I did a wipe. And now I have a kindle with no OS, and it can't flash anything because it doesn't have a root anymore.
I've been hunting down information on what to do for six-ish hours so far, but I haven't had any luck with anything. Can anyone help me?
Click to expand...
Click to collapse
Do you have twrp?
If so which version?
Sent from my XT907 using Tapatalk
Yes. If I remember correctly, its version 2.6.3.0. It used to have boot loader otterx v2.05, but after some failure with KFU, it has FFF v1.4a.
So, after some more searching, I found that I couldn't mount anything in recovery and they wouldn't mount on their own. So I used adb shell to jump in, and I could manually mount system, data, sdcard, and cache. The only thing that would work was mount /dev/block/mmcblk0p9 , so I had use that on all of them.
After this I could push my ROM and gapps to the sdcard, and install them, but it gives me a new error: error executing updater binary in zip.
And as a bit more info, on first booting into recovery, this is the log:
Unable to mount /sdcard
Unable to recreate and-sec folder
Unable to mount /sdcard
Unable to mount /sdcard
Updating partition details....
Unable to mount /data
Unable to mount /cache
Unable to mount storage
Unable to mount /sdcard during GUI startup
Unable to mount /cache
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
Unable to mount /sdcard
My TWRP version is 2.6.3.1
I hope that helps.
kingsmaug said:
So, after some more searching, I found that I couldn't mount anything in recovery and they wouldn't mount on their own. So I used adb shell to jump in, and I could manually mount system, data, sdcard, and cache. The only thing that would work was mount /dev/block/mmcblk0p9 , so I had use that on all of them.
After this I could push my ROM and gapps to the sdcard, and install them, but it gives me a new error: error executing updater binary in zip.
And as a bit more info, on first booting into recovery, this is the log:
Unable to mount /sdcard
Unable to recreate and-sec folder
Unable to mount /sdcard
Unable to mount /sdcard
Updating partition details....
Unable to mount /data
Unable to mount /cache
Unable to mount storage
Unable to mount /sdcard during GUI startup
Unable to mount /cache
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
Unable to mount /sdcard
My TWRP version is 2.6.3.1
I hope that helps.
Click to expand...
Click to collapse
which partition version is selected OtterX or Amazon?
sd_shadow said:
which partition version is selected OtterX or Amazon?
Click to expand...
Click to collapse
It should be OtterX, but the only way I know of access which it is, via the bootloader, doesn't show up in FFF.
kingsmaug said:
It should be OtterX, but the only way I know of access which it is, via the bootloader, doesn't show up in FFF.
Click to expand...
Click to collapse
You need to flash OtterX twrp and bootloader
Only OtterX twrp can handle OtterX partitions
Only OtterX bootloader can change partitions
See [Video] Flashing TWRP in OtterX bootloader
Sent from my XT907 using Tapatalk
sd_shadow said:
You need to flash OtterX twrp and bootloader
Only OtterX twrp can handle OtterX partitions
Only OtterX bootloader can change partitions
See [Video] Flashing TWRP in OtterX bootloader
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Ok. I was able to force it into fastboot, and then flash the otterx bootloader. I was able to confirm that they're otterx partitions, but it's still giving me the same startup errors about not being able to mount.
And then I rebooted to bootloader, and realized I forgot to change out of fastboot mode.
Double check the partition, and went into recovery, still getting the error about being unable to mount everything. So I manually mounted everything again.
I realized then that I needed to change TWRP to the otterx version, so I got it back into fastboot and flashed that. Now it'll mount /cache, but nothing else.
The truncated version of the opening log is:
can't mount /data
can't recreate /data/media
updating partition
can't mount /data
can't mount storage
can't mount /data/media during GUI startup
full SELinux support is present
can't mount /data/media/TWRP/.twrps when trying to read settings file
After that, I can manually mount the system in TWRP, but I can't mount data.
kingsmaug said:
Ok. I was able to force it into fastboot, and then flash the otterx bootloader. I was able to confirm that they're otterx partitions, but it's still giving me the same startup errors about not being able to mount.
And then I rebooted to bootloader, and realized I forgot to change out of fastboot mode.
Double check the partition, and went into recovery, still getting the error about being unable to mount everything. So I manually mounted everything again.
I realized then that I needed to change TWRP to the otterx version, so I got it back into fastboot and flashed that. Now it'll mount /cache, but nothing else.
The truncated version of the opening log is:
can't mount /data
can't recreate /data/media
updating partition
can't mount /data
can't mount storage
can't mount /data/media during GUI startup
full SELinux support is present
can't mount /data/media/TWRP/.twrps when trying to read settings file
After that, I can manually mount the system in TWRP, but I can't mount data.
Click to expand...
Click to collapse
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT907 using Tapatalk
sd_shadow said:
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Well, following that worked. Everything got cleared up, and now I'm loading into the ROM. Thank you!
unable to mount /data
No idea what happened.
Woke up today.. phone seemed off .. tried to charge and reboot and could not.
Got into recovery, and tried to wipe caches etc.. could not..
This is the message I get in logs from TWRP.
I read in another forum about going into the console and typing a manual command to reformat the partition.
I have no idea if that command would be the same here..
ANYONE??? please?
You didn't post the command, but just from common knowledge I'd say the Linux command would be the same, but the partition you need to format might be/probably is named differently on this phone.
Incidentally, there is always the possibility of partial or full emmc failure. Your description of the symptoms sound consistent with hardware failure, so I wouldn't rule out that possibility.
I just had the same thing happen. Can't find the command to manually reformat as well. My external SD card was wiped as well, apparently. Or it won't read it. TWRP also says internal storage is 0 mb.