I'm trying to dump the boot.img in the hopes of porting CWM and, eventually, CM11 to the Lenovo B8080, better known as the Lenovo Yoga 10 HD+. But I'm at a loss how to extract the boot.img.
I've been following this guide here: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device and am stuck at trying to extract my boot.img as the binary is missing. All I get is
Code:
$ dump_image boot /storage/sdcard1/boot.img
dump_image: not found
I've also tried using romdump but the binary that I found won't run on the b8080, wrong architecture.
Lastly, I tried
Code:
$ cat /proc/mtd
as recommended in this guide: http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
but that also doesn't work as there is no "/proc/mtd".
What I do have is the following output:
Code:
$ cat /proc/partitions
major minor #blocks name
7 0 17703 loop0
179 0 15267840 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 32 mmcblk0p5
179 6 768 mmcblk0p6
179 7 768 mmcblk0p7
179 8 500 mmcblk0p8
179 9 500 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 500 mmcblk0p11
179 12 500 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 10240 mmcblk0p16
179 17 1572864 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 131072 mmcblk0p19
179 20 204800 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 1536 mmcblk0p23
179 24 1 mmcblk0p24
179 25 8 mmcblk0p25
179 26 12646383 mmcblk0p26
179 32 4096 mmcblk0rpmb
254 0 17703 dm-0
179 64 31166976 mmcblk1
179 65 31162880 mmcblk1p1
and
Code:
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=962644k,nr_inodes=182058,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
/dev/faccc /fac ext4 rw,seclabel,nodev,noatime,nodiratime,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=755,gid=1000 0 0
tmpfs /mnt/asec2 tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=962644k,nr_inodes=182058,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/lesw /lesw ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated 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/block/dm-0 /mnt/asec/[0]com.sketchbook-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:65 /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/block/vold/179:65 /mnt/secure/asec2 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
Does anybody know how to proceed from here? Thanks!
In case anybody else is wondering, I found this wonderfully useful post that solves this problem:
http://forum.xda-developers.com/showpost.php?p=45564277&postcount=4
In case anybody is interested, here's the repository I'm working on:
https://github.com/zyrill/android_device_LENOVO_B8080
I am extremely interested! Nice work
Anny update ?
Related
This is my portion layout:
$ su
# 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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,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=1000,gid=1015,fmask=0002,dmask=0002,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
and
$ su
# cat /proc/partitions
major minor #blocks name
137 0 513024 bml0/c
137 1 1536 bml1
137 2 768 bml2
137 3 768 bml3
137 4 17920 bml4
137 5 12800 bml5
137 6 768 bml6
137 7 6144 bml7
137 8 2048 bml8
137 9 10240 bml9
137 10 10240 bml10
137 11 768 bml11
137 12 173568 bml12
137 13 173056 bml13
137 14 102400 bml14
179 0 1955840 mmcblk0
179 1 1955775 mmcblk0p1
138 12 166912 stl12
138 13 166400 stl13
138 14 97280 stl14
#
I am trying to put system and boot.img!
I tried dd if=/dev/block/stl12 of=/sdcard/system.img and it shows a pound at the end I check my sdcard and there is nothing there? Is there something I'm doing wrong?
Does anyone know where I can find the CWM Recovery for the viper?
Sent from my LG-P999 using XDA
Bump
Sent from my LG-P999 using XDA
You can install the recoveries for the vs840 or the ms840 (lucid and connect respectively) through ROM Manager since all the sprint reps say they have the same coding but so far I haven't been able to do much other than boot into CWM. I can't make backups as it won't mount /system and when I manually mount /system for it it seems to backup but then the files just disappear :/ By the way you wouldn't happen to know the partition # of the recovery partition would you? I have a vague table laid out but it may not be 100% accurate so that info would help, or just let me know how to get into the bootloader/fastboot if you know how.
P.S. here's the table I've gotten so far with the file layouts (not 100% sure what files correspond to each partition)
Code:
/dev/block/mmcblk0p1 >IMAGE/MODEM*
/dev/block/mmcblk0p12 >Gaspra,LostFound,WCN1314_qcom_wlan_nv.bin,qcom
/dev/block/mmcblk0p14 >image/*.MBN
/dev/block/mmcblk0p22 >lost+found/,lpass/,mdm/,modem/
/dev/block/mmcblk0p23 >lost+found/
/dev/block/mmcblk0p27 >app/,bin/,build.prop,etc/,fonts/,framework/,lib/,media/,recovery/,sounds/,tts/,usbautorun.iso,usr/,xbin/ (/ ?)
/dev/block/mmcblk0p28 >lost+found/,recovery/
/dev/block/mmcblk0p29 >amit/,anr/,app/,app-private/,backup/,dalvik-cache/,data/,dontpanic/,fonta/,gesture/,img/,lgdrm/,local/,logger/,lost+found/,misc/,property/,qcks/,radio/,secure/,shared/,sutest/,system/,time/,tombstones/,wiper/,wmdrm/,wpstiles/ (/SYSTEM)
/dev/block/mmcblk0p30 >lost+found/
/dev/block/mmcblk0p31 >MPT_*,aat_result.txt,acc_calibration.dat,enable/,lost+found/,pid/,started/
Rom Development?
My wife just upgraded her EVO for this phone. I was able to find the rooting method with the superoneclick, and it worked slick. I was able to remove the sprint apps like NBA and NASCAR... but was looking for any custom rom. I had ICS running on her EVO, and since this comes with GB... I hate to go backwards. Is there anyone working on rom development for this phone yet?
some get me a dump of the stock recovey please
Also do
Code:
adb shell
Code:
cat proc/mounts
and
Code:
cat proc/partitions
Sounds like the viper has a different mount for system than its cousins.
In terminal emulator:
df to get list of partitions, if possible, and mount each on a temporary directory with loop options.. Hopefully the stock kernel supports fs wraps..
Just barely got this phone for my fiance, and I'm waiting for someone to nail this sucker to the wall.. Hopefully someone can come up with a working recovery..
Hope the above helps, because if you can df on su, especially with the -a option, if I remember right, it tells you the file systems used on each part.
Maybe once stuff settles down (because hectic is an understatement at this particular point irl, lol), I can jump in and be of more help, but right now.. It's just not the best time as I'm trying to keep a roof over our heads here..
Good luck all!
-----
Sent from my phone
using my finger... ;-)
-----
this needs testing and I still need the above mentions.
http://d-h.st/GFZ
# df -a
Filesystem Size Used Free Blksize
-a: No such file or directory
# df
Filesystem Size Used Free Blksize
/dev 400M 48K 399M 4096
/mnt/asec 400M 0K 400M 4096
/mnt/obb 400M 0K 400M 4096
# df
Filesystem Size Used Free Blksize
/dev 400M 48K 399M 4096 /mnt/asec 400M 0K 400M 4096
/mnt/obb 400M 0K 400M 4096
/mnt/extasec 400M 0K 400M 4096
/mnt/extobb 400M 0K 400M 4096 /system 1009M 348M 661M 4096
/tombstones 71M 4M 67M 4096 /firmware 1G 28M 1G 32768
/data 1G 579M 1G 4096 /persist 7M 4M 3M 4096
/cache 314M 5M 309M 4096 /LGE_RC 4M 24K 4M 4096
/mpt 15M 9M 6M 1024 /system/etc/firmware/misc_mdm 199M 22M 177M 4096 /mnt/sdcard 14G 4G 9G 32768
/mnt/secure/asec 14G 4G 9G 32768 /mnt/asec/com.droidemu.game.lite-1 12M 10M 1M 4096 /mnt/asec/com.diotasoft.spark-1 28M 26M 1M 4096
/mnt/asec/com.nelphy.android.heavenhell-1 32M 30M 1M 4096
/mnt/asec/com.mojang.minecraftpe.demo-1 8M 6M 1M 4096
#
Here are the proc/ results
Code:
# cat proc/mounts
rootfs / rootfs rw,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
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p27 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,noatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /LGE_RC ext4 rw,nosuid,nodev,relatime,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,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
/dev/block/dm-0 /mnt/asec/com.droidemu.game.lite-2 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.mojang.minecraftpe.demo-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-2 /mnt/asec/com.nelphy.android.heavenhell-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-3 /mnt/asec/com.diotasoft.spark-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-4 /mnt/asec/com.nelphy.android.crazyshuttle-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
# cat proc/partitions
major minor #blocks name
7 0 12506 loop0
7 1 8348 loop1
7 2 33296 loop2
7 3 29138 loop3
7 4 28098 loop4
179 0 3780608 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1048576 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 1843200 mmcblk0p29
179 30 5120 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 5120 mmcblk0p32
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
254 0 12505 dm-0
254 1 8347 dm-1
254 2 33295 dm-2
254 3 29137 dm-3
254 4 28098 dcode
?
sooo did you guys manage to find a cwm recovery?
im a total noob and i managed to root this phone but now i cant find a recovery :/ im still in GB
i got the cat /proc/mounts here -
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/nandi /oem cramfs ro,relatime 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/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal
_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journa
l_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=
ascii,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=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/extsd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.gameinsight.mycountry-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocha
rset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.vividgames.speedwaygp2012-1 vfat ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,i
ocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
can any one tell me from this which is the boot and recovery partition?
anyone please???
michael.the.don said:
i got the cat /proc/mounts here -
can any one tell me from this which is the boot and recovery partition?
Click to expand...
Click to collapse
/proc/mounts only shows currently mounted partitions, and not boot neither recovery are ever mounted. Instead check either /proc/mtd (for NAND) or in the partition table (for MMC, use fdisk).
If NAND, there's no guarantee the boot loader exposes those partitions to the kernel at all, though.
i tried using /proc/mtd but it says file missing.
how to use fdisk?
i tried using /proc/partitions
it gives me-
[email protected]:/ # cat /partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 5992448 nandj
179 0 15674368 mmcblk0
179 1 15670272 mmcblk0p1
michael.the.don said:
i tried using /proc/mtd but it says file missing.
how to use fdisk?
i tried using /proc/partitions
it gives me-
[email protected]:/ # cat /partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 5992448 nandj
179 0 15674368 mmcblk0
179 1 15670272 mmcblk0p1
Click to expand...
Click to collapse
Good enough, now you can start mapping all your partitions. Compare this to the mount list, and mark e.g. nande as data, etc. After a while you'll get a few unknown left, potential candidates for boot and recovery you can examine more carefully.
thanks very much.
michael.the.don said:
thanks very much.
Click to expand...
Click to collapse
I'd guess nandc and nandg, they seems about the right size and not mounted. dd them to a file and examine them if they've got the format mkbootimg produces. Those files should begin with "ANDROID!".
# dd if=/dev/block/nandg of=/sdcard/isthisboot.img
Hello,
I have a SM-P600 (32G) with failed factory reset that left the device soft-bricked so that booting to Download and recovery works, but OS-booting leaves the device freezed after boot animations (With stock-ROM). Flashing new recovery programs work and below results are from ABD Shell with CWM recovery flashed to the device.
Below are results from /proc/mounts, /partitions and /devices. It seems that NAND block device or its partitions are not listed in results.
I was wondering what can be the reasons for this behavior, and what can be done in order to get the NAND device back online?
Is there a way to manually re-initialize the device? Or some debugging tips to narrow down the problem?
Your help will be much appreciated if I manage to get this brick back alive without buying a new system board for it.
ADB cat /proc/mounts
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,discard,journal_checksum,j
ournal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,relatime,discard,journal_checksum,
journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
~ #
ADB cat /proc/partitions
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 20480 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 2465792 mmcblk0p20
259 13 27709440 mmcblk0p21
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 30948352 mmcblk1
179 33 30944256 mmcblk1p1
~ #
ADB cat /proc/devices
Block devices:
1 ramdisk
259 blkext
7 loop
8 sd
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
254 device-mapper
~ #
Hi there,
I am posting this post after long hard working on my own to cook a new rom and recovery for my phone. I have faced alot of problems that I have passed by the help of self digging and searching here and there. But finally I'm now stuck with these very stupid problems that made me completely down, which start with poor internet connection speed, and end with those foolish electricity cutting off periods, that make it very difficult to download all of required sources to establish a development experience. Additionally I cann't establish a VPS due to previous elec. reason and some financial points as well.
So now I'm asking any one who can help me cooking a new one so that I can download and test. And I really appreciate any help because I'm really willing to have one.
My phone is a chinese one made by UNISCOPE brand and it has ((a lot of chinese roms and recoveries)) but they are not recommended to me now as they are not updated and dont have arabic interface.
The phone specifications are as follow:
Manufacturer : Uniscope
Model : U1203
CPU : Qualcomm MSM8625 1.152 GHz x2
RAM : 512+256 MB DDR (Usable: 591 MB)
GPU : Adreno (TM) 203 (single core GPU) by Qualcomm
Display size : 540×960 (X/Y dpi 159 / 160 ; Pixel Density: 240 dpi)
Network : Dual SIM (CDMA/ GSM)
Camera : Back 8 MP and front 2 MP
Full specs and other Information about this phone will be found at its formal web page on this link : http://en.uniscope.com/show.php?contentid=21
Alternative links:
if the Official website are not loading which is the case now from my location at least here are the alter natives:
- Full specs at : http://www.mobile-phones.cn/uniscope-u1203-dual-core-msm8625-768mb-inch-smart-phone-p-13703.html
= Official firmwares:
- Ice cream sandwich 4.0.4 at : http://www.romzj.com/rom/6180.htm
- Jily beans 4.1.2 at : http://pan.baidu.com/share/link?shareid=423245&uk=2871557411
- Custom ROMs and recoveries at : http://bbs.zhiyoo.com/forum-820-1.html
Note: Official firmwares are of two different file system tables(partitions) which are ics 4.0.4 one and jb 4.1.2. so that I will concentrate on jb 4.1.2 version resources here; to continue building according to them specially the file system partitioning.
Here are some essential requirements:
1- A copy of /system/build.prop file : http://www.mediafire.com/download/occiy4b84c2yu4f/build.prop.7z
2- The file system table of the phone:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p16
/system ext4 /dev/block/mmcblk0p17
/data ext4 /dev/block/mmcblk0p21
/persist ext4 /dev/block/mmcblk0p15
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p13
/FOTA emmc /dev/block/mmcblk0p19
/splash emmc /dev/block/mmcblk0p22
/emmc vfat /dev/block/mmcblk0p20
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
3- The result of "cat proc/partitions":
Code:
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 250 mmcblk0p2
179 3 51200 mmcblk0p3
179 4 1 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 768 mmcblk0p12
179 13 13576 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 13576 mmcblk0p16
179 17 460800 mmcblk0p17
179 18 102400 mmcblk0p18
179 19 24576 mmcblk0p19
179 20 1048576 mmcblk0p20
179 21 1983508 mmcblk0p21
179 22 3072 mmcblk0p22
179 23 62171 mmcblk0p23
179 32 15454208 mmcblk1
179 33 14359552 mmcblk1p1
179 34 1085440 mmcblk1p2
4- The result of "mount" :
Code:
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
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
debugfs /mnt/debugfs debugfs rw,relatime,gid=512 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.3/by-num/p17 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p21 /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p18 /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p15 /persist ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:20 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
/dev/block/vold/179:33 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
5- A copy of its stock recovery.img: http://www.mediafire.com/download/k5xr0dkn1zpe3dc/recovery.img.7z
6- A copy of its stock boot.img: http://www.mediafire.com/download/c26vipdqmdruqvq/boot.img.7z
7- A copy of device/uniscope/u1203 folder that I worked hard to produce (building it from scratch) is on this link: http://www.mediafire.com/download/qgejhh6q1cbfv1r/device-uniscope-u1203.7z
Note: I built these device files according to different resources. firstly the original source has been taken from Codeaurora project. then has been modulated according to the building rules of CyanogenMod.
The list of required blobs has been created by help of other MSM8625 phones lists and by help of two pieces of software that I developed; and finally the list is now up. but I hope its really full and enough to establish an appropriate and fine booting; and this will depend on the future testing I guess.
8- A copy of device/qcom folder that is needed by device/uniscope/u1203 because of some includes is on this link : http://www.mediafire.com/download/bcnxkn85iuawsvc/device-qcom.7z
Note: I think with developing a new rom you may find some includes, from this part of "make files", that are missed which may be found in the source of Codeaurora project in the links below. Another small note here, which is when I run "adb devices" in the terminal my device appear with msm8625qdr5. and this my give a hint to help selecting the appropriate source from list in the QDR-Android Codeaurora project.
9- A copy of vendor/uniscope/u1203 folder that I prepared and extracted according to the scripts in the uniscope device folder is on this link : http://www.mediafire.com/download/v3bsa1den7az81v/vendor-uniscope-u1203.7z
10- And here's a copy of all phone's /system/bin folder contents if needed : http://www.mediafire.com/download/vfl48va4qam5lcp/system-bin.7z
Android Sources related to my phone:
1- The most correctly expected as source of my phone android present in this Codeaurora project :
https://www.codeaurora.org/xwiki/bin/QRD-Android/
2- The source of general android project of codeaurora:
https://www.codeaurora.org/xwiki/bin/QAEP/
3- The list of active projects of Codeaurora:
https://www.codeaurora.org/projects/all
Thank you in advance