In reference to the new storage configuration scheme mentioned in this thread
http://forum.xda-developers.com/showpost.php?p=54537828&postcount=677
I would like to create a new discussion for people who already implemented the re-partitioning of their phones following this method
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Please share your experience and confirm if the re-partitioning needs to be reverted prior to implementing the new storage scheme which uses fuse.
Donat.Callens said:
I would like to create a new discussion for people who already implemented the re-partitioning of their phones following this method
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Please share your experience and confirm if the re-partitioning needs to be reverted prior to implementing the new storage scheme which uses fuse.
Click to expand...
Click to collapse
Used that method, worked like a charm. Since I'm using AOSP and there have been zero updates for it, I probably won't reformat unless Fairphone starts updating their AOSP OS as well. Will update this post when/if they do.
to repartition or not to repartition
How about people with a repartitioned phone that applied the new storage scheme? Should we revert back to 1GB for the /data partition beforehand?
Donat.Callens said:
How about people with a repartitioned phone that applied the new storage scheme? Should we revert back to 1GB for the /data partition beforehand?
Click to expand...
Click to collapse
Hello, The partition upgrader rewrites MBR/EBR1/EBR2 *after* performing the update to the /system partition. It assumes the /system partition is not altered. I have not tried modifying the partition layout using the methods discussed on this forum (modifying the extended master boot record). As a result of the upgrade EBR2 is no longer used but remains present. MBR is not altered so only EBR2 and the PMT partition are modified before the cache and data partition are formatted. If only /data and the FAT partition are modified you should be fine. These are at the "end" of the disk.
I previously tried to download the APK from the link on the WIKI bellow but ended up downloading the wrong file(addware from the hosting company?) this is where I gave up.
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
download the repartitioning tool
_keesj said:
I previously tried to download the APK from the link on the WIKI bellow but ended up downloading the wrong file(addware from the hosting company?) this is where I gave up.
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Click to expand...
Click to collapse
Here is the original thread with the tool:
http://www.movilesdualsim.com/tema/...ilmente-data-apps-com-4gb-8gb-16gb-rom.31769/
This site refers to another download links to the same file:
http://www.china-devices.com/Thread-Tool-App-for-repartitioning-MTK-6589-Memory
As sear for Meteos MTK6589 will pop up many sites where it is to be found.
Donat.Callens said:
Here is the original thread with the tool:
http://www.movilesdualsim.com/tema/...ilmente-data-apps-com-4gb-8gb-16gb-rom.31769/
Click to expand...
Click to collapse
The original thread explains that you should perform a backup of EBR1 and EBR2 for safety. I assume this means only those two are modified. Could this mean we can apply the new cherry partitioning scheme on a re-partitioned phone without prior modification?
Note: hereby the mentionned commands for the backup
su
dd if=/dev/ebr1 of=/sdcard/EBR1 bs=512 count=1
dd if=/dev/ebr2 of=/sdcard/EBR2 bs=512 count=1
Donat.Callens said:
The original thread explains that you should perform a backup of EBR1 and EBR2 for safety. I assume this means only those two are modified. Could this mean we can apply the new cherry partitioning scheme on a re-partitioned phone without prior modification?
Note: hereby the mentionned commands for the backup
su
dd if=/dev/ebr1 of=/sdcard/EBR1 bs=512 count=1
dd if=/dev/ebr2 of=/sdcard/EBR2 bs=512 count=1
Click to expand...
Click to collapse
I changed my partition using the above tool and was able to perform a 1.3 -> 1.6 -> 1.6 FUSE update afterwards. This is not an endorsement but it does seam to work.
it did not seem to work for me
_keesj said:
I changed my partition using the above tool and was able to perform a 1.3 -> 1.6 -> 1.6 FUSE update afterwards. This is not an endorsement but it does seam to work.
Click to expand...
Click to collapse
I'm afraid I must report otherwise from my personal experience. I had previously re-partitioned my phone with a 4GB internal space storage. When applying the new FP partitioning schema, I did not loose my data as I should have. I am now stuck with bizarre values for the partition sizes. I will post the output of these commands here in my next post: df and mount. Please inform me if other information is required or if an official FP support request is preferable.
Donat.Callens said:
I will post the output of these commands here in my next post: df and mount.
Click to expand...
Click to collapse
$ df
Filesystem Size Used Free Blksize
/dev 487M 52K 487M 4096
/mnt/secure 487M 0K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/asec/com.camsam.plus-1 22M 19M 2M 4096
/mnt/asec/com.nuance.swype.dtc-1 36M 32M 3M 4096
/mnt/asec/com.koushikdutta.backup.license-1 1M 280K 1M 4096
/mnt/asec/ginlemon.flowerpro-1 5M 3M 1M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 351M 288M 4096
/data 3G 1G 2G 4096
/cache 124M 4M 119M 4096
/mnt/cd-rom 1M 1M 0K 2048
/protect_f 8M 4M 4M 4096
/protect_s 8M 4M 4M 4096
/storage/emulated 487M 0K 487M 4096
/storage/sdcard1 7G 6G 425M 32768
/storage/emulated/0 3G 1G 2G 4096
/storage/emulated/0/Android/obb 3G 1G 2G 4096
/storage/emulated/legacy 3G 1G 2G 4096
/storage/emulated/legacy/Android/obb 3G 1G 2G 4096
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.camsam.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/ginlemon.flowerpro-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:97 /storage/sdcard1 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 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Donat.Callens said:
I'm afraid I must report otherwise from my personal experience. I had previously re-partitioned my phone with a 4GB internal space storage. When applying the new FP partitioning schema, I did not loose my data as I should have. I am now stuck with bizarre values for the partition sizes. I will post the output of these commands here in my next post: df and mount. Please inform me if other information is required or if an official FP support request is preferable.
Click to expand...
Click to collapse
Can you please execute the following (as root e.g. adb shell ; su) and paste the result?
/system/bin/fp_part -r -f /dev/pmt | grep FAT; echo $?
_keesj said:
/system/bin/fp_part -r -f /dev/pmt | grep FAT; echo $?
Click to expand...
Click to collapse
__NODL_FAT,0x74F80000,0x33F3A0000,0x00000000
0
Donat.Callens said:
__NODL_FAT,0x74F80000,0x33F3A0000,0x00000000
0
Click to expand...
Click to collapse
Only the first part of the uprade has happend. The first part replaces the root file system, recovery and some other system partitions.
The second part of the upgrade is launched on the next boot in /system/etc/install-recovery.sh (itself copied from /system/bin/fp1_partition_upgrade ).
It checks if the partition upgrade has happened and if not perform the upgrade.
This step is not working on your phone/layout and to understand why you need to get the kernel messages (dmesg or logcat) while doing the upgrade.
/system/bin/fp1_partition_upgrade
Code:
#!/system/bin/sh
#
# Upgrade the partition layout from FP1 to FP1U
#
#
# dump pmt to see if the upgrade has happend
if /system/bin/fp_part -r -f /dev/pmt | grep FAT > /dev/null
then
echo Starting partition upgrade
cp /system/bin/fs_upgrade.bin /proc/sd_upgrade
echo "--wipe_data" > /cache/recovery/command
reboot recovery
fi
logcat
_keesj said:
This step is not working on your phone/layout and to understand why you need to get the kernel messages (dmesg or logcat) while doing the upgrade.
Click to expand...
Click to collapse
I restarted the partition updater and attach the corresponding logcat
$ logcat -v long
Donat.Callens said:
I restarted the partition updater and attach the corresponding logcat
$ logcat -v long
Click to expand...
Click to collapse
Can you please also provide the dmesg output, possibly using a private message? (the logcat does contains the info I am looking for an might contain private data)
custom recovery might be the source of the problem
_keesj said:
Donat.Callens said:
_keesj said:
The partition upgrdate is not happening, there should be lines containins SD_UPGRADE something like
Click to expand...
Click to collapse
could it be because I have a custom recovery installed?
Click to expand...
Click to collapse
This is an interesting idea.
-The sd_upgrade command is executed when not on the recovery so this is not probable.
-I think the recovery will also be replace back to "original" because we need a diifferent kernel.
Did you run the command and does the device reboot afterwards? A different recovery might not perform the factory reset?
Click to expand...
Click to collapse
I did not run the command, I merely started the FairPhone updater's partition upgrade tool. It displays a progress window like the first time, so I guess it is at least trying.
After the progress window, I get
ROM may flash stock recovery on boot. Fix?
Click to expand...
Click to collapse
I then reply
Yes - Disable recovery flash
Click to expand...
Click to collapse
I can try to let it install the stock recovery and run the partition updater after that to see if it solves the problem.
Donat.Callens said:
I did not run the command, I merely started the FairPhone updater's partition upgrade tool. It displays a progress window like the first time, so I guess it is at least trying.
After the progress window, I getI then replyI can try to let it install the stock recovery and run the partition updater after that to see if it solves the problem.
Click to expand...
Click to collapse
Post partition upgrade:
-The zip files downloaded have a different scattter file (a file describing the partition layout) that gets checked by the normal recovery.
-The zip are signed with a different key
This does not apply to the partition upgrader itself but might impact custom recovery users. The upgrader also replaces the recovery.
_keesj said:
Post partition upgrade:
-The zip files downloaded have a different scattter file (a file describing the partition layout) that gets checked by the normal recovery.
-The zip are signed with a different key
This does not apply to the partition upgrader itself but might impact custom recovery users. The upgrader also replaces the recovery.
Click to expand...
Click to collapse
I replied No to the question: ROM may flash stock recovery on boot. Fix?
This solved the issue. The installer completed and now my phone is back to factory default. I have 13.37 GB total space . I will restore my backups. Thank you for your support _keesj.
Please ensure user are informed they have to let the installer replace the existing custom recovery with the factory one for the partition upgrader to work correctly. You can always restore your custom recovery afterwards
I hereby confirm that, in my case, the partition upgrader worked with a modified partition scheme. For reference, I had changed the internal storage space to 4GB in the past.
Awesome guys!
This is why I like xda-developers and Fairphone and its community accompanied development so much. Not only I can follow the rapid conversations on problems and solutions that I could even run into, I also learn a lot about related techniques, background and the challenges in throwing a fair phone on the market.
I definitely appreciate the work of the xda developers, keejs and joemier - and of course all the others that stand behind that all. KUDOS!
But will all my apps still work, if I do backup the two partitions and then after the upgrade put everything on the one remaining partition? I guess quite a few apps might still "look" for their data on the no longer existing second partition, won't they?
Steps for "fiixing" your upgrade
Some user have repartitioned the partition of their FP1U using tool mentioned in on this forum. FP1U does not need this as the new layout is perfectly fine.
I think the following steps *should* work to get their phone back to "normal"
#get the partition upgrader
wget http://storage.googleapis.com/updat...G13G_partitionUpgrade_v1_6_OTA_2014-07-31.zip
#unzip it
unzip FP1_Fairphone_OS_1G13G_partitionUpgrade_v1_6_OTA_2014-07-31.zip
#attach your device to your pc and make sure adb works
#after that push the new partition layout to your device
adb push system/bin/fs_upgrade.bin /mnt/sdcard/
#the rest of the command need to run as root
adb shell
su.
# tell the kernel to perform the upgrade
cp /system/bin/fs_upgrade.bin /proc/sd_upgrade
#reboot and wipe the data
echo "--wipe_data" > /cache/recovery/command
reboot recovery
Related
Hello folks,
on my HTC Desire with OpenDesire 3.5.2 I'm trying to install the dropbear ssh-deamon according to a german tutorial (I'm not allowed to put the link here... ).
It is on www and then android-hilfe.de and then, go /root-hacking-modding-fuer-motorola-milestone/14241-per-ssh-auf-den-milestone.html
I'm connected to the phone using adb and shell'd into.
Now, they say that I have to mount /system as read-write to put a file (dropbear) into /system/bin. The command is
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
and results in no errors. mount then says:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
so in my opinion, /system shoult be writable.
But everything I try results in an "Out of memory" error: Creating directories, copying files - anything.
Only deleting files is possible: I backed-up and then deleted some ringtones from /system/media/audio/ringtones, and I'm also not able to copy the backup of them I did before onto the sdcard back into the directory again
I read in another thread, that the error "Out of memory" itself is a bug and should mean "No permission". But why don't I have permission?
df -h gives me
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 203.4M 0 203.4M 0% /dev
tmpfs 203.4M 0 203.4M 0% /mnt/asec
/dev/block/mtdblock3 250.0M 106.4M 143.6M 43% /system
/dev/block/mtdblock5 147.6M 53.9M 93.8M 36% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
/dev/block/vold/179:1
3.7G 2.9G 744.3M 80% /mnt/sdcard
/dev/block/vold/179:1
3.7G 2.9G 744.3M 80% /mnt/secure/asec
so there definitively IS enough memory for a 720kB file.
Any ideas?
You can only write to system on the desire via adb from recovery.
If above post didn't explain it enough...
There is no write access to /system partition yet, except via a overlay file system. Have a search and you'll find, like everybody else.
thank you! Yes, that is the problem. I read this also somewhere, but didn't remember it.
I still cant write files even though im in recovery?
zoltrix said:
I still cant write files even though im in recovery?
Click to expand...
Click to collapse
Type "adb remount"
(Without "")
zHk3R said:
Type "adb remount"
(Without "")
Click to expand...
Click to collapse
Im trying to relfash my recovery and i keep getting the no space issue.
If i type in adb remount, i can no longer mount my sd card that is holding my image..
http://forum.xda-developers.com/showthread.php?t=805141
EDIT: If i figure out how to s-off my phone, will that fix it?
zoltrix said:
Im trying to relfash my recovery and i keep getting the no space issue.
If i type in adb remount, i can no longer mount my sd card that is holding my image..
http://forum.xda-developers.com/showthread.php?t=805141
EDIT: If i figure out how to s-off my phone, will that fix it?
Click to expand...
Click to collapse
Just follow the thread in Desire Android Development and you'll have S-OFF easy.
PRO TIP: Use a flash drive rather than burning the .iso on a CD.
Yea but, will i need s-off to flash this recovery?
I know s-off lets you do stuff within fastboot, but im not too sure what taht really means
zoltrix said:
Yea but, will i need s-off to flash this recovery?
I know s-off lets you do stuff within fastboot, but im not too sure what taht really means
Click to expand...
Click to collapse
nevermind, ive done my research and s-off fixed my problem!
details
could you please describe in a little bit more details how you have managed to write the /system mount point ?
thanks in advance ...
btw, there are o bunch of guys that want this answer
What? and Why?
I too would like to know more about writing to /system.
adb remount appears to switch the mount point from "ro" to "rw" (as shown with mount command) but I still get the same "Read-only file system" response when I try to adb push files.
What exactly is the issue here? Is it related to S-ON / S-OFF ?
What do I have to do to be able to write to /system?
(other than reboot into recovery; when I copy files in Recovery, they are gone after a normal reboot)
Thanks
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Very good news! Hopefully something comes of this. I want to look at the code for TWRP 2.0 and see if that can be ported over to the fire, its touch control.
Sent from my Kindle Fire
you got partition table for fire yet ? i am looking for boot partition
cat /proc/mounts....
Code:
# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12 /mnt/sdcard 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 0 0
/dev/block/vold/179:12 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
cat /proc/partitions
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
#
cat /proc/filesystems
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
msdos
nodev nfs
nodev nfs4
#
ls /dev/block/platform/mmci-omap-hs.1/by-name
Code:
# ls /dev/block/platform/mmci-omap-hs.1/by-name
media
cache
userdata
system
splash
boot
backup
recovery
dfs
dkernel
bootloader
xloader
#
Probably doesn't help. But I guess it was worth a shot. I'm not sure what the partitions are mapped to. :/
using root explorer i can tell that
/dev/block/platform/mmci-omap-hs.1/by-name/boot
is symlinked to
/dev/block/platform/mmci-omap-hs.1/mmcblk0p7
so if you wanted to mount boot
you could type
mount -o rw,remount /boot
i believe..
well i did a dd if= from the phone to the sdcard, but now we can just grab the boot.img from the update on amazon's site
Can you post pictures? This is the main reason I am not trading my fire for a nook.
http://i.imgur.com/9zWTk.jpg just gettings rid of those error messages now. had the wrong filesystem for /cache
I love you.screw the nook.
Wow JackpotCalvin! How were you able to flash the clockwork recovery? Also are you still able to load your KF as normal?
really nice work
another way to mount things as is done in the init.rc:
mount [email protected]/system system
so for rw..."mount -o rw,remount -t ext4 [email protected] /system"
anyway mounts are as follows:
backup -> mmcblk0p6
boot -> mmcblk0p7
bootloader ->mmcblk0p2
cache -> mmcblk0p11
dfs -> mmcblk0p4
dkernel -> mmcblk0p3
media -> mmcblk0p12
recovery -> mmcblk0p5
splash -> mmcblk0p8
system -> mmcblk0p9
userdata -> mmcblk0p10
xloader -> mmcblk0p1
well we're at a bit of a road block as of right now as we have no way to navigate through the menu, we can just press OK and reboot the kindle. also, pressing reboot now does not start the device normally, it just reboots into clockwork. i'm looking for the flag that the OS puts in /cache or /data to trigger a recovery reboot because pressing reboot now does not remove that flag so it will continue to reboot into clockwork unless you do a little hackery to put the stock recovery back on it and then reboot it into the stock recovery and make it fail the signature verification this fluke update.zip i made. we need to find a way to make a fail safe to reboot into recovery as well in case when we start roming, something goes wrong
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
JackpotClavin said:
when we start roming,
Click to expand...
Click to collapse
Emphasis mine. I can't wait. Great work so far, this seems to be going a lot faster than I imagined at first. I wish I had the programming chops to become a dev, instead i just look on from the sidelines, and maybe monetarily support projects when and where I can.
Awesome work guys. I've got the Nook Tablet but thought I'd pop over to see how it's going. Again, awesome work.
Sent from my Nook Tablet using Tapatalk
littleemp said:
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
Click to expand...
Click to collapse
The official clockword mod does not support the fire yet... if that's what you're asking. That is what OP is trying to do.
JackpotClavin said:
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Click to expand...
Click to collapse
How did you boot into recovery?
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
JackpotClavin said:
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
Click to expand...
Click to collapse
Sounds like we may have to be connected to our PC to run the commands...??
Hello. I need help with backing up my /efs folder. I tried different methods and none seemed to work.
Phone: GT-S5660 Gio
Network Lock [OFF]
Network Subset Lock [OFF]
SP Lock [OFF]
CP Lock [OFF]
Android: 2.3.3
PDA : S5660XXKPO
PHONE : S5660XXKPA
CSC : S5660OXFKP5
Lurking the forums I tried different methods with no luck:
C:\sdk>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# tar zcvf /sdcard/efs-backup.tar.gz /efs
tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: not found
# exit
exit
$ exit
exit
=======================
C:\sdk>adb shell
$ su
su
# busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: /efs: No such file or directory
tar: error exit delayed from previous errors
# cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
/dev/block/stl3: Invalid argument
# exit
exit
$ exit
exit
This method creates efs_dev-block-stl3.img (0 bytes) and efs-backup.tar.gz (29 bytes)
=======================
EFS Pro
Checking Device Connection... Device Connected!
Restarting ADB Server... Okay!
Checking ROOT Access... Device Has ROOT Permissions!
Backing Up Device's '/efs' Folder, Please Wait...
Creating EFS Backup TAR Archive... EFS Backup Failed!
Operation Finished!
With the ISO option the program freezes.
=======================
C:\sdk>adb shell
$ su
su
# dd if=/dev/block/stl4 of=/sdcard/efs.rfs
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
/dev/block/stl4: cannot open for read: Invalid argument
# exit
exit
$ exit
exit
=======================
I also tried this:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.sportstracklive.stopwatch-1 vfat ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
=======================
With Root Explorer I am unable to find the /efs
Sorry for the long post, but what am I missing?
Best regards, V a L y O.
STOP!
The first rule with the Gio is not to mess with the EFS partition if you don't know what you're doing.
It is located in stl5, but you very much risk corrupting it solely by mounting and reading it.
Corruption in this case means a bricked phone or a blank IMEI, which means no phone service.
Either backup bml5, or work in recovery mode.
Thank you for the replay.
I know that messing with the stl5 can brick the phone. Well, that already happened once when I used Odin to flash a wrong 2.3.5 version. Lucky for me, It was repaired under warranty.
That's why I want to make a backup to the system files.
bml5 is backed up. Is it enough to fix the phone in case I brick it again?
Best regards, V a L y O.
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
phiexz said:
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
Click to expand...
Click to collapse
Same here! I live in the Netherlands and also have a blank IMEI(IMEI is 000000000000) but still evrything works except swype install because it requires an IMEI number. Somebody know how to fix it? maybe to use somebody elses IMEI? with /efs restore or is there an way to import my own IMEI in somebody elses /efs backup?
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S i9000 (galaxysmtd)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
XDA:DevDB Information
[i9000][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Samsung Galaxy S I9000
Contributors
Phil3759, tetakpatak
Version Information
Status: Stable
Created 2014-04-03
Last Updated 2014-04-03
A few features are missing because of the mtd stuff
If some one can provide the partitions linked to their mtd path, I will add them
cat /proc/mtd
Good job man , Good job
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Dude , you make our beloved phone alive with this nice recovery.
I will add it to my next Rom Update , it looks ... woah so nice!
Thanks for working now on i9000 device
The galaxysmtd version is an .img file , so , which kernel is it embedded into ?
ts1506 said:
The galaxysmtd version is an .img file , so , which kernel is it embedded into ?
Click to expand...
Click to collapse
I am trying to remove the img in new omni rom , i will report further.
kevinrus123 said:
I am trying to remove the img in new omni rom , i will report further.
Click to expand...
Click to collapse
cm-11.0
Oh my.. Thank you Phil! I've used your recovery on my note and i loved it! Thank you again
Sent from my GT-I9000 using XDA Premium 4 mobile app
Phil3759 said:
cm-11.0
Click to expand...
Click to collapse
Didnt really get it, you mean that its the CM11 kernel right , with Philz touch recovery. Cause recovery images cant be flashed on Galaxy S.
ts1506 said:
Didnt really get it, you mean that its the CM11 kernel right , with Philz touch recovery. Cause recovery images cant be flashed on Galaxy S.
Click to expand...
Click to collapse
Oh
I did not know that you need an update.zip like I was doing for the i9100 to start it from stock recovery
This is the recovery.img we get when building in cm
You'll have to unpack it, create the update.zip and sign it
I can provide the ramdisk if needed
Sorry
If you create an update.zip, add the missing mtd path for your partitions in extra.fstab
Also, if someone posts them here would be great so that I can merge them
( omni rom)
Sent from my GT-I9000 using XDA Premium 4 mobile app
Here the CM11 28/12 version.
Sent from my GT-I9000 using XDA Premium 4 mobile app
Phil3759 said:
Oh
I did not know that you need an update.zip like I was doing for the i9100 to start it from stock recovery
This is the recovery.img we get when building in cm
You'll have to unpack it, create the update.zip and sign it
I can provide the ramdisk if needed
Sorry
Click to expand...
Click to collapse
In galaxysmtd , the recovery is embedded within the kernel boot.img, there is no seperate recovery partition.
flashable zip attached
@Phil3759 thanx for your great work
the touch not work as it should
can you provide me the ramdisk
ts1506 said:
Didnt really get it, you mean that its the CM11 kernel right , with Philz touch recovery. Cause recovery images cant be flashed on Galaxy S.
Click to expand...
Click to collapse
imo this is a stock cm-11 kernel with philz cwm
not a standalone recovery
UPDATE:
I extracted the ramdisk-recovery.img and compile it with my own kernel
the recovery works, UI was nice but touch not work properly
only volume (navigate up-down) and power (to choose) button works normally
home button not working either
no problem with install kernel, so can easily switch to other kernel savely
hope all feature can works in future
thanks for your great works :good:
mohammad.afaneh said:
flashable zip attached
@Phil3759 thanx for your great work
the touch not work as it should
can you provide me the ramdisk
Click to expand...
Click to collapse
Does touch work if you use the cm-11 kernel provided?, that is flash it all as a boot.img, boot into recovery to test and then restore your stock boot.img
Phil3759 said:
Does touch work if you use the cm-11 kernel provided?, that is flash it all as a boot.img, boot into recovery to test and then restore your stock boot.img
Click to expand...
Click to collapse
One touch work and press any hardware key to perform another touch
Some weeks ago tryed to port the recovery from 9001 and touch was OK but mount point not.
---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------
Phil3759 said:
A few features are missing because of the mtd stuff
If some one can provide the partitions linked to their mtd path, I will add them
cat /proc/mtd
Click to expand...
Click to collapse
dev: size erasesize name
mtd0: 00780000 00040000 "boot"
mtd1: 00780000 00040000 "recovery"
mtd2: 1a600000 00040000 "datadata"
mtd3: 01180000 00040000 "cache"
mtd4: 00c80000 00040000 "efs"
mtd5: 01000000 00040000 "radio"
mtd6: 00b00000 00040000 "reservoir
mohammad.afaneh said:
One touch work and press any hardware key to perform another touch
Some weeks ago tryed to port the recovery from 9001 and touch was OK but mount point not.
---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------
dev: size erasesize name
mtd0: 00780000 00040000 "boot"
mtd1: 00780000 00040000 "recovery"
mtd2: 1a600000 00040000 "datadata"
mtd3: 01180000 00040000 "cache"
mtd4: 00c80000 00040000 "efs"
mtd5: 01000000 00040000 "radio"
mtd6: 00b00000 00040000 "reservoir
Click to expand...
Click to collapse
Thanks :good:
Here's how your extra.fstab should be:
Code:
/dev/block/mtdblock0 /boot mtd defaults defaults
/dev/block/mtdblock1 /recovery mtd defaults defaults
/dev/block/mtdblock2 /datadata yaffs2 defaults defaults
/dev/block/mtdblock3 /cache yaffs2 defaults defaults
#/dev/block/mtdblock4 /efs mtd defaults defaults
/dev/block/mtdblock5 /radio mtd defaults defaults
/dev/block/mmcblk0p1 /storage/sdcard0 auto defaults defaults
/dev/block/mmcblk1p1 /storage/sdcard1 auto defaults defaults
Only /efs I do not know if it is yaffs2 or mtd or ext4
Phil3759 said:
........
Only /efs I do not know if it is yaffs2 or mtd or ext4
Click to expand...
Click to collapse
yaffs2
rootfs / rootfs ro,relatime 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
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,seclabel,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,seclabel,relatime 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,seclabel,relatime 0 0
/dev/lvpool/system /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,seclabel,relatime 0 0
/dev/block/mtdblock2 /data/data yaffs2 rw,seclabel,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:1 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
Phil3759 said:
Thanks :good:
Here's how your extra.fstab should be:
Code:
/dev/block/mtdblock0 /boot mtd defaults defaults
/dev/block/mtdblock1 /recovery mtd defaults defaults
/dev/block/mtdblock2 /datadata yaffs2 defaults defaults
/dev/block/mtdblock3 /cache yaffs2 defaults defaults
#/dev/block/mtdblock4 /efs mtd defaults defaults
/dev/block/mtdblock5 /radio mtd defaults defaults
/dev/block/mmcblk0p1 /storage/sdcard0 auto defaults defaults
/dev/block/mmcblk1p1 /storage/sdcard1 auto defaults defaults
Only /efs I do not know if it is yaffs2 or mtd or ext4
Click to expand...
Click to collapse
Thanks will test it tomorrow
I have a Poco F3 Global, and I currently am running TWRP 3.5.2_11-Nebrassy.
If I tap Reboot and it shows my Current Slot as A, then under Mount I see the following:
System, system_ext, Product, Vendor, ODM, Metadata, Data, Cust, and Firmware
And I can check each of them. I can also perform Wipe -> Format Data -> yes.
But if I boot into Slot B, and tap Mount it doesn't let me click the checkmarks for System, system_ext, Product, or Vendor.
And if I try to execute Wipe -> Format Data -> yes it shows "Failed to mount" in red for all of the following:
'/system_root', '/system_ext', '/product', '/vendor' (Invalid argument)
(Some of them are in there multiple times)
Running cat /etc/fstab in B outputs:
Code:
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda35 /data f2fs rw 0 0
/dev/block/sda29 /cust ext4 rw 0 0
/dev/block/bootdevice/by-name/modem_b /firmware vfat rw 0 0
/dev/block/sda22 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
Running cat /etc/fstab in A outputs:
Code:
/dev/block/dm-2 /system_root ext4 ro 0 0
/dev/block/dm-3 /system_ext ext4 ro 0 0
/dev/block/dm-1 /product ext4 ro 0 0
/dev/block/dm-4 /vendor ext4 ro 0 0
/dev/block/dm-0 /odm ext4 ro 0 0
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda35 /data f2fs rw 0 0
/dev/block/sda29 /cust ext4 rw 0 0
/firmware vfat rw 0 0
/dev/block/sda22 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
For both A and B going to Wipe -> Advanced Wipe it only shows Dalvik / ART Cache, Metadata, Data, Internal Storage, and USB-OTG
I can still install an OS, but that is finicky at times.
How can I fix my B Partition?
Solved it:
Download the MiFlash Tool, and the Fastboot version of the Stock ROM. Extract the contents of the zip (and within the zip the tar file) to a directory without spaces in it (I just extracted it directly to C: drive). Open MiFlash, click Select and choose the directory you just extracted. At the bottom of the MiFlash app select "Clean All", NOT "Clean all and Lock" (unless that's what you want). Click Refresh (if phone doesn't appear, make sure your phone is in fastboot mode and connected to PC). Then click Flash. Mine failed the first time with some error about "Antirollback check error". If you get this you have to manually edit the "flash_all.bat" file within the extracted directory and remove the lines that don't start with "fastboot", then save the bat file, and restart the flash. It took MiFlash 604 seconds to complete, and ended with a status of "error: Not catch checkpoint, ..., flash is not done" you can ignore that, or remove that checkpoint in the MiFlash configuration settings. My phone restarted and booted into the stock ROM.
following had the same errors when i mistakenly ignorantly wiped system etc while trying to flash a rom