Hi there,
The device is rooted.
But
Code:
adb shell ls -l /dev/block/bootdevice/by-name
It returned
Code:
/dev/block/bootdevice/by-name: Permission denied
However,
Code:
adb shell su -c 'ls -l /dev/block/bootdevice/by-name'
It returned
Code:
lrwxrwxrwx root root 1970-01-21 16:08 DDR -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-21 16:08 DRIVER -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-21 16:08 LOGO -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-21 16:08 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-21 16:08 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-21 16:08 apdp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-21 16:08 bluetooth -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-21 16:08 boot -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-21 16:08 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-21 16:08 config -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-21 16:08 devinfo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-21 16:08 dpo -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-21 16:08 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-21 16:08 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-21 16:08 hyp -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-21 16:08 hypbak -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-21 16:08 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-21 16:08 limits -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-21 16:08 misc -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-21 16:08 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-21 16:08 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-21 16:08 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-21 16:08 msadp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-21 16:08 oem_dycnvbk -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-21 16:08 oem_stanvbk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-21 16:08 param -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-21 16:08 persist -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-21 16:08 pmic -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-21 16:08 pmicbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-21 16:08 recovery -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-21 16:08 reserve1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-21 16:08 reserve2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-21 16:08 rpm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-21 16:08 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-21 16:08 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-21 16:08 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-21 16:08 sdi -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-21 16:08 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-21 16:08 ssd -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-21 16:08 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-21 16:08 tz -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-21 16:08 tzbak -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-21 16:08 userdata -> /dev/block/mmcblk0p43
In addition,
Code:
adb pull /dev/block/mmcblk0p43 43.img
It returned
Code:
adb: error: remote object '/dev/block/mmcblk0p43' does not exist
How to resolve the issue of "permission denied"?
Why are there differences in terms of results between adb shell ls -l /dev/block/bootdevice/by-name and adb shell su -c 'ls -l /dev/block/bootdevice/by-name'?
Why adb pull failed to create a disk image?
Is mmcblk0p43 recognized as a file so adb pull could copy it out of /dev/block/?
Thanks in advance.
--- Solution ---
Install adbd insecure and check "Enable insecure adbd" and"Enable as boot", these two boxes;
However, it ensued another problem that the device is no more recognised by adb. And this issue is solved by
- installing SELinux Switch and choosing "Permissive".
And both
Code:
adb shell ls -l /dev/block/bootdevice/by-name
and
Code:
adb pull /dev/block/mmcblk0p43 43.img
worked.
But how come that adbd insecure could enable the 2 commands above?
Apparently the device's bootloader is locked.
Code:
fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.072s]
wenyendev said:
Hi there,
The device is rooted.
But
Code:
adb shell ls -l /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
There are 2 ways:
1. Use adb shell su instead. And then copy everything from root dir into internal storage after that you can pull files from internal storage using adb pull
2. Disable selinux enforcing with setenforce 0
'adb root' done?
CXZa said:
'adb root' done?
Click to expand...
Click to collapse
After adb root, it returned
Code:
adbd cannot run as root in production builds
Solved.. okay, I just leave this to this thread then. One more option...
Code:
adb exec-out "su -c cat /dev/block/mmcblk0p43" > [full path\]43.img
Above should work but there is quite many cases that it doesn't, i.e. \n are replaced with \r\n corrupting the file. Then below should fix the problem. If exec-out doesn't work, shell can be used too...
Code:
adb exec-out "su -c cat /dev/block/mmcblk0p43" | dos2unix -f > [full path\]43.img
More info...
Read binary stdout data like screencap data from adb shell?
Is it possible to read binary stdout from an adb shell command? For example, all examples of how to use screencap include two steps: adb shell screencap -p /sdcard/foo.png adb pull /sdcard/foo.png
stackoverflow.com
@CXZa dos2unix does not solve it, will mess up even more. best workaround so far is compress/decompress (for example gzip) also take care about exec-out stderr is mixed up with stdout.
btw @wenyendev the answer applies to all your following questions:
adbd cannot run as root in production builds. you have three options. 1) use adb root in TWRP recovery mode. 2) use insecure adbd daemon 3) use adb shell su shell instead. that's it.
https://forum.xda-developers.com/t/...as-root-in-production-builds-adb-root.4528831
https://forum.xda-developers.com/t/permission-denied-following-ls-dev-block.4530681
https://forum.xda-developers.com/t/permission-denied-cat-proc-partitions.4494267
https://forum.xda-developers.com/t/...wing-partition-identification-command.4528373
https://forum.xda-developers.com/t/...rtition-on-an-unrooted-android-device.4528247
https://forum.xda-developers.com/t/...ied-under-adb-shell-after-granting-su.4528815
https://forum.xda-developers.com/t/dd-versus-adb-pull.4535577
https://forum.xda-developers.com/t/closed-how-to-pull-partition-to-external-disk.4537667
Btw original SELinuxModeChanger by @MrBIMC occupied by SELinux Toggler (which is basically same as Selinux Switch) will work only on kernel that support developer mode.
[APP][Root][4.2+]SELinuxModeChanger v10.0 :: [24.07.2017]
Now opensourced under gplv3! GITHUB Get it in f-droid F-DROID page (v10 probably won't be there until release of stable gradle 4.0 and buildtools 26) Now available on the XDA Labs! XDA Labs page (UPD: somebody released a fork without changing...
forum.xda-developers.com
aIecxs said:
dos2unix does not solve it, will mess up even more.
Click to expand...
Click to collapse
No it doesn't. It is explained in the comments in the link I gave...
I know that link (and comments)
please try your own
https://pastebin.com/Z5ptLhqM
Various tests there. Tried with cache too in Windows using the latest dos2unix version mentioned there. Works if one has that problem, if not might make a mess. But in your case it looks like the file sizes aren't the same even when the command is the same. Odd...
Edit: I actually used shell too with the cache... exec-out also with some smaller files. So the exec-out can give different outputs... Edit2: As well as dos2unix it seems. Odd...
it works best with compressed streams as the decompression algorithm can handle minor encoding issues (such as CR CR LF)
Code:
C:\Android> adb exec-out su -c "cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/cache 2> /dev/null | gzip" > cache.img.gz
after unpacking gzip (7-zip) I recommend checksum (if possible) but might not work "online"
Code:
CUBOT_KING_KONG:/ # md5sum /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/cache
C:\Android> certutil.exe -hashfile cache.img MD5
@wenyendev does not concern you as afaik you're on darwin/macOS
You did a lot of tests indeed. BTW, not the best partition that cache of yours for testing dos2unix. Nothing to do for it as it didn't change a thing in those last files that worked.
So, many things might not work and shell is probably better option to use, and linux and compression. Still, if one doesn't have enough space i.e. sd card, it's an option...
Tested again. For me shell and exec-out work the same way. Both need the dos2unix treatment. Repeated it and it messed the file as there was still "leftovers" in it...
Code:
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" > C:\bin\adb\cache_aaa.img
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_bbb.img
C:\bin\adb>adb exec-out "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_ccc.img
C:\bin\adb>adb shell "su -c md5sum /dev/block/mmcblk0p47"
a87484dff7370bf71a253ee9af6baedf /dev/block/mmcblk0p47
C:\bin\adb>md5sum C:\bin\adb\cache_*.img
\2922f7f1ab51fa650779586e291e6783 *C:\\bin\\adb\\cache_aaa.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_bbb.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_ccc.img
C:\bin\adb>dos2unix -f -n cache_ccc.img cache_ddd.img
dos2unix: converting file cache_ccc.img to file cache_ddd.img in Unix format...
C:\bin\adb>md5sum C:\bin\adb\cache_ddd.img
\de27ad05c61510f4847651c44ab9922e *C:\\bin\\adb\\cache_ddd.img
results may differ between Win 7 10 11 cmd PowerShell platform tools and adb version
CXZa said:
Tested again. For me shell and exec-out work the same way. Both need the dos2unix treatment. Repeated it and it messed the file as there was still "leftovers" in it...
Code:
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" > C:\bin\adb\cache_aaa.img
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_bbb.img
C:\bin\adb>adb exec-out "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_ccc.img
C:\bin\adb>adb shell "su -c md5sum /dev/block/mmcblk0p47"
a87484dff7370bf71a253ee9af6baedf /dev/block/mmcblk0p47
C:\bin\adb>md5sum C:\bin\adb\cache_*.img
\2922f7f1ab51fa650779586e291e6783 *C:\\bin\\adb\\cache_aaa.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_bbb.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_ccc.img
C:\bin\adb>dos2unix -f -n cache_ccc.img cache_ddd.img
dos2unix: converting file cache_ccc.img to file cache_ddd.img in Unix format...
C:\bin\adb>md5sum C:\bin\adb\cache_ddd.img
\de27ad05c61510f4847651c44ab9922e *C:\\bin\\adb\\cache_ddd.img
Click to expand...
Click to collapse
Apparently it did not work out for me.
CXZa said:
Tested again. For me shell and exec-out work the same way. Both need the dos2unix treatment. Repeated it and it messed the file as there was still "leftovers" in it...
Code:
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" > C:\bin\adb\cache_aaa.img
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_bbb.img
C:\bin\adb>adb exec-out "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_ccc.img
C:\bin\adb>adb shell "su -c md5sum /dev/block/mmcblk0p47"
a87484dff7370bf71a253ee9af6baedf /dev/block/mmcblk0p47
C:\bin\adb>md5sum C:\bin\adb\cache_*.img
\2922f7f1ab51fa650779586e291e6783 *C:\\bin\\adb\\cache_aaa.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_bbb.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_ccc.img
C:\bin\adb>dos2unix -f -n cache_ccc.img cache_ddd.img
dos2unix: converting file cache_ccc.img to file cache_ddd.img in Unix format...
C:\bin\adb>md5sum C:\bin\adb\cache_ddd.img
\de27ad05c61510f4847651c44ab9922e *C:\\bin\\adb\\cache_ddd.img
Click to expand...
Click to collapse
Apparently it did not work on my device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The environment is adb on Macintosh High Sierra.
Whether I enabled adbd insecure & Selinux, it produced the same result.
aIecxs said:
@CXZa dos2unix does not solve it, will mess up even more. best workaround so far is compress/decompress (for example gzip) also take care about exec-out stderr is mixed up with stdout.
btw @wenyendev the answer applies to all your following questions:
adbd cannot run as root in production builds. you have three options. 1) use adb root in TWRP recovery mode. 2) use insecure adbd daemon 3) use adb shell su shell instead. that's it.
https://forum.xda-developers.com/t/...as-root-in-production-builds-adb-root.4528831
https://forum.xda-developers.com/t/permission-denied-following-ls-dev-block.4530681
https://forum.xda-developers.com/t/permission-denied-cat-proc-partitions.4494267
https://forum.xda-developers.com/t/...wing-partition-identification-command.4528373
https://forum.xda-developers.com/t/...rtition-on-an-unrooted-android-device.4528247
https://forum.xda-developers.com/t/...ied-under-adb-shell-after-granting-su.4528815
https://forum.xda-developers.com/t/dd-versus-adb-pull.4535577
Btw original SELinuxModeChanger by @MrBIMC occupied by SELinux Toggler (which is basically same as Selinux Switch) will work only on kernel that support developer mode.
[APP][Root][4.2+]SELinuxModeChanger v10.0 :: [24.07.2017]
Now opensourced under gplv3! GITHUB Get it in f-droid F-DROID page (v10 probably won't be there until release of stable gradle 4.0 and buildtools 26) Now available on the XDA Labs! XDA Labs page (UPD: somebody released a fork without changing...
forum.xda-developers.com
Click to expand...
Click to collapse
What do you mean by using adb root in recovery TWRP mode?
The command above was run in the "Terminal" <- "Advanced" in TWRP.
wenyendev said:
What do you mean by using adb root in recovery TWRP mode?
Click to expand...
Click to collapse
Just connect the usb cable and try it in mac's terminal.
CXZa said:
Just connect the usb cable and try it in mac's terminal.
Click to expand...
Click to collapse
Ok, adb root worked only when adbd insecure is enabled.
in TWRP recovery, adb root is already enabled by default. no need to type 'adb root'
on macOS one have to install dos2unix
Code:
brew install dos2unix
aIecxs said:
in TWRP recovery, adb root is already enabled by default. no need to type 'adb root'
on macOS one have to install dos2unix
Code:
brew install dos2unix
Click to expand...
Click to collapse
After installation of dos2unix,
Code:
./adb shell "su -c cat /dev/block/mmcblk0p43" | dos2unix -f /Users/wenyuan/Desktop/android/adb/43.img
still did not work.
Now you need that ">"...
Code:
./adb shell "su -c cat /dev/block/mmcblk0p43" | dos2unix -f > /Users/wenyuan/Desktop/android/adb/43.img
But do you have that \n replacing problem? If not dos2unix is not needed.
Code:
./adb shell "su -c cat /dev/block/mmcblk0p43" > /Users/wenyuan/Desktop/android/adb/43.img
Related
Hello XDA-Developers!
I want to install Back Track 5 ARM in my AllWinner A10 based tablet, I followed the lesson for Galaxy and I downloaded the boot script for Galaxy and the bt5.img(3.25G). I changed some of the codes to launch BT5 in external sdcard and suit my ROM,then launched it, only to find some errors. Well, the source code of the boot script(modified by myself to suit my device) like this:
perm=$(id|busybox cut -b 5)
if [ "$perm" != "0" ];then echo "This Script Needs Root! Type : su";exit;fi
mount -o remount,rw /dev/block/mmcblk0p1 /system
export kit=/mnt/extsd/BT5
export bin=/system/bin
export mnt=/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/
if [ -b /dev/loop2 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop2 b 7 0
fi
busybox mount -o loop,noatime -t extsd $kit/bt5.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $/etc/hosts
busybox chroot $/bin/bash
echo "Shutting down BackTrack ARM For Xoom"
umount $/dev/pts
umount $/proc
umount $/sys
umount $mnt
when I launch the script(bootbtV) in Terminal Emulator, only to find some errors like this:
[email protected]:/ $ su
[email protected]:/ # cd mnt/extsd/BT5
[email protected]:/mnt/extsd/BT5 # sh bootbtV
Loop device exists
mount: mounting /dev/loop8 on /mnt failed: No such device
mount: mounting /dev/pts on /mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /mnt/proc failed: No such file or directory
mount: mounting /sys on /mnt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
bootbtV[23]: can't create $/etc/resolv.conf: No such file or directory
bootbtV[24]: can't create $/etc/hosts: No such file or directory
chroot: can't change root directory to $/bin/bash: No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/mnt/extsd/BT5 #
Well, In my opinion, according to the errors "No such file or directory", I think it is the difference between my device and Galaxy that causes the errors. In my device, the file structure is different from what the boot script means, such is the file structure of my device's root directory:
drwxr-xr-x root root 2013-01-16 11:22 acct
drwxrwx--- system cache 2013-01-16 09:51 cache
dr-x------ root root 2013-01-16 11:22 config
lrwxrwxrwx root root 2013-01-16 11:22 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-13 17:14 data
-rw-r--r-- root root 116 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-01-16 11:27 dev
lrwxrwxrwx root root 2013-01-16 11:22 etc -> /system/etc
-rwxr-x--- root root 105268 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 19030 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2644 1970-01-01 08:00 init.sun4i.rc
-rwxr-x--- root root 2230 1970-01-01 08:00 init.sun4i.usb.rc
-rwxr-x--- root root 1637 1970-01-01 08:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 08:00 init.usb.rc
-rwxr-x--- root root 1536000 1970-01-01 08:00 initlogo.rle
drwxrwxr-x root system 2013-01-16 11:22 mnt
-rw-r--r-- root root 782728 1970-01-01 08:00 nand.ko
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwx------ root root 2012-10-11 13:57 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-01-16 11:22 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-16 11:22 sys
drwxr-xr-x root root 2013-01-13 17:59 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 3879 1970-01-01 08:00 ueventd.rc
-rw-r--r-- root root 1313 1970-01-01 08:00 ueventd.sun4i.rc
lrwxrwxrwx root root 2013-01-16 11:22 vendor -> /system/vendor
I think, the only way to launch BT5 in my device successfully is to modify the boot script so that it can suit my device, especially the file structure. But I am a green hand in Linux, I don't know what does some of the codes mean, if you are good at Linux script, would you please give me some advice?
Thank you very much!
I545 ME7 new version has a lock, do not accidentally brush or misuse upgrade, think about tossing a Brush Brush RECOVERY trouble. Is it possible to upgrade will not be downgraded? The answer is definitely no. Well, we want to downgrade, then understand its partition structure is a must. You know, in the end we have to upgrade to upgrade what was a result of being locked!
First, here is the I545 partition table structure:
Code:
lrwxrwxrwx root root 1970-01-01 16:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 16:14 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 16:14 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 16:14 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 16:14 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 16:14 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 16:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 16:14 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 16:14 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 16:14 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 16:14 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 16:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 16:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 16:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 16:14 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 16:14 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 16:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 16:14 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 16:14 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 16:14 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 16:14 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 16:14 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 16:14 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 16:14 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 16:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 16:14 userdata -> /dev/block/mmcblk0p29
Know the partition table, then we have to look at the official ROM ME7 what is inside, at least to know what he upgraded partition was a result of being locked.
The following is the official package ME7 opened with RAR see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see, there are 12 official package file , in fact, there should be 13 years , I feel like I had a SBL1.MBN delete the file, this is an important guiding document , a blank screen will be lost . Connection brush modes anyhow. So we know that under the first bar . BOOT.IMG is the core of the boot files will be lost card first screen . CACHE This is not , MODEM.BIN and NON-HLOS.BIN this is related to the baseband , I brush off alone , it will not be locked , and this has nothing to do , RECOVERY This is a card swipe mode , recovery mode , this is not , RPM is a power management scheme related , SBL2.MBN SBL3.MBN boot record which two are related , SYSTEM this is the system , nor is , TZ is that I do not understand what to do .
**Now the question comes, if not understand, a recovery in the past may have a try. Such high risk factor . Therefore, we even try , but also row a sequence . For example SBL1.MBN, this is the first boot , when this fails if the coverage directly on a black screen , and we try not to move it to this , at least we do not move it, cover the failure modes that can feed wire brush brush the official rescue package bricks ! Of course , this is not relevant to the lock BOOTLOADER .
***535 used all know , 535 is V version, it also has BOOTLOADER lock, then unlock 535 using what methods do, in fact, is replaced by the partition method, which is aboot.mbn replace this partition. In fact, it says so much just thinking, we can be like 535 as a direct replacement overwrite this partition. If not, then only SBL2 SBL3 SBL1 these three , this three risk factor is quite high, and our principle is can not move do not move these three !
Well, just say replace overridden methods !
First of all, we have to use ADB SHELL under the DD command. Then we will obtain ADB SHELL authority , which is first ROOT.
The ROOT method ME7 forum there, I will not say more . I direct that ADB SHELL command .
We go first to Taiwan MDK the machine, put a few partition backup, is SBL1.MBN SBL2.MBN SBL3.MBN and ABOOT.MBN If you are interested , you can put all of the above partition table partition backup under , be prepared to stay with maybe someday that can use ! ~ ~
Backup method is to obtain ROOT , enter ADB SHELL command:
Code:
adb shell
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1.mbn bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl2.mbn bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/sbl3.mbn bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.mbn bs=4096
To explain, dd command to copy the partition related commands, if the meaning can be understood as if it. If there IF = path behind the partition, partition backup to put this on the path of = this, SDCARD this is the path of built-in memory card, you can back up directly to an external memory card, you have to do to change the path down.
Next, we put the backup files are copied to the four external SD card, or copied to a computer backup.
Then again, we took our locked machine, and put the MDK overwrite these partitions ME7 partition. Cover only aboot.mbn oh.
We first connect the phone to the computer, the backup out who's copied to the phone's built-in memory card.
root, I do not say this directly into the adb shell input overrides command:
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/ME7_aboot.mbn bs=4096
dd if=/sdcard/aboot.mbn of=/dev/block/mmcblk0p6 bs=4096
Note that this command following the second IF = OF = position and the position in turn, because it is not backed up, it was restored. The first DD command can not operate, I was customary to put it back down. Be prepared!
Well, I write to you, these commands is very dangerous, and can not be successful looking at you peril Oh, I only provide ideas and does not promise any consequences. Understand their own caution to decide whether to try, do not understand it not tried!
New ideas are always appreciated. Thank you for your efforts!
There are two places to discuss this ...and remember, if you ever try any of this stuff, you do so at your own risk....
see http://forum.xda-developers.com/showthread.php?t=2500826
or
http://forum.xda-developers.com/showthread.php?t=2417713
or possibly here http://forum.xda-developers.com/showthread.php?t=2428226
Assembling system.img for the models on the processor Samsung Snapdragon &Exynos Octa
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
What's needed to build their own ROM images: Preferably installed natively (live, not to Wirth., Machine) operating system based on Linux (UBUNTU, Linux Mint) and always 64 bit version.
Configure the system to use in building firmware:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.8-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind libreadline6-dev gcc-multilib g++-multilib libc6-dev x11proto-core-dev libx11-dev libz-dev gawk texinfo automake libtool cvs libsdl-dev
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ raring partner"
sudo apt-get update
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-jdk7-installer
Code:
sudo apt-get update
sudo apt-get install ia32-libs
Collect firmware:
1. - We will need to complete the assembly binaries Downloading this file
View attachment ext4_utils.zip
On versions of UBUNTU 13.04 and above may experience problems when you use these binaries, the way to solve:
http://forum.xda-developers.com/showpost.php?p=13834882&postcount=1
2. - Unpack the archive in your home directory, which is desirable in any folder you created previously, for example util
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. - Extract to the same folder from the downloaded firmware zip or in other formats, depending on where you get it. Prior to the status of individual images as below:
4. - Go to the folder in the terminal:
Code:
cd utils
We carry out the same in the terminal
Code:
ext4_utils/simg2img ./system.img ./system.raw.img
Code:
mkdir system
Code:
sudo mount -t ext4 -o loop system.raw.img system
Here, the terminal will be prompted to enter your administrator password, enter.
Here's what happened in the folder utils
5. - All our image system.img safely disassembled and placed in a folder for editing system (DO NOT close the terminal after these teams, if something else is needed to perform open another copy of the terminal) Next, go to the folder under administrator privileges (as root) and make the necessary changes. I've been using for these purposes Krusader, it is possible and usual file manager (as root)
For example:
Code:
sudo nautilus
But it more difficult to edit the permissions on files of modified, shorter than an amateur))
6. - After making the changes need to raise the image back to this continuing in the same place at the terminal where they made the disassembly:
Code:
ext4_utils/ext2simg -v system.raw.img system_new.img
Wait for the end of the process, and then:
Code:
ext4_utils/sgs4ext4fs --bloat system_new.img notesystem.img
Wait for the end of the process, and then:
Code:
chmod 0644 notesystem.img
7. - All our way safely assembled and ready after a subsequent packaging tar.md5 for flashing. Before packing firmware tar.md5 change the name of the new image notesystem.img on system.img simple renaming. Everything! Can clean the folder for the following assemblies, and unmount the mounted folder system
Code:
sudo umount system
Automated build process and edit images ---------------------------------- -------------------- ------------ V
View attachment 2431367
Special Thanks
Chainfire
A.S._id
Does this differ for SM-N9005?
Sent from my SM-N9005 using xda app-developers app
danieljamie said:
Does this differ for SM-N9005?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Many of the other image format.
alexyuh said:
Many of the other image format.
Click to expand...
Click to collapse
help image I9505 Android 4.3
Help me the format image system.img.ext4, the working as above way and the result ODIN flash failed
thinh182009 said:
help image I9505 Android 4.3
But flash odin fail
Click to expand...
Click to collapse
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
alexyuh said:
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
Click to expand...
Click to collapse
Thank you for this tutorial. I did successfully I9500 version 4.3. You are asked to do all Note3 are successfully using this method. Thank you very much
Please SP all Qualcomm Snapdragon & Exynos 5 Octa
Thank you very much
Do you want a manual for Qualcomm Snapdragon?
Give me a log of commands from a terminal emulator.
Code:
cat /proc/partitions
and
Code:
cd dev/block/platform/dw_mmc.0/by-name
*************************************************************
or if does not work
*************************************************************
cd dev/block/platform/msm_sdcc.1/by-name
Code:
ls-l
alexyuh said:
Do you want a manual for Qualcomm Snapdragon?
Give me a log of commands from a terminal emulator.
Code:
cat /proc/partitions
and
Code:
cd dev/block/platform/dw_mmc.0/by-name
*************************************************************
or if does not work
*************************************************************
cd dev/block/platform/msm_sdcc.1/by-name
Code:
ls-l
Click to expand...
Click to collapse
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 512000 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p
su-mksh: cd: /dev/block/platform/msm_sdcc.1/by-name/dev/block/platform/msm_sdcc.1/by-name: No such file or directory
2|[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 1970-04-05 13:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-05 13:01 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-05 13:01 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-05 13:01 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-05 13:01 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-05 13:01 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-05 13:01 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-05 13:01 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-05 13:01 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-05 13:01 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-05 13:01 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-05 13:01 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-05 13:01 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-05 13:01 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-05 13:01 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-05 13:01 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-05 13:01 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-05 13:01 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-05 13:01 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-05 13:01 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-05 13:01 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-05 13:01 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-05 13:01 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-05 13:01 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-05 13:01 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-05 13:01 userdata -> /dev/block/mmcblk0p29
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Please Slution. Thanks you very much:good:
---------- Post added at 11:29 AM ---------- Previous post was at 11:01 AM ----------
I was dumb to succeed, but I want you to open and close a tutorial of the original file system
You can collect an image directly on phone.
It will be flash.
Will contain already only regional part of csc. Thus I remade custom rom. For example
http://forum.xda-developers.com/showthread.php?t=2511167
Collected image internal sd to the card. It should be packed into tar.md5
Flashing Odin3
I will write the instruction for the personal computer later.
Okta
su
make_ext4fs -s -l 2436890624B -a system /sdcard/system.img /system
Snap
su
make_ext4fs -s -l 2894069760B -a system /sdcard/system.img.ext4 /system
Sent from my SM-N900 using xda app-developers app
alexyuh said:
You can collect an image directly on phone.
It will be flash.
Will contain already only regional part of csc. Thus I remade custom rom. For example
http://forum.xda-developers.com/showthread.php?t=2511167
Collected image internal sd to the card. It should be packed into tar.md5
Flashing Odin3
I will write the instruction for the personal computer later.
Okta
su
make_ext4fs -s -l 2436890624B -a system /sdcard/system.img /system
Snap
su
make_ext4fs -s -l 2894069760B -a system /sdcard/system.img.ext4 /system
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hi alexyuh! Requirements of thinh182009 want your phone to run guide build Qualcomm Snapdragon chip by means of
which you have given above.
Please guide thinh182009. I trust you to do this Thank you very much.
FAQ
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
To build on Snap:
http://forum.xda-developers.com/showpost.php?p=46906278&postcount=1
In one of the points have been a topic change:
4 -> After unpacking the firmware from zip -> Change the name on system.img.ext system.img, simply renaming the image.
Code:
mv system.img.ext system.img
And mount as indicated:
Code:
ext4_utils/simg2img ./system.img ./system.raw.img
Code:
mkdir system
Code:
sudo mount -t ext4 -o loop system.raw.img system
6-> Assembly:
Code:
sudo ./make_ext4fs -s -l 2894069760B -a system system_new.img system
Code:
sudo chown 1000.1000 system_new.img
Code:
rm -f system.img
Code:
mv system_new.img system.img.ext
Code:
sudo umount system
Code:
rm -r system
Code:
rm *.raw.img
Pack into the firmware tar.md5
To assemble the need to add this folder ext4_utils binary.
View attachment make_ext4fs.zip <-- Unpack the zip of a folder and add ext4_utils
alexyuh said:
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
Click to expand...
Click to collapse
Thanks you very much
very professional:good:
alexyuh said:
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
Click to expand...
Click to collapse
Thank you. You do a very professional.
You can create for me simg2img make_ext4fs adnroid version 4.4_r1 (https://android.googlesource.com/platform/system/extras/).
I really believe you do this. Thank you very much.
[/COLOR]
linhbs said:
Thank you. You do a very professional.
You can create for me simg2img make_ext4fs adnroid version 4.4_r1 (https://android.googlesource.com/platform/system/extras/).
I really believe you do this. Thank you very much.
Click to expand...
Click to collapse
Yes, show for us the master class, and will you make Makefile android-4.4_r1.2 brunch well, or even android-4.3_r2? we are trusting in you...
A.S._id said:
[/COLOR]
Yes, show for us the master class, and will you make Makefile android-4.4_r1.2 brunch well, or even android-4.3_r2? we are trusting in you...
Click to expand...
Click to collapse
Thank you. You can create makefile from https://android.googlesource.com/platform/system/extras/+/refs/heads/master/ext4_utils/ help me.
I want to get Make_ext4fs. If you create make_ext4fs help me. I believe you do this. Thank you very much.
Automated build process and edit images ---------------------------------- -------------------- ------------ V
View attachment 2431377
ext4_utils_4.3
1- Download folder on your computer and unzip
2- Open the folder ext4_utils in the terminal
3- Execute the command
Code:
make
4-Enjoy :laugh:
https://mega.co.nz/#!DwIjyRTY!a9Ega2UnJwDg_E__QV0GVSXqWVUl9IudzdsvNUkTGDU
dell
Hi, i'm Andrea, I'm 19, Computer Engineer's student.
The device is rooted and it has TWRP.
I made a backup of the original ROM (4.4.2) but i don't know how to get boot.img from the phone.
This is the Block Info from MTK Droid Root.
Code:
postimg(.org)/image/hrlwdklq9/ I'm under 10 post, so i can't post links
I tried with adb shell:
Code:
adb shell
[email protected]:/ # ls -l /dev/block/platform/
ls -l /dev/block/platform/
drwxr-xr-x root root 2010-01-04 10:09 mtk-msdc.0
[email protected]:/ # ls -l /dev/block/platform/mtk-msdc.0/by-num
ls -l /dev/block/platform/mtk-msdc.0/by-num
lrwxrwxrwx root root 2010-01-04 10:09 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2010-01-04 10:09 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2010-01-04 10:09 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2010-01-04 10:09 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2010-01-04 10:09 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2010-01-04 10:09 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2010-01-04 10:09 p7 -> /dev/block/mmcblk0p7
Now, which is the boot.img?
Hi everybody,
I would like to unlock the bootloader of a Wiko Y80 to install a custom ROM.
On the Internet, there are many pages where there is the same guide (written in different ways) for unlocking the bootloader using 'fastboot'.
The problem is that 'fastboot' does not work because:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
By chance, does anyone know if there is another way for unlocking the bootloader or, even better, to flash a ROM like LineageOS 17.x GSI?
I would like to have some news from guys who really made/tried it successfully.
Thanks,
Roberto
Unfortunately, same for me on my Wiko Y80.
I tried the following with no success (https://www.droidwin.com/fix-failed-remote-unknown-command-error/):
enable USB debuging (phone's GUI)
enable OEM unlocking (phone's GUI)
disable screen lock, PIN and so on (phone's GUI)
reinstall USB drivers (r13 windows)
get the latest ADB (30.0.5)
Although, driver seems to work mostly as I can get in `adb shell`, list `adb devices` or `fastboot devices`... I can even get the `fastboot --help` which suggests me to use `fastboot oem unlock` (seriously?). But when it's time to unlock oem/flashing, I get FAILED message.
I didn't succeed to install wiko's drivers for the deveice (neither for normal nore fastboot mode).
Well, I don't know what to try now to unlock this and install lienageOS...
Run
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
to see whether unlocking the booloader is denied by OEM/carrier or not.
If 1 is returned then it should be possible to unlock the bootloader, otherwise not.
Well, not sure whether "no return" means anything... I expected an integer a char at least...
I first wondered I needed to be in the shell to see the result but it doesn't make any difference.
Do you confirm this absence of 1 meens the end of the game, or am I in another edgy case of this device?
Code:
E:\Logiciels\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
JAD82024004528 device
E:\Logiciels\platform-tools>adb shell "getprop ro.oem_unlock_supported"
E:\Logiciels\platform-tools>adb shell
W-V720:/ $ getprop ro.oem_unlock_supported
W-V720:/ $
Code:
E:\Logiciels\platform-tools>adb shell
W-V720:/ $ getprop ro.oem_unlock_supported
W-V720:/ $ echo $?
0
W-V720:/ $
I think it's an official no...
You queried ( $? ) command's exit code, not output of getprop command. Exit code 0 indicates that executing the command was successful, nothing else.
Run
Code:
cat /system/build.prop /default.prop | grep 'ro.oem_unlock_supported=' | dd bs=1 skip=24 count=1
to get the value of property in question.
It seems like I must be root to get these values (as many others, like a simple ls)...
Code:
1|W-V720:/ $ ls -al
ls: ./init: Permission denied
ls: ./ueventd.rc: Permission denied
ls: ./init.zygote32.rc: Permission denied
ls: ./init.rc: Permission denied
ls: ./init.zygote64_32.rc: Permission denied
ls: ./init.usb.configfs.rc: Permission denied
ls: ./init.usb.rc: Permission denied
ls: ./init.recovery.v720.rc: Permission denied
ls: ./init.environ.rc: Permission denied
ls: ./productinfo: Permission denied
total 72
drwxr-xr-x 19 root root 4096 2008-12-31 17:00 .
drwxr-xr-x 19 root root 4096 2008-12-31 17:00 ..
dr-xr-xr-x 78 root root 0 2020-01-03 17:03 acct
lrw-r--r-- 1 root root 11 2008-12-31 17:00 bin -> /system/bin
lrw-r--r-- 1 root root 50 2008-12-31 17:00 bugreports -> /data/user_de/
0/com.android.shell/files/bugreports
drwxrwx--- 7 system cache 4096 2021-01-06 15:28 cache
lrw-r--r-- 1 root root 13 2008-12-31 17:00 charger -> /sbin/charger
drwxr-xr-x 4 root root 0 1970-01-01 01:00 config
lrw-r--r-- 1 root root 17 2008-12-31 17:00 d -> /sys/kernel/debug
drwxrwx--x 40 system system 4096 2021-01-06 15:28 data
lrw------- 1 root root 23 2008-12-31 17:00 default.prop -> system/etc/p
rop.default
drwxr-xr-x 17 root root 3480 2020-01-03 17:03 dev
lrw-r--r-- 1 root root 11 2008-12-31 17:00 etc -> /system/etc
drwx------ 2 root root 16384 2008-12-31 17:00 lost+found
drwxr-xr-x 11 root system 260 2020-01-03 17:03 mnt
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 odm
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 oem
dr-xr-xr-x 375 root root 0 1970-01-01 01:00 proc
drwxr-xr-x 9 root root 4096 2008-12-31 17:00 product
drwxr-x--- 2 root shell 4096 2008-12-31 17:00 sbin
lrw-r--r-- 1 root root 21 2008-12-31 17:00 sdcard -> /storage/self/prim
ary
drwxr-xr-x 5 root root 120 2020-01-03 17:03 storage
dr-xr-xr-x 12 root root 0 2020-01-03 17:03 sys
drwxr-xr-x 15 root root 4096 2008-12-31 17:00 system
drwxr-xr-x 13 root root 4096 2008-12-31 17:00 vendor
1|W-V720:/ $ cat /system/build.prop /default.prop | grep 'ro.oem_unlock_supported=' | dd bs=1 skip=24 count=1
cat: /system/build.prop: Permission denied
cat: /default.prop: Permission denied
dd: skip reached end of input
1|W-V720:/ $
Any clue..?
Wiko support replied to "help" on this , but I guess they didn't realy get the point and avoid the real question :
To do so you would need open source files to apply this changes but they aren't available for this device at the moment. We can't help you further at the moment but this demand has been transfered to the proper service.
Click to expand...
Click to collapse
It seems they blame the lack of lineage/TWRP support but they don't answer the question : how to unlock OEM, enabling us to flash something else.
Has anyone got this working yet??
Really looking to get Lineage installed on this..
Bump, any success?
posenato said:
Hi everybody,
I would like to unlock the bootloader of a Wiko Y80 to install a custom ROM.
On the Internet, there are many pages where there is the same guide (written in different ways) for unlocking the bootloader using 'fastboot'.
The problem is that 'fastboot' does not work because:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
By chance, does anyone know if there is another way for unlocking the bootloader or, even better, to flash a ROM like LineageOS 17.x GSI?
I would like to have some news from guys who really made/tried it successfully.
Thanks,
Roberto
Click to expand...
Click to collapse
wiko uses the default key so if you follow the identifier token tutorial on hovatek you should be able to unlock bl
already unlocked my wiko y51 with no problems