Related
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
I'm trying to port CWM for my device.
I need to replace iunin with CWM.
The problem is that I cannot extract the recovery img. I have a recovery.img but cannot edit/mount it (tried as ext2/3/4, gzip and so on).
Recovery is flashed as fastboot flash recovery.img (what type of image is this .img file??).
Here are is the recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p2
/cache ext3 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p3
/kernel mtd kernel
/ramdisk mtd ramdisk
/misc mtd misc
/boot mtd boot
/recovery mtd recovery
/bootloader mtd bootloader
/radio mtd radio
I have read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images and similar posts but they don't work for me (no Android magic...).
Please point me in the right direction, how to mount this recovery.img file - that's all I need.
Thank you!
mexusbg said:
I'm trying to port CWM for my device.
I need to replace iunin with CWM.
The problem is that I cannot extract the recovery img. I have a recovery.img but cannot edit/mount it (tried as ext2/3/4, gzip and so on).
Recovery is flashed as fastboot flash recovery.img (what type of image is this .img file??).
Here are is the recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p2
/cache ext3 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p3
/kernel mtd kernel
/ramdisk mtd ramdisk
/misc mtd misc
/boot mtd boot
/recovery mtd recovery
/bootloader mtd bootloader
/radio mtd radio
I have read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images and similar posts but they don't work for me (no Android magic...).
Please point me in the right direction, how to mount this recovery.img file - that's all I need.
Thank you!
Click to expand...
Click to collapse
Just to clarify you are trying to mount the recovery.img on your PC?
thewadegeek said:
Just to clarify you are trying to mount the recovery.img on your PC?
Click to expand...
Click to collapse
Yeah I'm trying to mount the recovery.img and replace iunin recovery files with cwm's files.
I tried:
gunzip -c ../your-ramdisk-file | cpio -i
gzip: recovery.img: not in gzip format
cpio: premature end of archive
./split_bootimg.pl recovery.img
Android Magic not found in recovery.img. Giving up.
Also I don't have /dev/mtd/ ....
I've attached the recovery.img file if someone want's to check it out.
EDIT: I tired dsixda-Android-Kitchen and still cannot mount/unpack recovery.img.
EDIT2: List of other files in the update.zip:
zImage-GB-v746-2703 - KERNEL
system-GB-1.3-2703.ext4 (EXT4 image) - System
ramdisk-uboot-GB-1.3-2703.img - ramdisk
ramdisk-recovery-uboot-GB-1.0.img - recovery
Link to the whole firmware: https://dl.dropbox.com/u/41124284/A8HD/Firmware/um2703-GB-1.3-sdUp-381.zip
Please help me.
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
First off, mods, if this is in the wrong place sorry, secondly, thanks for the help in advance.
I have dsixda's kitchen set up via cygwin, but do not have the proper files in the edify_defs folder so that the kitchen knows the proper mount points. What I am talking about is in the following bit quoted from the original kitchen thread.
WARNING: If your device is not listed in post #1 of this thread, and it does NOT use a 'YAFFS'-based filesystem (e.g. usually only low-end devices use YAFFS), do not attempt to flash a ROM that you built with this kitchen. Instead, you must do the following if your device is NOT listed:
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
NOTE: This method does not guarantee your device will work with your custom ROM, however. Some devices may require more steps than just the edify_defs file, but the procedure is outside the scope of this FAQ. Ask around in the XDA sub-forum for your device if you need further help.
Click to expand...
Click to collapse
The devices I would like to add are both the first gen Nexus 7 (nakasi/grouper) and second gen Nexus 7 (flo). When I follow the instructions from that quoted section I am unable to make sense of the listed mount points and how to create the proper files. Any help is appreciated, thanks!
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
danger_beast said:
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
Click to expand...
Click to collapse
Yes, going to sell the first gen N7, so just would like to add support for the 2nd gen (flo/razor).
dark2099 said:
Yes, going to sell the first gen N7, so just would like to add support for the 2nd gen (flo/razor).
Click to expand...
Click to collapse
would like to add support for LG-E510, I've tried many times, help
---------- Post added at 07:59 PM ---------- Previous post was at 07:38 PM ----------
here is my fstab file:
# Mount point fstype device [device2]
/ boot mtd boot
/ cache yaffs2 cache
/ data yaffs2 userdata
/ misc mtd misc
/ recovery mtd recovery
/ sdcard vfat / dev/block/mmcblk0p1 / dev/block/mmcblk0
/ system yaffs2 system
help me
danger_beast said:
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
Click to expand...
Click to collapse
No one can help:good:
giltros1 said:
No one can help:good:
Click to expand...
Click to collapse
Mobile name?? version >> android
danger_beast said:
Mobile name?? version >> android
Click to expand...
Click to collapse
Mobile name: LG-E510, LG optimus Hub
Version android 2.3.6
Thanks
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
giltros1 said:
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Click to expand...
Click to collapse
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
So if u got the ro.product.device ID (can be found in build.prop its easy then follow the steps above.....)
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
giltros1 said:
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Click to expand...
Click to collapse
Could u upload and pm me the files??
Hey guys, I was recently given a Galaxy Tab 3 Lite (SM-T110) and have found very little roms considering its an old tablet and none are with my latest stock firmware. That said, I'm trying to implement this tablet into dsixda's kitchen but am having a little bit of trouble.
I have set up the kitchen successfully on Windows 10 using cygwin and have even complied a rom successfully but the problem is when I flash it it gives me errors about boot.img mounting points. I pretty much have 3 questions:
1. Cant find my boot mnt point and was wondering if someone can help me find it? (ill attach my recovery.fstab file in the bottom for you to see)
2. Dont really know if I need that "fix_boot2=yes" line? "fix_boot=yes" line? Or none? How can I tell if i need it?
3. Since boot mount point is not inside recovery.fstab file, does that mean it is not need to be mentioned?
I made a file called "goyawifi" inside the edify_defs folder with the following info inside it:
# Samsung Galaxy Tab 3 Lite SM-T110
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p15
cache_mnt=\/dev\/block\/mmcblk0p14
boot_mnt=\/dev\/block\/mmcblk0p15
data_mnt=\/dev\/block\/mmcblk0p16
sdcard_mnt=\/dev\/block\/mmcblk1p1
fix_boot2=yes
And this is my recovery.fstab info:
#mount point fstype device [device2]
/mrd emmc /dev/block/mmcblk0p1
/mrd1 emmc /dev/block/mmcblk0p2
/mep2 emmc /dev/block/mmcblk0p3
/efs ext4 /dev/block/mmcblk0p4
/dtim emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p9
/kernel emmc /dev/block/mmcblk0p10
/radio emmc /dev/block/mmcblk0p11
/custom ext4 /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p16 length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/mnt/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Can anyone please help me to start customizing/flashing my rom? Thanks in advance...
FWI: When I say "successfully compiled a rom" I mean that the kitchen makes a rom, but upon flashing it, it gives me an error. Something about boot.img not mounted right
Bump! 45 views and no replies? So many developers here, surely someone knows the answer to my problems
Tried again to build a rom using dsixda's Android Kitchen, would like to find boot mount points... can anybody help?
Sorry, I don't have this device to test, but I think you should check "/kernel emmc /dev/block/mmcblk0p10"
Here should be the kernel image and maybe not the whole boot.img !
As you already know , boot.img have a kernel image and a ramdisk .... but on your device , ramdisk may be under /system ... I'm not 100% sure ... but from what you've posted so it seems !
So, there is no partition on your device for boot.img ... anyway you can make a custom rom also in this case, but you should know how to flash the new kernel image and also the ramdisk !
Unfortunately Samsung has made this device quite difficult for development, but not impossible .
Good luck !