I've been reading through many threads on the subject, and it seems that we still don't have a reliable way to root this phone.
Is there any word yet on a TWRP build? Are there any viable alternatives to TWRP?
I'm really starting to miss some of the apps I use that require root.
There are very reliable methods that work..
Just look within this forum.
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
xichael said:
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
Click to expand...
Click to collapse
Root doesn't differ from model variants. It's not perfect but works most of the time.
xichael said:
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
Click to expand...
Click to collapse
Nothing bad will happen if you do the steps right. Head over to the bootloader unlock thread.
I'm not taking any chances. To quote from another thread:
evilpaul13 said:
The SuperSU's not the problem it's nobody's made a working TWRP for FRD-L04. I've seen lots of people who tried the Mondaco TWRP on L04 say they just got a bootloop with one guy saying it worked, but he couldn't make a backup and just install the root package.
Click to expand...
Click to collapse
Try philz touch recovery or other cwm recovery for rooting honor 8
xichael said:
I've been reading through many threads on the subject, and it seems that we still don't have a reliable way to root this phone.
Is there any word yet on a TWRP build? Are there any viable alternatives to TWRP?
I'm really starting to miss some of the apps I use that require root.
Click to expand...
Click to collapse
I am also hesitant to do this on my brand new L04. What are the steps to download and flash the stock ROM for this specific model in case it is bricked? I have not found anything about this yet.
I'd very much like to be able to root, but everything I've read makes it look less than promising at the moment. Honor has the B122 firmware from September on their site: http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
I'm running B150 though which I got OTA and don't really want to go back to an older version with broken auto-brightness if things don't go right. I had B144 when I got the thing.
So the initial release firmware is available for the L04? I guess we can flash it with Hisuite?
If we want to get TWRP working on L04 we need to send partition mount info to the developer that made TWRP work on the other Honor 8 models. I am not sure who that person would be. I have attached the info I am able to get without root. We may need `cat /proc/mtd`. But this virtual device can only be read by root. If anyone has working root on L04 please post here and share with TWRP developer for Honor 8.
Code:
1|[email protected]:/ $ cat /proc/partitions
major minor #blocks name
253 0 524288 zram0
179 0 30535680 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 12288 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 65536 mmcblk0p30
179 31 65536 mmcblk0p31
179 32 16384 mmcblk0p32
179 33 8192 mmcblk0p33
179 34 16384 mmcblk0p34
179 35 65536 mmcblk0p35
179 36 262144 mmcblk0p36
179 37 2048 mmcblk0p37
179 38 2048 mmcblk0p38
179 39 3670016 mmcblk0p39
179 40 524288 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 25255936 mmcblk0p42
179 96 4096 mmcblk0rpmb
179 48 4096 mmcblk0boot0
179 144 61259776 mmcblk1
179 145 61258752 mmcblk1p1
252 0 3641084 dm-0
252 1 520124 dm-1
252 2 25255920 dm-2
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1869360k,nr_inodes=467340,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,ionice,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/frz cgroup rw,relatime,freezer 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=750,gid=1000 0 0
none /sys/fs/cgroup/pids cgroup rw,relatime,pids 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime,gid=1000,mode=755 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/block/vold/public:179:145 /mnt/media_rw/1EF6-36FE exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,iocharset=utf8,namecase=0,errors=remount-ro 0 0
/dev/fuse /mnt/runtime/default/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/dm-1 /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/splash2 /splash2 ext4 rw,context=u:object_r:splash2_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodem /3rdmodem ext4 ro,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodemnvm /3rdmodemnvm ext4 rw,context=u:object_r:radio_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodemnvmbkp /3rdmodemnvmbkp ext4 rw,context=u:object_r:radio_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/secure_storage /sec_storage ext4 rw,context=u:object_r:teecd_data_file:s0,nosuid,nodev,noatime,discard,nodelalloc,data=journal 0 0
/dev/block/bootdevice/by-name/modemnvm_img /mnvm2:0 ext4 rw,context=u:object_r:modem_nv_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/modem_om /modem_log ext4 rw,context=u:object_r:modem_log_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/dm-2 /data f2fs rw,seclabel,nosuid,nodev,noatime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,extent_cache,active_logs=6 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/fuse /storage/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/self tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
[email protected]:/ $
Tk has a video. Watch it.
kevev said:
I am also hesitant to do this on my brand new L04. What are the steps to download and flash the stock ROM for this specific model in case it is bricked? I have not found anything about this yet.
Click to expand...
Click to collapse
It's pretty much like any Huawei. And I think the worst case is bootloop, except if you flash some other's model recovery or system.
Download stock full OTA
Extract boot.img, recovery.img, cust.img and system.img from update.app file with Huawei firmware extractor.
To go back to stock just flash boot and recovery partitions.
kevev said:
...we need to send partition mount info to the developer that made TWRP work on the other Honor 8 models. I am not sure who that person would be...
Click to expand...
Click to collapse
Here's the thread where it was originally posted: http://www.modaco.com/forums/topic/377647-twrp-recovery-3020-for-honor-8/
Here's the dev's xda acct: http://forum.xda-developers.com/member.php?u=220328
xichael said:
Here's the thread where it was originally posted: http://www.modaco.com/forums/topic/377647-twrp-recovery-3020-for-honor-8/
Here's the dev's xda acct: http://forum.xda-developers.com/member.php?u=220328
Click to expand...
Click to collapse
Thanks. I sent the dev a PM earlier today on XDA. No preply yet. I am not able to register on modaco. I never receive the registration email. Could someone ping him there for me?
Sent from my FRD-L04 using XDA Free mobile app
kevev said:
Thanks. I sent the dev a PM earlier today on XDA. No preply yet. I am not able to register on modaco. I never receive the registration email. Could someone ping him there for me?
Click to expand...
Click to collapse
Done!
Tmobilefan906 said:
Done!
Click to expand...
Click to collapse
Appreciated
Sent from my FRD-L04 using XDA Free mobile app
So there's finally a working copy of TWRP for the Honor 8: https://twrp.me/devices/huaweihonor8.html
And fortunately the backup/restore feature works properly, as I needed it after UPDATE-SuperSU-v2.46.zip threw my phone into a bootloop.
Is there a different SuperSU zip I could try flashing?
EDIT:
Found the current v2.78, which worked fine: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Google's top results were pointing to the old version on chainfire.eu. Shoulda checked here first...
xichael said:
So there's finally a working copy of TWRP for the Honor 8: https://twrp.me/devices/huaweihonor8.html
And fortunately the backup/restore feature works properly, as I needed it after UPDATE-SuperSU-v2.46.zip threw my phone into a bootloop.
Is there a different SuperSU zip I could try flashing?
Click to expand...
Click to collapse
46 is outdated. Try 78. If it's still giving you bootloop, try phh's SU.
Sent from my honor 5X using XDA Labs
GensTattu said:
I want somebody can help me finished it, it is too difficult for me .
Click to expand...
Click to collapse
What step are you on?
Related
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...
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
I tried to install cyanogenmod (cm-11-20140504-SNAPSHOT-M6-m4.zip) and in the process I probably did something wrong
Any help is highly appreciated.
The header in the unlocked bootloader is:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.24.40e.00.26
Recovery can be easily flashed via
Code:
sudo fastboot flash recovery recovery-clockwork-touch-6.0.4.8-m4.img
After selecting "BOOTLOADER" > "RECOVERY", I get the error messages
Code:
ClockworkMod Recovery v6.0.4.8
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:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
After sideloading "adb sideload cm-11-20140504-SNAPSHOT-M6-m4.zip", I receive the following error messages
Code:
Restarting adbd...
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: File exists
Finding update package...
Opening update package...
Installing update...
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
If anybody can help me, that would be great. (Flashin the Nexus4 was so much more fun )
Ive not seen a cwm v6.0.4.8 for the Htc Mini (m4) i could be wrong?
either try flashing philz latest touch recovery v6.41.6 from here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m4
or twrp 2.7.0.8 from here http://mdmower.cmphys.com/twrp-m4/
these two support the new partition layout.
Braddison said:
Ive not seen a cwm v6.0.4.8 for the Htc Mini (m4) i could be wrong?
either try flashing philz latest touch recovery v6.41.6
or twrp 2.7.0.8
these two support the new partition layout.
Click to expand...
Click to collapse
With philz and twrp I get the same behaviour (warnings and errors).
Try changing the name of your recovery "recovery-clockwork-touch-6.0.4.8-m4.img" to just "recovery.img" (its easier and less chance of a typo)
then try this sudo fastboot flash recovery /path/to/recovery.img
hopefully that will give you a working recovery,if that fails do the same with a different recovery
hope that helps,cheers
Braddison said:
Try changing the name of your recovery "recovery-clockwork-touch-6.0.4.8-m4.img" to just "recovery.img" (its easier and less chance of a typo)
then try this sudo fastboot flash recovery /path/to/recovery.img
hopefully that will give you a working recovery,if that fails do the same with a different recovery
hope that helps,cheers
Click to expand...
Click to collapse
I am not sure why renaming the file would help, but I did anyway.
Still, I get the same errors.
Jini.Dough said:
I am not sure why renaming the file would help, but I did anyway.
Click to expand...
Click to collapse
as stated in previous post, it's for ease of use and less likely to make a spelling mistake causing things to go t*ts up
am thinking your partitions are messed up,
try used twrp1 2.7.0.8 recovery
Sent from my HTC One mini
did you tried OTG option inside of the twrp via OTG cable and usb flashdisc?
410eaL said:
try used twrp1 2.7.0.8 recovery
Click to expand...
Click to collapse
I am not sure if I do understand what you mean by twrp1. Do you have a link.
mypat said:
did you tried OTG option inside of the twrp via OTG cable and usb flashdisc?
Click to expand...
Click to collapse
No, I did not try this. I am not sure if I have an OTG cable.
Since mounting of cache seems the main problem, I tried to get some information about the partitions. Does anybody recognize if these partitions are OK or if I do have to apply some change here:
Code:
adb shell
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2080 mmcblk0p12
179 13 5120 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 46080 mmcblk0p16
179 17 10240 mmcblk0p17
179 18 5120 mmcblk0p18
179 19 8190 mmcblk0p19
179 20 4096 mmcblk0p20
179 21 28671 mmcblk0p21
179 22 1022 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 20480 mmcblk0p25
179 26 4 mmcblk0p26
179 27 256 mmcblk0p27
179 28 16 mmcblk0p28
179 29 1280 mmcblk0p29
179 30 64 mmcblk0p30
179 31 1448 mmcblk0p31
179 32 32767 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 16383 mmcblk0p34
179 35 2195455 mmcblk0p35
179 36 688127 mmcblk0p36
179 37 11927552 mmcblk0p37
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 399632 128 399504 0% /dev
tmpfs 399632 8 399624 0% /tmp
tmpfs 399632 0 399632 0% /storage
tmpfs 399632 0 399632 0% /mnt/secure
tmpfs 399632 0 399632 0% /mnt/fuse
~ # mount
rootfs on / type rootfs (rw,seclabel)
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 /tmp type tmpfs (rw,seclabel,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)
To me it appears as if /cache does not even exist anymore. The recovery seems to be OK, since the selinuxfs is used for a sys-partition.
Braddison, do you know how to fix the partition?
Jini.Dough said:
Braddison, do you know how to fix the partition?
Click to expand...
Click to collapse
I’m afraid I don’t.
I would try the above recoveries ensuring that they are copied in your fastboot folder , and spelled exactly the same when flashing.
Then try a different rom other than CM , just to see if you can boot . can always flash cm at a later date from recovery.
Hopefully someone on here will come to the rescue.
Hi,
This is basically a fork of the Query I made in Here.
I am trying to root Zenfone C and will try to build a custom recovery(TWRP2) for this device. Any help/guidance will be greatly appreciated.
Code:
[email protected]_Z007:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 7626752 mmcblk0
179 1 131072 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 32768 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 32768 mmcblk0p5
179 6 716800 mmcblk0p6
179 7 196608 mmcblk0p7
179 8 32768 mmcblk0p8
179 9 2097152 mmcblk0p9
259 0 4362220 mmcblk0p10
179 40 4096 mmcblk0rpmb
179 30 8192 mmcblk0gp0
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 7761920 mmcblk1
179 51 7757824 mmcblk1p1
Above is the partition table and below is the mount details
Code:
[email protected]_Z007:/ $ cat /proc/mounts
cat /proc/mounts
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=755,gid=1000 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/factory /factory ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/intel/by-label/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/intel/by-label/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,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/data /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/intel/by-label/ADF /ADF ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/block/mmcblk0p7 /APD ext4 rw,seclabel,noatime,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
/dev/block/vold/179:51 /mnt/media_rw/MicroSD vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,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,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,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=1023,default_permissions,allow_other 0 0
I would like to do a system dump first. Any idea how do I get started? The stock recovery does only sideload and does not allow unsigned zip/system mount.
Reserved #1
Reserved #1
Reserved #2
Reserved #2
Reserved #3
Reserved #3
help plz
hey buddy. glad to know tht u r a zenfone c user too. even m a zenfone c user. due to some issue, my zenfone c is stuck on bootloop [asus logo].
i need a favor from u buddy.
cud u plz provide me with the backup of the stock rom from ur zenfone c.
i cant find a stock rom/firmware/flash file for the zenfone c.
plz buddy.
in return i'd help u for anything.
plz buddy.
thnx a ton in regards.
waiting fr ur response.
dj4v1n45h said:
hey buddy. glad to know tht u r a zenfone c user too. even m a zenfone c user. due to some issue, my zenfone c is stuck on bootloop [asus logo].
i need a favor from u buddy.
cud u plz provide me with the backup of the stock rom from ur zenfone c.
i cant find a stock rom/firmware/flash file for the zenfone c.
plz buddy.
in return i'd help u for anything.
plz buddy.
thnx a ton in regards.
waiting fr ur response.
Click to expand...
Click to collapse
1. Remove your battery
2. Start phone with Power+Volume Up
3. Droid Boot menu will boot.
4. Select with Volume Up/Volume Down
5. Confirm Selection with Power Button
6. Select Factory Reset and Go
Check if phone is booting.
Found a Great way to root Zenfone C without touching anything HERE by our kind friend superuser.pm
I have tried the commands in the rar file as manual commands in fastboot mode and voila!! It is rooted now.
I have also tried the unroot and re-rooted it again. Works flawlessly.
I will immediately try to make a system dump and start working on a custom recovery(TWRP2).
Let us check the OTA and how it behaves now with rooted Zenfone C. :laugh::fingers-crossed::good:
abhis3k said:
Found a Great way to root Zenfone C without touching anything HERE by our kind friend superuser.pm
I have tried the commands in the rar file as manual commands in fastboot mode and voila!! It is rooted now.
I have also tried the unroot and re-rooted it again. Works flawlessly.
I will immediately try to make a system dump and start working on a custom recovery(TWRP2).
Let us check the OTA and how it behaves now with rooted Zenfone C. :laugh::fingers-crossed::good:
Click to expand...
Click to collapse
Unfortunately I have to revert to unroot the device as while updating the SuperSu from Play Store, the device becomes unresponsive and reboot randomly. I will check it later. For now, this method of rooting is unusable. :crying:
hey thanks a lot for ur quick response.
I be done wit all those methods. Now the fon isn't even bootin up since today noon. Buddy m totally worried. Buddy if u won mind cud u contact me on whatsapp. My no. is 07204633698. Plz and thanks a lot buddy for ur quick response. Buddy in return I ll do anything for u. Coz I believe that u r d only one who can help me out. Waiting for u on whatsapp, buddy. Tc. C ya.
dj4v1n45h said:
I be done wit all those methods. Now the fon isn't even bootin up since today noon. Buddy m totally worried. Buddy if u won mind cud u contact me on whatsapp. My no. is 07204633698. Plz and thanks a lot buddy for ur quick response. Buddy in return I ll do anything for u. Coz I believe that u r d only one who can help me out. Waiting for u on whatsapp, buddy. Tc. C ya.
Click to expand...
Click to collapse
As discussed with you, I am really very sorry if your phone is hard bricked.
Please find the /system/app and /system/bin dump HERE
hey its ok frnd. i finally got my ZC replace with a new unit.
Can any one plz give me the link of any custom recovery for asus zenfone c.....i badly need it plz help me...thnks in advance.....plz give me..and tell me how to flash it.....
Regarding Pixel 32GB, I want to know the size of each partition(boot, system etc).
Please show below via adb shell.
cat /proc/partitions
ls -l /dev/block/platform/soc/7824900.sdhci/by-name
notice: "7824900.sdhci" is diffirent name folder.
Sorry, the following path is correct.
ls -l /dev/block/bootdevice/by-name
Can't list the /dev directory due to lack of permissions. Best I can give you is /proc/partitions:
Code:
sailfish:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
8 0 31145984 sda
8 1 512 sda1
8 2 512 sda2
8 3 512 sda3
8 4 512 sda4
8 5 2048 sda5
8 6 2048 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 512 sda10
8 11 512 sda11
8 12 512 sda12
8 13 256 sda13
8 14 256 sda14
8 15 256 sda15
259 0 256 sda16
259 1 4096 sda17
259 2 4096 sda18
259 3 32768 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 32768 sda22
259 7 128 sda23
259 8 128 sda24
259 9 71680 sda25
259 10 71680 sda26
259 11 256 sda27
259 12 256 sda28
259 13 256 sda29
259 14 256 sda30
259 15 307200 sda31
259 16 307200 sda32
259 17 2097152 sda33
259 18 2097152 sda34
259 19 26038272 sda35
259 20 4820 sda36
8 32 4096 sdc
8 33 4052 sdc1
8 16 4096 sdb
8 17 4052 sdb1
8 48 49152 sdd
8 49 1024 sdd1
8 50 8 sdd2
8 51 32768 sdd3
8 52 128 sdd4
8 53 4 sdd5
8 54 4 sdd6
8 55 1024 sdd7
8 56 4 sdd8
8 57 2048 sdd9
8 58 2048 sdd10
8 59 1024 sdd11
8 60 4 sdd12
8 61 9020 sdd13
8 64 36864 sde
8 65 512 sde1
8 66 6144 sde2
8 67 4096 sde3
8 68 2048 sde4
8 69 16384 sde5
8 70 7636 sde6
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 5824 sdf5
253 0 2064396 dm-0
253 1 302360 dm-1
Thank you so much for reply!
I have a another request.
Please show below via adb shell.
df
mount
tatsu_vel said:
Thank you so much for reply!
I have a another request.
Please show below via adb shell.
df
mount
Click to expand...
Click to collapse
Here you go:
sailfish:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1999708 1484912 498412 75% /
tmpfs 1898468 440 1898028 1% /dev
tmpfs 1898468 0 1898468 0% /mnt
/dev/block/dm-1 292868 223040 63784 78% /vendor
/dev/block/bootdevice/by-name/userdata 25497924 8109564 17371976 32% /data
/dev/fuse 25497924 8109564 17371976 32% /storage/emulated
sailfish:/ $ mount
rootfs on / type rootfs (rw,seclabel)
/dev/root on / type ext4 (ro,seclabel,relatime,data=ordered)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1898468k,nr_inodes=474617,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1898468k,nr_inodes=474617,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/dm-1 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/modem_a on /firmware/radio type vfat (ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1898468k,nr_inodes=474617,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Click to expand...
Click to collapse