Database Info

[Q] HTC Sensation, Flashing offical ROM, branded, SIMunlock, rooted

Hi I know im new to this forum, but I am technically knowledgeable, however I have a question, I bought a HTC Sensation, that was branded and locked to three UK network..
After thinking about this, is it not the case that network locks are applied by the network operator when they brand the device, if so, whats to stop me from flashing a Europe version, which I assume would get rid of all that, since it would then function as if it was not from any specific carrier right ?
My Sensation has been, s-off, permanently rooted, and super CID, with complete success, and i have done a backup with clockwork..
I mean the whole point to doing all this is so you are able to modify and have complete access to the set, i have seen people manually hex edit a specific file to make the phone unlocked on all networks, but that was for a different HTC model..
Any advice would be welcome.. !

List of defualt mounts HTC Sensation
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
/dev/block/mmcblk0p22 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p27 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data= ordered 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022 ,codepage=cp437,iocha
rset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs 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 /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/data/d /data/d debugfs rw,relatime 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allo w_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=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/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso 8859-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.androirc-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=02 22,dmask=0222,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.svox.pico.voice.eng.gbr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=02 22,dmask=
0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

List of defualt files in /dev/block/
mmcblk1p1
mmcblk1
mmcblk0p31
mmcblk0p30
mmcblk0p29
mmcblk0p28
mmcblk0p27
mmcblk0p26
mmcblk0p25
mmcblk0p24
mmcblk0p23
mmcblk0p22
mmcblk0p21
mmcblk0p20
mmcblk0p19
mmcblk0p18
mmcblk0p17
mmcblk0p16
mmcblk0p15
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0

Will find out soon..
Im going to pay my three network to give me the code to unlock my phone, when thay do, ill serch for that code in the files on my device and tell you where you can also get yours.. thats if its not encoded or something..

will be looking forward to this, I also have a 3(uk) locked phone, which i installed a custom rom on, was expecting the phone to open onto all networks (like my old htc touch hd).
good luck, will be checking progress.

sa2am said:
will be looking forward to this, I also have a 3(uk) locked phone, which i installed a custom rom on, was expecting the phone to open onto all networks (like my old htc touch hd).
good luck, will be checking progress.
Click to expand...
Click to collapse
help me here, thanks.
http://forum.xda-developers.com/showpost.php?p=16816803&postcount=1

Ok ive held off paying £15 quid to get the code at the moment, im looking for the code my self.. at the moment the codes ive used dont work, including the date in mmcp6 file..
If you want to try your self.. use ADB..
Open a CMD window and type:
adb shell
su
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
then mount ur sdcard, and open the drive in windows.. and copy the files over.. and open them in hex edotor or notepad dosent really matter what.. and try numbers.. it should be 8 digits..
This is the output from copying the files over for me.. so you can see the byte sizes etc
# dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcp4.dump
2+0 records in
2+0 records out
1024 bytes transferred in 3.160 secs (324 bytes/sec)
# dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcp6.dump
512+0 records in
512+0 records out
262144 bytes transferred in 0.163 secs (1608245 bytes/sec)
# dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcp16.dump
512+0 records in
512+0 records out
262144 bytes transferred in 0.086 secs (3048186 bytes/sec)
#
Heres more info on this subject:
http://forum.xda-developers.com/showthread.php?p=16933050#post16933050
Method one is not the same on my device, though there is a date its not in the same place.. and dosent work..
so im tempted to try mothod 2.. but a bit hessitant to try things that i dont know what damage it would do..
Ok screw it just did method 2 in here:
http://forum.xda-developers.com/showthread.php?p=16933050#post16933050
And POW indeed my sim is now unlocked.. and whats great it it also removed the dumb boot branding screen of Three network as well...

[Q] samsung galaxy wifi 5.0 boot.img

Does this device have a boot.img file that is accessible and editable?
I have the following details from the system files:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 1931264 mmcblk1
179 9 1930240 mmcblk1p1
# grep "mmcblk0" init.rc
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system ro remount
mount rfs /dev/block/mmcblk0p10 /efs nosuid nodev check=no
# mount rfs /dev/block/mmcblk0p16 /data nosuid nodev check=no
mount rfs /dev/block/mmcblk0p16 /data nosuid nodev crypt check=no
mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev crypt check=no
#mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev check=no
mount rfs /dev/block/mmcblk0p15 /cache nosuid nodev check=no
mount j4fs /dev/block/mmcblk0p9 /mnt/.lfs
# 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
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

