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
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.
Hello,
I am flashing roms since nearly two years and I got my first big problem 2 days ago.
My GT-i9100 (DBT Germany) was running stable under cm-12.1-20150611-UNOFFICIAL-i9100.zip brought by Lysergic Acid.
When I tried to log on WLAN on Tuesday morning, my rom crashed with a few percent of energy remaining. I charged my battery and started the phone again. I had a message "No Service" and a barred circle. Pin Code was being asked, as well as my lock screen Pin Code.
I thought it was a mobile network operator issue, and that it would be temporary. Didn't care about it, I was able to log in my WLAN network. Then I saw an update (06/17) on xda, that I downloaded and flashed following the installation instructions. I noticed still the "No service" message and the circle barred. I looked at my telephone settings an saw Unknown Baseband, No Signal, Unknown Imei. When I called *#6#, there was a popup with only the Text IMEI no number.
Finally I did sthg really stupid (I didn't google Unknown Baseband Unknown Imei at this time), because I thought wrongly that the issue is a rom, modem or csc issue. Then I decided to flash back to a stable jelly bean version.
Thus, I had to flash the partition with Stock i9100 pit, because I was using a preload modified area partition before.
Then I made my great mistake, that's what I think now, I think I corrupted my /efs folder. I installed a stock firmware from sammobile on my SII (still no service, unknown baseband), then rooted the phone again, and installed
ASNET MIUI v5 (4.8.10) everything is working except this my mobile network unknown baseband, unknown Imei, etc
I tried to look on my external harddrive, if I had any backups from my phone, did not have any /efs backup. :crying:
With root explorer I am able to to see the /efs folder no file is missing I think, but it is certainly corrupt. I am joining a .tar file of this folder here. https mega.nz/#!4IZijDTK!2eZ1lhC01bTEcbzwP7OVe8tePiIm5GNQ_dwpZRZHF0k
~ $ 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/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=writeback)
/dev/block/mmcblk0p12 on /preload type ext4 (ro,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
~ $ su
[email protected]:/ # #
[email protected]:/ #
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 422816 76 422740 0% /dev
tmpfs 422816 0 422816 0% /mnt/asec
tmpfs 422816 0 422816 0% /mnt/obb
/dev/block/mmcblk0p9 516040 453384 62656 88% /system
/dev/block/mmcblk0p7 100784 4160 96624 4% /cache
/dev/block/mmcblk0p1 20144 10492 9652 52% /efs
/dev/block/mmcblk0p12
516040 77688 438352 15% /preload
/dev/block/mmcblk0p10
2064208 306208 1758000 15% /data
df: /mnt/.lfs: Function not implemented
/dev/block/vold/259:3
12063840 445792 11618048 4% /storage/sdcard0
1|[email protected]:/ # mount /efs
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /data
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /preload
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /cache
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /system
mount: can't read '/etc/fstab': No such file or directory
I still have the IMEi on the back of my phone.
Is there a way to fix this or is it impossible?
Good day,
The situation at hand:
- Samsung SM-G900F
- CM 14.1 (or what ever the last official CM Build was)
- rooted ("#" in ABD SHELL is shown)
- non-functional display (no input it seems and black. glorious spider-app)
- phone is booting normally (TWRP recovery + download mode included)
- ADB only works in recovery
So, as the phone is still working fine (apart from keeping everything for itself) I'd figure I could use programs like "MyPhoneExplorer", DDMS, or anything to use it while I'm waiting to get a new one.
Only thing that keeps me from doing so - my phone is on "charging mode" when plugged in USB and normally booted.
In order to activate the "usb debugging" (and set it as default) I tried to pull the "build.props" from /system - however, ADB keeps telling that folder doesn't exist.
I thought at first, there'd be an problem with RO/RW settings but when trying to remount /system I'm getting this:
Code:
~ # ←[6nmount -o w,remount /system
mount -o w,remount /system
mount: can't find /system in /proc/mounts
When checking with ADBFileExplorer, the folder "system" is there but completely empty.
Running #mount results in
Code:
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel)
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/mmcblk0p26 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p26 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p24 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
I assume (or rather: I fear), I'd have to enable "system" for mounting in the TWRP screen to be able to temper with my build.prop.
Maybe someone can shed a light and show me, what I got to do to access /system and build.prop?
(Apart from getting a new display.)
Greetings
I believe you need to call "/sys" instead of "/system" so it can be found in /proc/mounts where the mount requirement are stored
Pan0ptics said:
I believe you need to call "/sys" instead of "/system" so it can be found in /proc/mounts where the mount requirement are stored
Click to expand...
Click to collapse
help!
my audio daemon services are not running in latest nitrogen pie rom.it was running before on other pie rom on redmi 3s
some bug reports generated .
i did all possible simple solution like factory reset or complete clean flash of stock rom or tried other older rom like rr oreo rom but no luck .
and i mounted system partition as rw it resets to ro after every reboot.
maybe strace is not running properly it is mentioned in bug report