So yesterday I posted that I was having issues after trying to load the HairBean from AndroWook, and after the WW_epaduser_10_4_2_9_UpdateLauncher.zip flash I lost my bootloader, and thought I was BRICKED.
After a LOT of reading about NVFLASH, and some posting in other website/forums, I've been able to recover my TFP and I'm looking at a Team EOS Jelly Bean nightly on it now.
Steps taken....(I'm running Ubuntu 12.04 on an old MacBook)
1) Download *externallinknotallowed*/androidroot.mobi/download/rec_bootloader.bin
2) In a terminal window run the following command
[email protected]:/home/charlie/Downloads/NVFLASH/tf201_nvflashpack# ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
3) Connected TFP to macbook and power cycled while holding the Volume UP key
[=] Chip UID: 0x98091256096231435
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:/home/charlie/Downloads/NVFLASH# ./nvflash --resume --download 4 rec_bootloader.bin
Nvflash v1.5.66719 started
[resume mode]
sending file: rec_bootloader.bin
/ 1021997/1021997 bytes sent
rec_bootloader.bin sent successfully
[email protected]:/home/charlie/Downloads/NVFLASH# ./nvflash --resume --go
Nvflash v1.5.66719 started
[resume mode]
The device rebooted and immediately went into TWRP.
I wiped everything and then installed fresh from external SDCARD the Team EOS nightly and the gapps packages.
I'm beyond happy that this worked.
--Charlie
Special thanks to jrodder for his post. Helped a lot mate!
so this really worked out?
i have the same problem with HairBean from AndroWook...
Yes it works! As long as you have the blob file from NVFlash setup... AND you download the file listed, you can recover the bootloader.
Sent from my vivow using Tapatalk 2
what if i don't have blob file?
Did you perform all the steps in the NVFlash recovery guide? It's part of those tools. It starts the NVFlash recovery via the wheelie command also included in that tool set.
Once you are in NVFlash recovery, then you can nvflash the file rec_bootloader.bin
Sent from my vivow using Tapatalk 2
ecatsab said:
Did you perform all the steps in the NVFlash recovery guide? It's part of those tools. It starts the NVFlash recovery via the wheelie command also included in that tool set.
Once you are in NVFlash recovery, then you can nvflash the file rec_bootloader.bin
Sent from my vivow using Tapatalk 2
Click to expand...
Click to collapse
I too did this to get the bootloader back, but something is much worse for me. I have a thread in the other general forum here:
*edit* I guess it got moved to this forum, sorry!
http://forum.xda-developers.com/showthread.php?p=32041006
It really looks like I hosed my partitions somehow after the initial HB failure. When I flashed the original JB rom, I saw it tried to do a /system format I think, and it was all bad after that. Can you maybe do me a HUGE favor and do an adb shell, and post the output of "df -h"? I seem to be missing at the very least a /staging partiton amongst others, and an desperately trying to find a way to get the partition structure fixed so I can flash. Thanks!
jrodder said:
I too did this to get the bootloader back, but something is much worse for me. I have a thread in the other general forum here:
*edit* I guess it got moved to this forum, sorry!
http://forum.xda-developers.com/showthread.php?p=32041006
It really looks like I hosed my partitions somehow after the initial HB failure. When I flashed the original JB rom, I saw it tried to do a /system format I think, and it was all bad after that. Can you maybe do me a HUGE favor and do an adb shell, and post the output of "df -h"? I seem to be missing at the very least a /staging partiton amongst others, and an desperately trying to find a way to get the partition structure fixed so I can flash. Thanks!
Click to expand...
Click to collapse
I'll do this first thing when I go home for lunch. 1200 MST
Click to expand...
Click to collapse
Here is the df -h output from an adb shell while the TFP was in TWRP recovery.
Filesystem Size Used Available Use% Mounted on
tmpfs 491.5M 52.0K 491.4M 0% /dev
/dev/block/mmcblk0p2 421.3M 16.4M 404.9M 4% /cache
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /data
/dev/block/mmcblk1p1 14.9G 523.0M 14.4G 3% /external_sdcard
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /sdcard
/dev/block/mmcblk0p1 755.9M 262.3M 493.6M 35% /system
ecatsab said:
Here is the df -h output from an adb shell while the TFP was in TWRP recovery.
Filesystem Size Used Available Use% Mounted on
tmpfs 491.5M 52.0K 491.4M 0% /dev
/dev/block/mmcblk0p2 421.3M 16.4M 404.9M 4% /cache
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /data
/dev/block/mmcblk1p1 14.9G 523.0M 14.4G 3% /external_sdcard
/dev/block/mmcblk0p8 26.4G 274.1M 26.1G 1% /sdcard
/dev/block/mmcblk0p1 755.9M 262.3M 493.6M 35% /system
Click to expand...
Click to collapse
Thanks, that's what I have as well, at first glance. Can you paste what your /etc/fstab is by chance? It looks like my /system partition isn't mounting on a regular boot, only when done manually via TWRP...
(adb pull /etc/fstab filename.txt)
Mine:
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
Click to expand...
Click to collapse
jrodder said:
Thanks, that's what I have as well, at first glance. Can you paste what your /etc/fstab is by chance? It looks like my /system partition isn't mounting on a regular boot, only when done manually via TWRP...
(adb pull /etc/fstab filename.txt)
Mine:
Click to expand...
Click to collapse
Just went back into the shell and did a cat on /etc/fstab.....
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext3 rw
/dev/block/mmcblk0p2 /cache ext3 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
Here is what is is output with the mount command in the shell......
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk0p8 on /sdcard type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
I hope this helps.
ecatsab said:
Just went back into the shell and did a cat on /etc/fstab.....
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext3 rw
/dev/block/mmcblk0p2 /cache ext3 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
Here is what is is output with the mount command in the shell......
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk0p8 on /sdcard type ext3 (rw,relatime,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
I hope this helps.
Click to expand...
Click to collapse
It might, it might not. Honestly, I am feeling totally lost. I just wish I knew how to make this tablet work again. I have full access to it, and am just not sure what I need to attack. So when you boot into TWRP 2.2.2, and check the mounts, is /system already mounted? Mine isn't, and I am thinking that's the issue. I can manually mount in TWRP and all the ROM data is there...
jrodder said:
It might, it might not. Honestly, I am feeling totally lost. I just wish I knew how to make this tablet work again. I have full access to it, and am just not sure what I need to attack. So when you boot into TWRP 2.2.2, and check the mounts, is /system already mounted? Mine isn't, and I am thinking that's the issue. I can manually mount in TWRP and all the ROM data is there...
Click to expand...
Click to collapse
I have to actually check the box to mount system. Usually it's not mounted.
I would try loading a Team EOS nightly or some other ROM just to see if you are able to get a basic load on it.
Having access to TWRP (TFP version right!?!?!) you should be able to perform all the functions of loading/flashing a ROM.
When I recovered my bootloader, I went into TWRP, performed a wipe on all partitions (even if they failed) and then loaded Team EOS JB Nightly with gapps.
I was running CM10 before I did the HairBean failure.
--Charlie
ecatsab said:
I have to actually check the box to mount system. Usually it's not mounted.
I would try loading a Team EOS nightly or some other ROM just to see if you are able to get a basic load on it.
Having access to TWRP (TFP version right!?!?!) you should be able to perform all the functions of loading/flashing a ROM.
When I recovered my bootloader, I went into TWRP, performed a wipe on all partitions (even if they failed) and then loaded Team EOS JB Nightly with gapps.
I was running CM10 before I did the HairBean failure.
--Charlie
Click to expand...
Click to collapse
We both were then, I as well was running CM10. I have tried about 4 or 5 different roms, and nothing will boot. I have wiped everything over and over. Everything ends up with the same result, the Eee Pad bootloader screen using AndroidBoot loader, and the rom never loads up. I reflashed the recovery several times as well, just in case. The warning from Androwook page about the whole TF300 recovery thing worries me. :/ So am I supposed to be using a TF300 recovery, since I was broken halfwat there? (I tried)
**NOTE** Before proceeding please note that by following these instructions and flashing this ROM you are essentially turning you TF201 into a TF300. Therefore if you have issues with or want to update recovery for example you must use the TF300 recovery and NOT the TF201 version unless other wise stated. By using the incorrect version you could BRICK YOUR PRIME IRREVERSIBLY!! You have been warned...!! **NOTE**
Click to expand...
Click to collapse
jrodder said:
We both were then, I as well was running CM10. I have tried about 4 or 5 different roms, and nothing will boot. I have wiped everything over and over. Everything ends up with the same result, the Eee Pad bootloader screen using AndroidBoot loader, and the rom never loads up. I reflashed the recovery several times as well, just in case. The warning from Androwook page about the whole TF300 recovery thing worries me. :/ So am I supposed to be using a TF300 recovery, since I was broken halfwat there? (I tried)
Click to expand...
Click to collapse
I hope you're subscribed to this thread, my man. I see you're green... lol. Anyway, it looks like my /system is the difference here. Did you mount the /system then in TWRP mounts menu before you issue a mount command? Check this out: Also, ext4 partitions, but I don't think that should matter.
cat /etc/fstab
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk1p1 /external_sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext rw
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /sdcard type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Click to expand...
Click to collapse
Anyone have an idea? Should I make a fresh thread with specific questions?
Warning..... Code
Everything in BOLD are notes
This was ran after booting the device into TWRP, then running adb shell in a linux terminal
~ # mke2fs -t ext3 -m 0 /dev/block/mmcblk0p8
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p8 is apparently in use by the system; will not make a filesystem here!
~ # umount /dev/block/mmcblk0p8
~ # mke2fs -t ext3 -m 0 /dev/block/mmcblk0p8
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1757840 inodes, 7023232 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
215 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # blkid
/dev/block/mmcblk0p8: UUID="8d2f6f94-082c-4ec8-87e7-0ef7f6f3bf9f" TYPE="ext3"
/dev/block/mmcblk0p4: UUID="eceb44ac-5cd8-4a55-be93-1046eb25c887" TYPE="ext3"
/dev/block/mmcblk0p2: UUID="f7c6a895-ad00-4103-aa9c-009b0639cd78" TYPE="ext3"
/dev/block/mmcblk0p1: UUID="6070af7b-4190-4e36-85d2-3e0a7661e636" TYPE="ext4"
Notice that the system block device is still ext4. TWRP tried wiping it but failed earlier
~ # mke2fs -t ext3 -m 0 /dev/block/mmcblk0p1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
49152 inodes, 196608 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=201326592
6 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.
I mounted all the partition checkboxes in TWRP recovery
~ # blkid
/dev/block/mmcblk1p1: UUID="48A0-C8EC" TYPE="vfat"
/dev/block/mmcblk0p8: UUID="8d2f6f94-082c-4ec8-87e7-0ef7f6f3bf9f" TYPE="ext3"
/dev/block/mmcblk0p4: UUID="eceb44ac-5cd8-4a55-be93-1046eb25c887" TYPE="ext3"
/dev/block/mmcblk0p2: UUID="f7c6a895-ad00-4103-aa9c-009b0639cd78" TYPE="ext3"
/dev/block/mmcblk0p1: UUID="87de235c-e978-43c5-997f-76eef8910187" TYPE="ext3"
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /external_sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ #
Click to expand...
Click to collapse
Still having an issue with loading any other ROM than Team EOS JB Nightly
TWRP Output from log file when flash was failing. Can someone (or you) assist in what that error is?
-- Install /sdcard/goomanager/cm-10-20120924-NIGHTLY-tf201.zip ...
Finding update package...
I:Update location: /sdcard/goomanager/cm-10-20120924-NIGHTLY-tf201.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "tf201" || getprop("ro.build.product") == "tf201"
assert failed: getprop("ro.product.device") == "tf201" || getprop("ro.build.product") == "tf201"
E:Error in /sdcard/goomanager/cm-10-20120924-NIGHTLY-tf201.zip
(Status 7)
Click to expand...
Click to collapse
Nevermind. I just went into the update script in the zip and removed that line. A
Running CM10 now.
ecatsab said:
Everything in BOLD are notes
This was ran after booting the device into TWRP, then running adb shell in a linux terminal
Still having an issue with loading any other ROM than Team EOS JB Nightly
TWRP Output from log file when flash was failing. Can someone (or you) assist in what that error is?
Nevermind. I just went into the update script in the zip and removed that line. A
Running CM10 now.
Click to expand...
Click to collapse
No kidding. I was figuring the recovery was smart enough to format with the correct type, considering I verified that the recovery was flashing data to the system partition without a problem, just wouldn't boot up. I will try changing mine to ext3 as well and post back with results.
ecatsab said:
Yes it works! As long as you have the blob file from NVFlash setup... AND you download the file listed, you can recover the bootloader.
Sent from my vivow using Tapatalk 2
Click to expand...
Click to collapse
which blobfile you mean? can you please upload your blobfile so i can use it too :/ would be very nice man..because im trying to follow your guide..but my problem is i dont know which blob you mean..and what did you do with ubuntu? for what is that? please help!
kind regards
edit: ok now i know what you mean..i had to do a special process for getting this blob.bin via fastboot..damn! -.- can you upload your blob.bin though..maybe it will work ! i have nothing to lose anymore.
0din said:
which blobfile you mean? can you please upload your blobfile so i can use it too :/ would be very nice man..because im trying to follow your guide..but my problem is i dont know which blob you mean..and what did you do with ubuntu? for what is that? please help!
kind regards
edit: ok now i know what you mean..i had to do a special process for getting this blob.bin via fastboot..damn! -.- can you upload your blob.bin though..maybe it will work ! i have nothing to lose anymore.
Click to expand...
Click to collapse
How broken are you? Did you reflash the bricksafe.img via nvflash?
jrodder said:
How broken are you? Did you reflash the bricksafe.img via nvflash?
Click to expand...
Click to collapse
i have a bootloop to asus logo..cant use fastboot or adb..just have the apx-mode! coming from cm10,cwm 5.8.2.0.. tried to flash TWRP via Android Terminal Emulator..after that started in recovery mode..and then the bootloop began..i didnt flash any nvflash stuff before..thats why I'm asking for his blod-file..coz maybe it will work. Hope dies last. cheers
0din said:
i have a bootloop to asus logo..cant use fastboot or adb..just have the apx-mode! coming from cm10,cwm 5.8.2.0.. tried to flash TWRP via Android Terminal Emulator..after that started in recovery mode..and then the bootloop began..i didnt flash any nvflash stuff before..thats why I'm asking for his blod-file..coz maybe it will work. Hope dies last. cheers
Click to expand...
Click to collapse
Now, you have no recovery at all? I don't think you can nvflash without running the nvflash procedure first. I could be totally off base, but pretty sure there's some signing and encryption involved with the blob.bin creation. Anyone else reading this feel free to correct me.
jrodder said:
I don't think you can nvflash without running the nvflash procedure first. I could be totally off base, but pretty sure there's some signing and encryption involved with the blob.bin creation. Anyone else reading this feel free to correct me.
Click to expand...
Click to collapse
you are correct sir, thank you.
sent from my i9250
Related
For some reason my sd-card partition can't be mounted anymore by cwm after I followed this guide http://forum.xda-developers.com/showthread.php?t=1601942 to stop cwm boot loop into recovery.
My CM10 doesn't boot anymore after I flashed latest version (2012-08-06) and I'm trying to manually adb shell into the tf201 to try and mount the partition myself.
What's the block device for sdcard?
I have:
Code:
# ls /dev/block
loop0 loop4 mmcblk0 mmcblk0p3 mmcblk0p7 sda
loop1 loop5 mmcblk0p1 mmcblk0p4 mmcblk0p8 sda1
loop2 loop6 mmcblk0p10 mmcblk0p5 mmcblk0p9
loop3 loop7 mmcblk0p2 mmcblk0p6 platform
and the following is mounted:
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /system type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
fstab
Code:
# cat /etc/fstab
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p1 /system ext4 rw
and trying to mount mmcblk0p8:
Code:
# mount /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
help?
Ok, RaYmAn on the irc channel helped me out! I cleared my mmcblk0p8 partition with fastboot:
Code:
fastboot -i 0xb05 erase userdata
And voila! Now I can use /data to copy my roms to and use CWM to flash them.
Thanks all! Peace!
can u please elaborate more on this? how to fastboot and stuff? i cannot flash other roms after i flashed recovery v5.5.0.4 because in recovery my sd card is not seen
dimushor said:
can u please elaborate more on this? how to fastboot and stuff? i cannot flash other roms after i flashed recovery v5.5.0.4 because in recovery my sd card is not seen
Click to expand...
Click to collapse
Go into the dev thread, look at the twrp thread there, it explains how to use fastboot. If I were you I would seriously consider installing twrp, isn't that an old version of cwm your using?
http://forum.xda-developers.com/showthread.php?t=1615990 TWRP external sd card support
http://forum.xda-developers.com/showthread.php?t=1533697 CWM 5.8.2.0
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.
So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?
thanks!
Adromir said:
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.
So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?
thanks!
Click to expand...
Click to collapse
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
Because with just the stock Recovery it doesn't mount all needed partitions correctly. I took the stock recovery i extracted from the latest RUU.
give me the stock recovery and i will do the recovery.fstab for you
globula_neagra said:
give me the stock recovery and i will do the recovery.fstab for you
Click to expand...
Click to collapse
Here it is. Thats really great! Thanks a lot
try this recovery
what i did, i used the recovery.fstab from this http://forum.xda-developers.com/showthread.php?t=1484753
i would like to try the recovery from the 4ext and see what mount points and how the filesystem is managed.
if you have one share`it with me.
the attached files is the cwm that i cooked, using the stock recovery and adding the fstab from the 5.8 cwm
you can flash it and see what results you have (if you get anny errors)
but don`t use the recovery to flash something till you don`t get the mount results to see if the mounting points are like this, if the mounting points are like this you should be ok to try and flash a rom.
# mount point fstype device
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
to find out the mounting points
adb shell
mount
and you should have a long output like this (This are not from a htc desire s ! )
C:\Android\android-sdk\platform-tools>adb shell
uid=0 [email protected]:/ # mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,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)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p12 on /system type ext4 (ro,relatime,user_xattr,barrier=1,dat
a=ordered)
/dev/block/mmcblk0p13 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,ba
rrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p14 on /persist type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,b
arrier=1,data=ordered)
/dev/block/mmcblk0p17 on /content type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/vold/179:97 on /mnt/external_sd type vfat (rw,dirsync,nosuid,nodev,no
exec,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:20 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:20 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,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)
uid=0 [email protected]:/ #
Thanks for your effort, but i can't test the recovery properly because there is a key missing to run an option. I can browse through the menu with volume +/- though, but can't enable the selected option.
I found an 4ext Recovery (version 1005.5.0), i attached it with the fstab i extracted from it
well, i could use the maping key from the cwm 5.8
there are some cwm`s that need enabling
for example on a tablet i need to press 27 times the volume key -, or a combination of + - + (volume keys) to enable the selection.
i can not test the recovery, i will rebuild later on a version based on the 5.8 key maping.
on the screen did you got any errors ?
No, it didnt show any errors yet. Is it possible to make it touch too? I tried to cook up a cwm with the fstab of 4ext but it completly failed to load any partition. 4ext itself is working though
here is the touch one, check also if the key`s are working
the recovery that you made, the keys where working ?
Havent tried the keys on my Build, but with yours they are working.
In the cwm i got this errors:
I:Skipping execution of extended command, file not found
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
Now trying to make a Backup, that seems to work, but i am not completly sure, havent tried to restore it yet. Will do that tomorrow
this is the first cwm that i made for you, but with the key maping from the stock recovery
http://www.mediafire.com/?kc8dk9gl2c9660o
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
you can check the recovery files on the sd card, if you see there the boot.img recovery, and system/data mds5 it should be ok to restore.
Is this different from the built you attached last? This works fine with the keys.
btw. can you maybe give me some tips how you built it? Later i want to make a new cwm for my tablet, but i dont want to bother you with that too
yes it is different, it is like the first build but i used the key mapping from the htc desire s stock recovery, the one from the ruu
well the tips are, keep trying till you get something working.
for example on my tablet i am using a htc sensation xl recovery (not all the stuff only the recovery which is in the sbin directory if you unpack the recovery)
unpack the stock recovery, and analyse the recovery.fstab by comparing it to the mount points, if they are ok is very good, you will have bigger chance to get something working.
try and use the clockwork builder and see if you get any results, but select the stock recovery.fstab (you have the option when you cook the recovery, is the second option)
if you don`t get any results like this try to find a similar device from a spec point of view and steal the /sbin/recovery from the device cwm recovery, put it on your recovery, repack and test.
it depends on what tablet you have also
If you need help in the future, send me a pm, because i check only once per week this section of the forum.
Ok, found boot.img but no system/data and system.ext3.dup is only about 100kb of size. Is that correct?
in the logfile there are three errors:
W:Unable to get recovery.fstab info for /datadata during fstab generation
W:Unable to get recovery.fstab info for /emmc during fstab generation
W:Unable to get recovery.fstab info for /sd-ext during fstab generation
no, is not corect, that means that the recovery made by the clockworok server has some flaws
i will try to make a new one, based on 4ext recovery
---------- Post added at 07:47 PM ---------- Previous post was at 07:31 PM ----------
K, i remade the fstab
it looks like this now
# mount point fstype device
/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
/sd-ext ext4 /dev/block/mmcblk1p2 fstype2=ext4
/system_lib ext4 /dev/block/mmcblk0p28 fstype2=ext4
You could try and find a similar device that has the version 6 recovery and try the recovery from that device (am talking about getting the recovery, unpack it, take the recovery file which is in boot.img-ramdisk\sbin\recovery
In the end, it`s all about testing
I did all my stuff alone, nobody helped me.
http://www.mediafire.com/?69a74qq9idko02v this is the recovery based on the recovery.fstab from the 4ext recovery which looks more complete.
Thanks very, very much, i really appreciate your efforts. So now, i'll start trying and trying until i get a working one
Help me plz..
I don't haved knowledge about android scripting or any something like that,.. but I was try hard to get and learn about creating CWM of my stock recovery.img .. after all is unfortunately .. always failed.
I haved try on builder.clockworkmod.com but itsn't success,...
would any member in here should help me to create CWM from my stock recovery.img please... my phone is One Scribe ZA987 with MTK6577
Hi Guys, I have a quick question
I am new to this but im learning quickly.... I think!
im making up my own recovery and so far my recovery.fstab looks like this:
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/cache ext4 /dev/block/mmcblk0p10 fstype2=ext3
/data ext4 /dev/block/mmcblk0p12 fstype2=ext3
/system ext4 /dev/block/mmcblk0p11 fstype2=ext3
/factory ext4 /dev/block/mmcblk0p4 fstype2=ext3
/crypo emmc /dev/block/mmcblk0p3
but when trying to do a backup it throws up an error saying it cant write to SDCARD, which makes sense as its not mounted
So, the question is, how do I go about mounting it for recovery?
Now, the sdcard is internal, there is no external card, I believe its symlinked to /storage/sdcard within android which is all located in the partition /data/ (mmcblk0p12)
sooo, can anyone help, ive been trawling the interweb and I can find lots of ways to do this within the main OS, but how do I go about it for recovery.fstab to be used in a custom clockwork recovery img
globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
can you explain to me how to dump? my phone is brigadier
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.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.
ghirux said:
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.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.
Click to expand...
Click to collapse
have you tried repairing system via twrp?
toolhas4degrees said:
have you tried repairing system via twrp?
Click to expand...
Click to collapse
yes, I forgot to say it but yes. On /data and /sdcard the procedure fails, i think for the same reason that makes e2fsck fail too.
I'm almost sure that the memory is gone, I need to find a tool to test its functionality.
Whatever I write on there it gets deleted at the next reboot, I don't think it's normal.
thank you.
Hi,
Completely new to smartphones in general, I just bought a second-hand Samsung Galaxy S2 from a specialized website. I tried to install LineageOS on it but with no success so far (the LineageOS wiki for this device seems to forget some important things when starting from a stock ROM).
Current situation and things that might help:
I don't have a microSD card.
I have a backup of the original .pit file.
Even if I really do not want to use the stock ROM, I can not find a way to reinstall a working one: installation with Odin works but there is a "boot loop" on the Samsung logo.
Installing Replicant works, but it is unfortunately too extremist for me.
As I don't have a microSD card, I try installing with "adb sideload image_file.zip" (like I do with Replicant), but TWRP displays errors about partitions :
Code:
...
E:Unable to locate storage partition for storing settings file.
Updating partition details...
...done
Unable to find partition for path '/system'
Unable to find partition for path '/data'
MTP enabled
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Target: samsung/GT-I9100:4.1.2/JZ054K/I9100XWMS2:user/release-keys
detected filesystem ext4 for /dev/blockmmcblk0p9
detected filesystem ext4 for /dev/blockmmcblk0p10
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
Updater process ended with ERROR: 7
I tried doing a "factory reset" from TWRP but result is the same.
Here are some information that might be useful, gathered from an ADB shell:
/etc/recovery.fstab
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usbdisk0:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
/etc/mtab
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/tmp/recovery.fstab
Code:
...
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/dev/block/mmcblk0p9'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
'I:Processing '/dev/block/mmcblk0p7'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
'I:Processing '/dev/block/mmcblk0p1'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
'I:Processing '/dev/block/mmcblk0p10'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
'I:Processing '/dev/block/mmcblk0p12'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
'I:Processing '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0*'
E:Invalid block device 'auto' in fstab line '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,nonremovable,noemulatedsd
'I:Processing '/devices/platform/s3c-sdhci.2/mmc_host/mmc1*'
E:Invalid block device 'auto' in fstab line '/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
'I:Processing '/devices/platform/s3c_otghcd/usb*'
E:Invalid block device 'auto' in fstab line '/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usbdisk0:auto
'I:Processing '/dev/block/mmcblk0p5'
E:Invalid block device 'emmc' in fstab line '/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
'I:Processing '/dev/block/mmcblk0p6'
E:Invalid block device 'emmc' in fstab line '/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
'E:Unable to locate storage partition for storing settings file.
Updating partition details...
...done
I:Unable to find storage partition '/'.
I:Unmounting main partitions...
Unable to find partition for path '/system'
Unable to find partition for path '/data'
...
I spent many hours hours on this issue and read many many things. I really hope someone will be able to help, or at least sympathise Feel free to ask if I can provide some information. Thanks!
Your life would be easier if you paid ten dollars for an SD card lol. My advice is to flash the stock ROM back. Root it. Install dual boot patcher apk and install lineage as data1. This way you avoid your headache and if anything goes wrong you can just boot back to the stock ROM and try again. Also are you sure you have the right ROM? S2 stuff is hard to find. I've been working on an s3 with no luck. Years ago I downgraded the bootloader and bricked it.
Interesting to know that dual boot with microSD card would be easier than only LineageOS (I am coming from the Linux word where it is generally simpler to remove Windows)… I will try to see that.
I got the stock ROM from samsung-updates.com/device/?id=GT-I9100. I am really disappointed to know that vendors like Samsung does not provide these officially.
Finally done it, thanks to people on Reddit! :victory:
Go to 3W dot reddit dot com/r/LineageOS/comments/603qeq/cannot_boot_into_twrp_on_samsung_galaxy_s2/ where the solution is written many times by different persons. Just note that you have to use TWRP 3.1.0, version 3.1.1 fails (see first post).
Now the goal is to update the LineageOS official wiki…
Hi everybody
Currently i have attached a F1 to my pc which has some weird conditions...
The phone itself seems to be flashed to latest LineageOS, but it is encrypted.
Maybe because of the latest sideload, i can't really tell because the owner gave this to a friend...
So, prefered solution would be: decrypt the phone, get all the pictures/videos from it.
Another acceptable solution would be: install from scratch.
But:
fastboot seems to be botched.
Code:
C:\adb>adb devices
List of devices attached
22fd65f3 recovery
Looking good, adb can access this device.
So, if i could flash some decrypt-voodoo that the device boots and decrypts system...
But no, failing so far.
Then i thought, well, as it is already gone, just fastboot flash and forward.
Nope:
Code:
C:\adb>fastboot devices
???????????? fastboot
And the device goes back to bootloop.
Booting to recovery gives me a TWRP 3.5.2_10-0
Full access, except the encrypted data.
recovery is fully working, so i tried to flash vbmeta with fastboot (--disable-verity --disable-verification) but fastboot seems to be broken.
So... any thoughts where to start first?
Thx
I pulled fstab from phone:
twrp.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# mount point type device device2 flags
/boot emmc /dev/block/bootdevice/by-name/boot flags=display="Boot"
/cache ext4 /dev/block/bootdevice/by-name/cache
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=display="Recovery";backup=1
/system ext4 /dev/block/bootdevice/by-name/system flags=backup=1;wipeingui;display="System"
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=backup=1;wipeingui;display="Vendor"
/system_image emmc /dev/block/bootdevice/by-name/system flags=backup=1;flashimg=1
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=backup=1;flashimg=1
/data ext4 /dev/block/bootdevice/by-name/userdata flags=encryptable=footer;length=-16384;fileencryption=ice:aes-256-cts:aes-256-heh
/firmware vfat /dev/block/bootdevice/by-name/modem flags=display="Firmware";mounttodecrypt
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust"
/misc emmc /dev/block/bootdevice/by-name/misc
/modem emmc /dev/block/bootdevice/by-name/modem flags=backup=1;display="Modem"
/bluetooth emmc /dev/block/bootdevice/by-name/bluetooth flags=backup=1;subpartitionof=/modem
/dsp emmc /dev/block/bootdevice/by-name/dsp flags=backup=1;subpartitionof=/modem
/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display=EFS
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/efsc emmc /dev/block/bootdevice/by-name/fsc flags=backup=1;subpartitionof=/efs1
/efsg emmc /dev/block/bootdevice/by-name/fsg flags=backup=1;subpartitionof=/efs1
/persist ext4 /dev/block/bootdevice/by-name/persist flags=display="Persist"
/storage ext4 /data/media/0 flags=display="Internal Storage";usermrf;backup=1;fsflags="bind";removable
# Removable storage
/usb_otg vfat /dev/block/sdg1 /dev/block/sdg flags=display="USB-OTG";storage;wipeingui;removable
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 flags=display="MicroSD Card";storage;wipeingui;removable
recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem e2fsck binary (typically /system) cannot
# specify 'check', and must come before any filesystems that do specify 'check'
# NOTE: /system and /vendor partitions are early-mounted and the fstab entry is specified in device tree (duplicated below for recovery image purposes only):
# /proc/device-tree/firmware/android/fstab/system
# /proc/device-tree/firmware/android/fstab/vendor
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=0,noauto_da_alloc latemount,wait,check,fileencryption=ice,quota,encryptable=footer
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/boot /boot emmc defaults recoveryonly
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults recoveryonly
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,recoveryonly
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait,recoveryonly
/devices/platform/soc/8804000.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=footer
/devices/platform/soc/a600000.ssusb/a600000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
and the regular fstab
Code:
/dev/block/sda20 /cache ext4 rw 0 0
/dev/block/sde48 /system_root ext4 ro 0 0
/dev/block/sde47 /vendor ext4 ro 0 0
/dev/block/sda21 /data ext4 rw 0 0
/dev/block/sde46 /firmware vfat rw 0 0
/dev/block/sda18 /cust ext4 rw 0 0
/dev/block/sda14 /persist ext4 rw 0 0
/storage ext4 rw 0 0
/usb_otg vfat rw 0 0
/external_sd vfat rw 0 0
Lonesome Walker said:
Hi everybody
Currently i have attached a F1 to my pc which has some weird conditions...
The phone itself seems to be flashed to latest LineageOS, but it is encrypted.
Maybe because of the latest sideload, i can't really tell because the owner gave this to a friend...
So, prefered solution would be: decrypt the phone, get all the pictures/videos from it.
Another acceptable solution would be: install from scratch.
But:
fastboot seems to be botched.
Code:
C:\adb>adb devices
List of devices attached
22fd65f3 recovery
Looking good, adb can access this device.
So, if i could flash some decrypt-voodoo that the device boots and decrypts system...
But no, failing so far.
Then i thought, well, as it is already gone, just fastboot flash and forward.
Nope:
Code:
C:\adb>fastboot devices
???????????? fastboot
And the device goes back to bootloop.
Booting to recovery gives me a TWRP 3.5.2_10-0
Full access, except the encrypted data.
recovery is fully working, so i tried to flash vbmeta with fastboot (--disable-verity --disable-verification) but fastboot seems to be broken.
So... any thoughts where to start first?
Thx
Click to expand...
Click to collapse
If the phone doesn't recognize in fastboot you need the fix and the drivers.
You can find everything you need in my POCO F1 Ultimate Collection & Guides.
Check AMD/Intel Fastboot Fix.
If you know pin/pattern you can flash the TWRP by REIGNZ go to recovery put pin/pattern to decrypt then connect your device to pc while you are in twrp (if MTP doesn't work at first go advanced>file manager> and choose sdcard0 (internal storage) then your device shoule recognized in pc and get your data.
To clean flash follow my clean installation guide.
Everything you need is on my thread I mentioned above.
Okay, this is interesting...
My own Poco F1 had no issues with the drivers installed before.
After updating, the actual bugged F1 can fastboot but my own can't anymore.
WTF?
I also switched cables, doesn't matter.
Okay, nevertheless, mine is not broken, so this will be a task for later...
Thank you so far for this working hint!
So, i now finally have rescued all the pictures, videos and Whatsapp stuff.
My friend is happy.
The next step would be flashing the Pixel Experience.
But: how to find out which Android version is currently installed?
Or should i flash the latest stock rom from Xiaomi? I mean, it can't be higher than that, right?
Thank you for your response!