no mtd in /proc
I also found that there is no /proc/mtd which makes it hard to figure out which mount points are the boot and recovery images.
Code:
# ls /proc/
param
rfs
last_kmsg
batt_info_proc
uid_stat
pvr
apm
sysrq-trigger
partitions
diskstats
crypto
kpageflags
kpagecount
kmsg
softirqs
version
uptime
stat
meminfo
loadavg
interrupts
devices
cpuinfo
cmdline
locks
filesystems
vmallocinfo
zoneinfo
vmstat
pagetypeinfo
buddyinfo
kallsyms
modules
timer_list
iomem
ioports
execdomains
sched_debug
cpu
asound
scsi
misc
fb
wakelocks
irq
cgroups
sys
bus
tty
driver
fs
sysvipc
net
mounts
self
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
37
38
39
40
41
42
49
51
52
53
54
55
56
57
58
59
60
61
62
64
67
68
69
71
72
73
74
75
76
77
78
79
80
84
86
87
91
93
100
120
199
207
212
213
217
234
276
309
419
557
566
574
695
995
1391
1409
2159
5135
5769
8293
8301
9704
10957
10959
10973
14462
14493
21343
32673

YP-G70 - 3 boot logos... wtf?
I successfully flashed the boot logo and replaced the animated boot logo but there is still a samsung boot logo showing up on this device.
When I boot I see my custom boot logo which is written to param.lfs after modifying the name of the original logo.jpg to l0g0.jpg and reflashing via odin. Heimdell won't successfully flash this device although it can extract the pit file without problems.
The custom logo in /mnt/.lfs displays for about 2 seconds then I see the original "samsung" logo for about 5 seconds then I see the custom boot animation.
I replaced the boot animation like this:
# cd /system/bin
# mv samsungani samsungloopani
# mv bootanimation samsungani
# reboot
I added my own custom boot animation "sanim.zip" to /system/media which plays just fine. Samsung have renamed bootanimation.zip to sanim.zip for no apparent reason.
I can't find any info anywhere about this mysterious third logo that shows up between the boot logo and the boot animation.
I found a logo file in /sbin/ called fota.png but it seems that it is not possible or at least undocumented on how to retrieve and edit the samsung "boot.img" to replace /sbin/fota.png with my own logo. Even if I did that I am not certain that it would solve the problem.

no one has any hints?

Turns out the "zImage" partition is located on /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/zImage
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/factoryfs.rfs
dd if=/dev/block/mmcblk0p9 of=/mnt/sdcard/param.lfs

hi i like ur thread
so can i change the
GT-S7500 Logo before boot animation

[Q] Extract recovery.img from your phone

Hey everyone,
I'm having trouble extracting a recovery.img from my phone. More specific I can't seem to find which file I have to 'dd' to create the img file.
Some commands with the output
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
Code:
[email protected]:/ # 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
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
/[email protected] /system ext4 ro,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:97 /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:97 /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
/dev/block/vold/179:6 /mnt/sdcard2 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
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 85216 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15110144 mmcblk1
179 97 15106048 mmcblk1p1
Code:
[email protected]:/ # cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0000ac40 00002800 "sec_ro"
emmc_p3: 00010740 00100000 "android"
emmc_p4: 00110f40 00100000 "cache"
emmc_p5: 00211740 00500000 "usrdata"
emmc_p6: 00711f40 000299c0 "fat"
Even by running the commands above I'm still not able to determine where I can extract a recovery.img.
Ive been looking around and can't seem to find anything so I hope someone can point me in the right direction.
PS: Phone in question is a Star B92M (chinaphone)
Thanks for the help!
~Whookid
EDIT: I'm looking for a way to do this without SP Flash tool

Is your phone rooted? If so, you can create a backup by using a script made available by our fellow Russian users from forum.china-iphone.ru. Give it a shot... here.

I've just remembered that you can also use MTK Droid Root & Tools for that.

[Completed] [Q] Need help finding recovery partition

