xHausx just emailed me this test recovery for the nexus s 4g only. it's a port of the famous amon recovery that the evo uses. i thought id share it with you guys, remember this is a test recovery. he said if it works he will make an official thread here. unzip and push it via adb as you would with clockwork.
NS4G users only, i am not responsible if you brick your phone.
enjoy!
EDIT: it flashes but is not fully functional yet. you can flash clockwork back over this with no issues.
As of now we need an experienced dev to complete this project.
I'm getting "can't open /tmp/recovery.log"
Uncle Jimmy says hello
yeah but at least we know it does flash it successfully. it also mounts the usb in recovery. i made this thread to debug for the dev. this is a step in the right direction at least. also reboot and power off works but cannot seem to read the internal storage to flash anything.
lets use this thread to debug and see what we can do to help the dev.
fixxxer2008 said:
yeah but at least we know it does flash it successfully. it also mounts the usb in recovery. i made this thread to debug for the dev. this is a step in the right direction at least. also reboot and power off works but cannot seem to read the internal storage to flash anything.
lets use this thread to debug and see what we can do to help the dev.
Click to expand...
Click to collapse
Have you reported to xhausx yet? It was nice to see amon on my phone again.
Uncle Jimmy says hello
snandlal said:
Have you reported to xhausx yet? It was nice to see amon on my phone again.
Uncle Jimmy says hello
Click to expand...
Click to collapse
yes i did and i linked him to this thread. i think were on the road to having amon on the nexus s 4g.
what i am wondering is, if we get this to work will we have to sign our zips differently now? clockwork needs edify and i believe amon does not.
also in theory we should be able to make a ext partition and convert it to ext2 for dark temor a2sd. id love to be able to move the dalvik at least as clockwork doesn't support this.
I love RA! I can't wait till its functional
Evo 4G --> Nexus S 4G
Amon's will flash either so that's even better
Uncle Jimmy says hello
i remember having amon on my heroc ages ago, i dont remember but dont the zips have to be signed for that one?
hopefully the dev will update this today. id love to run amon on my nexus.
Nice nice, hope it gets ported to the GSM Nexus S too. Shouldn't be too hard though.
Nice! I've been PM'n devs about this too with no luck...hell, I even tried to port it myself but it's beyond my capabilities. Glad someone is finally on this.
We have to invest in xhausx. Well worth the $
Uncle Jimmy says hello
pm him guys and show your interest. i haven't heard from him today yet. also another dev is welcome to take this on too.
Flashed fine with fastboot and boots into it fine but I also get that recovery log error. Would love to see this working for us, thanx for the work done so far...
Sent from my Nexus S 4G using XDA Premium App
can someone connect with adb and try a few things for me?
Code:
cat /proc/mtd
mount
mount -a
mount
That will give me an idea of what partitions, if any, it is mounting.
xHausx said:
can someone connect with adb and try a few things for me?
Code:
cat /proc/mtd
mount
mount -a
mount
That will give me an idea of what partitions, if any, it is mounting.
Click to expand...
Click to collapse
ill try this later and post here. i have to leave for work soon.
xHausx said:
can someone connect with adb and try a few things for me?
Code:
cat /proc/mtd
mount
mount -a
mount
That will give me an idea of what partitions, if any, it is mounting.
Click to expand...
Click to collapse
here ya go:
Code:
cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00040000 "bootloader"
mtd1: 00140000 00040000 "misc"
mtd2: 00800000 00040000 "boot"
mtd3: 00800000 00040000 "recove
mtd4: 1d580000 00040000 "cache"
mtd5: 00d80000 00040000 "radio"
mtd6: 006c0000 00040000 "efs"
Code:
mount
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)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock6 on /efs type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/platform/s3c-sdhci.0/by-name/system on /system type ext4 (ro,relatim
,barrier=1,data=ordered)
/dev/block/platform/s3c-sdhci.0/by-name/userdata on /data type ext4 (rw,nosuid,
odev,noatime,barrier=1,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:3 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
elatime,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:3 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
xec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
Code:
mount -a
mount: can't read /etc/fstab: No such file or directory
hope it helps
Seeing this getting implemented on the ns4g makes me want to switch from the evo that much more!
it booted up on nexus_s gsm version. I did a fastboot boot RA-v2.3-crespo4g-test2.img.
usb mount didn't really work for me.. it mounted something, and windows prompted me if i wanted to format. so i rebooted.. my sdcard and all it's files are still there
hopefully we get a fully working port soon. i hope you all will donate to him as well.
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
I just downloaded this after finding it online. it says im missing the runtime. how do i fix this
Make sure you use the most recent version which can be found in the Android dev section on these forums.
DirkGently1 said:
Make sure you use the most recent version which can be found in the Android dev section on these forums.
Click to expand...
Click to collapse
I was on the SuperOneClick Android dev. page but it would not allow me to post as I am a horrible underling and have no privileges.
So if anyone can post it there or answer it here then this is the failure error I get for the device (A coby Kyros MID8024)
I have everything set up and the tablet is running android 2.2 all drivers and other files needed are installed.
Installed terminal emulator confirms NO SU allowed.
Getting mount path...
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,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)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p3 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/vold/179:1 on /mnt/nand type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 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=utf8,shortname=
FAILED
Thanks if anyone can assist.
I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.
Vernox701 said:
I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.
Click to expand...
Click to collapse
Why not just flash google apps? That should install the market or you could download the apk for the market directly. See this thread: http://forum.xda-developers.com/showthread.php?t=1231290 .
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
So last night i finally decided to install JetiX20. Installation ran smoothly until reboot.
hmm ... stuck on Samsung galaxy note 2 logo for over 45 mins.
Reboot into clockworkMod recovery v6.0.4.3
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
So.. i tried to wipe data/factory reset and cache partition....
Code:
--wiping data--
formatting /data...
error mounting /data!
skipping format...
formatting /cache...
E: format_volume:make_extf4fs failed on /dev/block/mmcblk0p12
formatting /sd-ext...
formatting /sdcard/.android_secure...
E: unknown volume "/sdcard/.android_secure"
data wipe complete
So, now i move to adb:
[email protected]:~$ adb devices
List of devices attached
42f7410e7bc79f3f recovery
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 67.1 GB, 67108864000 bytes
4 heads, 16 sectors/track, 2048000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 2048000 65535992 83 Linux
~ #
Code:
# 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 /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
Some how i manage to corrupt my mobile's partition?
I tried Odin, Heimdall, fastboot and adb as per recommended on the forum.
Is there anything else i could try?
Thanks for any advices.
You should re-flash the stock ROM of Samsung Galaxy Note 2 through ODIN.
I did, still getting the very same error.
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
gregsarg said:
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
Click to expand...
Click to collapse
I sure will read up on it. thanks
http://forum.xda-developers.com/showthread.php?t=2609871
There they are...
Again....I cannot stress enough the importance of reading every word Zen posted on the subject...
And remember....the PIT may not be your issue....so evaluate carefully...
I bid you good luck....g
Hello again
So sadly I'm still having the same issue, looks like everything install/runs ok but at reboot the phone still at bootloop when I try to pull the logs from the device all I get is can't mount mmcblk0p12.
Are you getting a "cannot mount sd card " in that error message ??
That error would indicate a failed partition on the emmc..
This is not looking good.....g
No just can't mount/open /cache/recovery.
But on wipe data/factory reset one of the lines say "E: unknown volume "/sdcard/.android_secure".
I can't find anything else that will give me that error.
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
gregsarg said:
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
Click to expand...
Click to collapse
Hi greg, this is the link http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189 and i am pretty sure NE5.
at first i though it was the actual external sd card, but then after some more careful reading, mmcblk0p12 is a partition of my internal storage correct?
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
gregsarg said:
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
Click to expand...
Click to collapse
Well thats a shame is there another way to verify the status of the emmc or this is pretty much it?is just strange how i try to install the JediX20 rom before and installed ok still boot, i would figure it will give errors installing and hang.
Oh well... ill try a few more times before i decide to move onto hardware
thanks greg.
Hello again everyone
So doing some more reading last night about my issue and found this:
****@****:~$ adb shell cat /sys/block/mmcblk0/device/manfid
0x000000
Will this confirm the issue to be with the chip?
thanks. \m/
One last attempt here...
Format your external SD CARD to FAT32 on a PC....then reload it into the device and reflash your rom....g
Omg Greg I was just about to do that lmao. Thanks working on it
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Chamo709 said:
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
Click to expand...
Click to collapse
Because your device is trying to mount the storage block....and the mmcblk0 is the address...
I'm hoping it's an external error and not internal...because the emmc will give similar errors....g
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Chamo709 said:
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Click to expand...
Click to collapse
Wipe data....factory reset in recovery...g
Ok... So no bueno still getting the same exact error ... What a shame really. I guess next step is getting a new board?
My mom has a Kindle 2nd Generation running 10.5.1 stock.
The other day, it started rebooting, but not in the traditional bootloop sense. The OS would load to the lock screen, you could swipe and use it (albeit sluggishly) for approximately 30 seconds before it rebooted again. So, it made it impossible to access the device via ADB.
I made a factory cable, accessed fastboot, and did the following:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
(if using a fastboot USB cable, swap to a normal USB cable before entering the next command)
fastboot -i 0x1949 oem recovery
Click to expand...
Click to collapse
This worked fine. I was able to get into recovery mode with TWRP and access ADB. I pulled all the data off the /sdcard partition. This was a big concern since my mom has been using this thing for a couple years now and she's collected quite a bit. Originally, my directive was to factory reset and reflash the stock firmware from Amazon: update-kindle-10.5.1_user_5174820.bin. It would be nice if they supplied a checksum, but they don't apparently.
Anyway, the more I thought about it, I thought I could clear some caches, uninstall some apks and that would resolve the issue without a new system image. Then I started to notice the problem:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 336.6M 136.0K 336.5M 0% /dev
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /data
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /sdcard
/dev/block/mmcblk0p12
639.8M 11.0M 628.8M 2% /cache
~ # 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)
/dev/block/mmcblk0p13 on /data type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p13 on /sdcard type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
~ #
Click to expand...
Click to collapse
Both /data and /sdcard are read-only. They also use the same block device. Maybe that's normal? I've already tried remounting the partitions read-write to no avail.
mount -o rw,remount /sdcard
mount -o rw,remount /data
Click to expand...
Click to collapse
Both commands execute as if they were accepted successfully (ala no output). However, rechecking mount's output, shows no change. It's still read-only.
I've tried sideloading in TWRP, but that resulted in a protocol fault. Also through TWRP, the factory reset succeeds, but actually does nothing. All of the data is still there. My other idea is to push the image onto the /cache partition (there's just enough room), and try to install that way, but I have a feeling that 1) won't work and 2) may exacerbate problems.
I'm stuck. Anyone have any ideas?
Solved
I was able to free the partitions.
fastboot -i 0x1949 erase userdata
Click to expand...
Click to collapse
It must have been some sort of corruption in userspace. I had previously tried a wipe through TWRP which was claimed to be successful. I still can't determine if TWRP doesn't check all their syscalls and handle the return codes or the Linux subsystem in Android is the root of the bugs. Either way, upon reboot, the device returned to factory "out of box" state.