I've got a fancy new Asus K01A and as far as I can tell, I'm the first to try to root it on xda, or at least the first to try to make CWM for it. When you're making CWM, it's rather important to know exactly where the recovery partitition is, in case I need to flash something from fastboot to correct something stupid it did. Problem is, I can't seem to find a partition for recovery, here's a bunch of partition information I gathered:
/proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 48128 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 21504 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 21504 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 428032 mmcblk0p8
179 9 1187840 mmcblk0p9
259 0 13633519 mmcblk0p10
179 40 4096 mmcblk0rpmb
179 30 8192 mmcblk0gp0
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 3872256 mmcblk1
179 51 3870720 mmcblk1p1
"$ mount" results
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
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=700,uid=1023,gid=1023 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/intel/by-label/system /system ext4 ro,seclabel,noatime,data=
ordered 0 0
/dev/block/platform/intel/by-label/factory /factory ext4 ro,seclabel,noatime 0 0
/dev/block/platform/intel/by-label/cache /cache ext4 rw,seclabel,nosuid,nodev,no
atime,data=ordered 0 0
/dev/block/platform/intel/by-label/config /config ext4 rw,seclabel,nosuid,nodev,
noatime,data=ordered 0 0
/dev/block/platform/intel/by-label/firmware /firmware ext4 ro,seclabel,noatime,d
ata=ordered 0 0
/dev/block/platform/intel/by-label/data /data ext4 rw,seclabel,nosuid,nodev,noat
ime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/intel/by-label/gauge /gauge ext4 rw,seclabel,nosuid,nodev,no
atime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p7 /ADF ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
none /pstore pstore rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:51 /mnt/media_rw/MicroSD vfat rw,dirsync,nosuid,nodev,noexec
,relatime,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:51 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/MicroSD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/platform/intel/by-label contents
lrwxrwxrwx root root 2014-11-28 17:29 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 cache -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 config -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 data -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-28 17:29 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 firmware -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 gauge -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 system -> /dev/block/mmcblk0p9
/dev/block/platform/intel/by-guid contents
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000000 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000001 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000002 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000003 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000004 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000005 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000006 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000007 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000008 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000009 -> /dev/block/mmcblk0p10
Parted info for partitions
Model: MMC 016GE2 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 49.3MB 49.3MB reserved boot
2 49.3MB 57.7MB 8389kB panic boot
3 57.7MB 59.8MB 2097kB ext2 factory
4 59.8MB 81.8MB 22.0MB ext4 config
5 81.8MB 82.9MB 1049kB ext2 gauge
6 82.9MB 105MB 22.0MB ext4 firmware
7 105MB 138MB 33.6MB ext4 ADF
8 138MB 577MB 438MB ext4 cache
9 577MB 1793MB 1216MB ext4 system
10 1793MB 15.8GB 14.0GB ext4 data
I'm wondering if somehow there is a specific file or if the recovery is somehow integrated into the bootloader. If so, my hopes are dashed :crying:

Hi,
I would ask if anyone knows anything here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!

Need a little hand figuring out the partition layout on an Acer A1-830 (intel based)

My wife has the above A1-830, it worked for years with little problem after rooting. Fast forward a few months and due to life/career changes, it gets put away for a while. I brought it out a few months ago to give it a top up charge before putting it away and it still worked fine. I go to bring it back out recently, only to find that it's stuck on the loading android logo (where the logo shimmers). Fast forward again after a couple weeksand when I now have the motivation to look into it further, it now no longer starts and the shimmering logo just sits there. I connected a USB cable and have full root access over ADB, however I now seemingly have no way to get into droidboot/fastboot/recovery on this device. All attempts simply hang, with "fastboot devices" not showing anything.
After looking into this a little (and finding this and this blog post) I realised that I can use dd to overwrite the recovery and boot volume and hopefully bring this tablet back to life. The snag is that the points suggested within that blog that I can identify what partition resides where, are absent on this device (I figure maybe it's due to it being intel and not ARM architecture).
My problem is I unfortunately I don't know which ones to mess around with, and would very much like to avoid overwriting the wrong one or risking mounting the wrong partition and managing to break something in an unexpected way while poking around and trying to figure out the partitions to overwrite with what.
Partition Table
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
.
179 0 15376384 mmcblk0
179 1 167936 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 32768 mmcblk0p3
179 4 131072 mmcblk0p4
179 5 131072 mmcblk0p5
179 6 786432 mmcblk0p6
179 7 262144 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 12275692 mmcblk0p9
179 40 8192 mmcblk0gp0
179 30 8 mmcblk0rpmb
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 1931264 mmcblk1
179 51 1931200 mmcblk1p1
/proc/mounts
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 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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /factory ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p8 /system ext4 ro,noatime,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,noatime,journal_checksum,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p5 /config ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p9 /data ext4 rw,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p7 /logs ext4 rw,nosuid,nodev,relatime,journal_checksum,journal_async_commit,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
contents of "partition.tbl" within the ROM i wish to write.
Code:
partition_table=gpt
create -z /dev/block/mmcblk0
create /dev/block/mmcblk0
boot -p /dev/block/mmcblk0
reload /dev/block/mmcblk0
add -b 40 -s 335872 -t efi -u 80868086-8086-8086-8086-000000000000 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 335912 -s 16384 -t efi -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 352296 -s 65536 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 417832 -s 262144 -t data -u 80868086-8086-8086-8086-000000000003 -l misc -T 0 -P 0 /dev/block/mmcblk
add -b 679976 -s 262144 -t data -u 80868086-8086-8086-8086-000000000004 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 942120 -s 1572864 -t data -u 80868086-8086-8086-8086-000000000005 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 2514984 -s 524288 -t data -u 80868086-8086-8086-8086-000000000006 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 3039272 -s 3145728 -t data -u 80868086-8086-8086-8086-000000000007 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 6185000 -s $calc($lba_end-16384) -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0
reload /dev/block/mmcblk0
Now I'm sure I can figure out from this which partition to write it to, however I would much rather get the answer (or pointers on where to look) to get a more concrete answer than "i think boot.img/fastboot.img/recovery.img goes ..." as frankly I feel this thing is recoverable in it's current state, and I don't want to go digging myself a deeper hole than I already need to with this.
I've spent the better part of 6+ hours trying to figure this out looking at various threads on XDA and searching online in general, any pointers for myself? anyone?