WARNING!!!
This binary files are for UNIX system, with amd64 architecture ONLY!!!
This morning, I'm little bit confuse to execute adb binary file which given by zeppelinrox in Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH.zip file. After check this binary file, I realize that this file is 32bit binary.
Code:
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# ls -lahrt .
total 6.4M
-rwxr-xr-x 1 root root 17K Nov 11 1999 tee.exe
-rwxr-xr-x 1 root root 16K Nov 11 1999 sleep.exe
-rwxr-xr-x 1 root root 26K Jun 20 2003 tr.exe
-rwxr-xr-x 1 root root 191K Jul 30 2003 awk.exe
-rwxr-xr-x 1 root root 133K Oct 23 2003 grep.exe
-rwxr-xr-x 1 root root 93K Oct 25 2003 sed.exe
-rwxr-xr-x 1 root root 3.2M Sep 25 2007 sh.exe
-rwxr-xr-x 1 root root 284K Jul 12 2008 zip.exe
-rwxr-xr-x 1 root root 5.4K Aug 1 2008 dexopt-wrapper
-rwxr-xr-x 1 root root 200K Apr 20 2009 unzip.exe
-rwxr-xr-x 1 root root 342K Nov 19 2011 adb-mac
-rwxr-xr-x 1 root root 333K Nov 19 2011 adb
-rwxr-xr-x 1 root root 60K Jul 15 2012 AdbWinUsbApi.dll
-rwxr-xr-x 1 root root 94K Jul 15 2012 AdbWinApi.dll
-rwxr-xr-x 1 root root 187K Jul 15 2012 adb.exe
-rwxr-xr-x 1 root root 528K Dec 16 12:46 baksmali.jar
-rwxr-xr-x 1 root root 622K Dec 16 12:46 smali.jar
-rwxr-xr-x 1 root root 20K Dec 25 15:20 ultimatic_jar_patcher_adb.bat
-rwxr-xr-x 1 root root 17K Dec 25 15:20 ultimatic_jar_patcher_adb.sh
-rwxr-xr-x 1 root root 26K Dec 25 22:31 ALL_ROMS_Ultimate_Jar_Power_Tools-Smali_Patcher_RC9.sh
drwxr-xr-x 4 root root 4.0K Mar 28 10:21 ..
drwxr-xr-x 2 root root 4.0K Mar 28 10:21 .
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# file adb
adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
And I'm using amd64 bit architecture
Code:
[email protected]:~# uname -a
Linux kali 3.7-trunk-amd64 #1 SMP Debian 3.7.2-0+kali5 x86_64 GNU/Linux
If you try execute adb binary which given by zeppelinrox, you will got this error message:
Code:
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# ./adb
bash: ./adb: No such file or directory
In order to execute this 32bit binary file, yo have to install ia32-libs on your system with this command:
Code:
[email protected]:~# apt-get install ia32-libs
But it will give you some errors like these:
Code:
[email protected]:~# apt-get install ia32-libs
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
ia32-libs : Depends: lib32bz2-1.0 but it is not going to be installed
Depends: lib32asound2 (> 1.0.18) but it is not going to be installed
Depends: lib32gcc1 (>= 1:4.1.1) but it is not going to be installed
Depends: lib32ncurses5 (>= 5.7+20100313) but it is not going to be installed
Depends: lib32stdc++6 (>= 4.1.1) but it is not going to be installed
Depends: lib32v4l-0 (>= 0.5.0) but it is not going to be installed
Depends: lib32z1 (>= 1:1.2.3.3.dfsg) but it is not going to be installed
PreDepends: libc6-i386 (>= 2.9-18) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Desperate with this condition, I decide to compile adb and fastboot using amd64 architecture. So you can use adb and fastboot with your amd64 architecture. Give a try!
Here is some output that these binary files are based from amd64 architecture:
Code:
[email protected]:/tmp/adb_and_fastboot# ls -lahrt .
total 368K
-rwxr-xr-x 1 root root 91K Mar 28 11:37 fastboot
-rwxr-xr-x 1 root root 153K Mar 28 11:40 adb
-rw-r--r-- 1 root root 111K Mar 28 11:41 adb_and_fastboot.zip
drwxr-xr-x 2 root root 4.0K Mar 28 11:41 .
drwxrwxrwt 12 root root 4.0K Mar 28 11:52 ..
[email protected]:/tmp/adb_and_fastboot# file adb
adb: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x2bd948a70efb09cc8604f9903dd6f617686fa707, stripped
[email protected]:/tmp/adb_and_fastboot# file fastboot
fastboot: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0xaaf735fdf5123bb446cea17c45e42bef3017c1d5, stripped
Note:
After extract these files, move them to /usr/bin directory, or /bin/ directory using this command
Code:
[email protected]:~# mv adb /bin/adb && mv fastboot /bin/fastboot
If you are about using Ultimatic Jar Patcher Tools, just overwrite original adb (which based from i386) with your adb (which based from amd64):
Code:
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# ls -lahrt .
total 6.4M
-rwxr-xr-x 1 root root 17K Nov 11 1999 tee.exe
-rwxr-xr-x 1 root root 16K Nov 11 1999 sleep.exe
-rwxr-xr-x 1 root root 26K Jun 20 2003 tr.exe
-rwxr-xr-x 1 root root 191K Jul 30 2003 awk.exe
-rwxr-xr-x 1 root root 133K Oct 23 2003 grep.exe
-rwxr-xr-x 1 root root 93K Oct 25 2003 sed.exe
-rwxr-xr-x 1 root root 3.2M Sep 25 2007 sh.exe
-rwxr-xr-x 1 root root 284K Jul 12 2008 zip.exe
-rwxr-xr-x 1 root root 5.4K Aug 1 2008 dexopt-wrapper
-rwxr-xr-x 1 root root 200K Apr 20 2009 unzip.exe
-rwxr-xr-x 1 root root 342K Nov 19 2011 adb-mac
-rwxr-xr-x 1 root root 333K Nov 19 2011 adb
-rwxr-xr-x 1 root root 60K Jul 15 2012 AdbWinUsbApi.dll
-rwxr-xr-x 1 root root 94K Jul 15 2012 AdbWinApi.dll
-rwxr-xr-x 1 root root 187K Jul 15 2012 adb.exe
-rwxr-xr-x 1 root root 528K Dec 16 12:46 baksmali.jar
-rwxr-xr-x 1 root root 622K Dec 16 12:46 smali.jar
-rwxr-xr-x 1 root root 20K Dec 25 15:20 ultimatic_jar_patcher_adb.bat
-rwxr-xr-x 1 root root 17K Dec 25 15:20 ultimatic_jar_patcher_adb.sh
-rwxr-xr-x 1 root root 26K Dec 25 22:31 ALL_ROMS_Ultimate_Jar_Power_Tools-Smali_Patcher_RC9.sh
drwxr-xr-x 4 root root 4.0K Mar 28 10:21 ..
drwxr-xr-x 2 root root 4.0K Mar 28 10:21 .
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# file adb
adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# cp -fv $(which adb) adb
`/usr/bin/adb' -> `adb'
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# file adb
adb: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x2bd948a70efb09cc8604f9903dd6f617686fa707, stripped
Any question? I hope this will help you.
Qucker Fix for adb & fastboot on Linux amd64
This fixed it for me without the hassel. After you have followed a regular install of adb or whatever binary you are trying to use. Then:
dpkg --add-architecture i386
apt-get update
apt-get install ia32-libs
apt-get install libncurses5:i386
reboot
//edit- Running Kali - Linux amd 64 gnome Version 3.4.2 just by the way.
maylonious said:
This fixed it for me without the hassel. After you have followed a regular install of adb or whatever binary you are trying to use. Then:
dpkg --add-architecture i386
apt-get update
apt-get install ia32-libs
apt-get install libncurses5:i386
reboot
//edit- Running Kali - Linux amd 64 gnome Version 3.4.2 just by the way.
Click to expand...
Click to collapse
Yeah, this is happened (breaking dependencies) if you didn't include mirror on your source.list at the end of Kali Linux Installation. Anyway, just running some command like this
Code:
[email protected]:~# echo "deb http://http.kali.org/kali kali main non-free contrib" > /etc/apt/source.list
[email protected]:~# echo "deb-src http://http.kali.org/kali kali main non-free contrib" >> /etc/apt/source.list
[email protected]:~# echo "deb http://security.kali.org/kali-security kali/updates main contrib non-free" >> /etc/apt/source.list
[email protected]:~# dpkg --add-architecture i386
[email protected]:~# apt-get update
[email protected]:~# apt-get install ia32-libs
Should fix the problem. I made this thread for them who stuck on breaking dependencies. :highfive:
The adb and fastboot executables are not working on android 6.0.1.
I copied them to /bin and then tried to execute.
Each gives the following error:
Code:
sush: //bin/adb: not executable: 64-bit ELF file
(with fastboot adb is replaced in the error with fastboot)
I've read about it here and i think it could be fixed with giving the compiler a parameter to use android's linker instead of libld.so. The guys seen in the forum i linked passed this option to linker, these made the executable work:
Code:
--dynamic-linker=/system/bin/linker
And this to FPC:
Code:
-k--dynamic-linker=/system/bin/linker
I would be glad if you could do that, because i can't find any adb and fastboot (arm) executables to run in my phone, only shady executables which maybe stole my whole life.
Related
I am trying to use HTC Desire's openvpn to connect to dd-wrt router with a static key, the following is the config file used:
remote xxx.xxx.xxx
port 2008
dev tap
secret static.key
proto udp
comp-lzo
route-gateway 192.168.1.1
redirect-gateway
I used openvpn setting 0.4.7. the openvpn told me it's connected but when I tried to connect the sites blocked by my carrier, I still cannot open it (I can bypass carrier's blocking if I use PC for the same setting). Anyone advice? Btw, I've use the DNS fix in 0.4.7 and changed dns to 8.8.8.8
redirect-gateway doesn't work for me 2
try to check routing table after connect
if find answer pls share
appears that route is not working, still pointing to my local router ip address 192.168.0.1, my remote router should be 192.168.1.1
any advice?
The following are the commands I executed from terminal and results I got!
cd sdcard/openvpn
openvpn --config abc.ovpn
------------
Thu Jan 6 01:14:04 2011 OpenVPN 2.1.1 i686-pc-linux-gnu [SSL] [LZO2] [EPOLL] built on Jul 26 2010
Thu Jan 6 01:14:04 2011 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Thu Jan 6 01:14:04 2011 WARNING: file 'static.key' is group or others accessible
Thu Jan 6 01:14:04 2011 LZO compression initialized
Thu Jan 6 01:14:05 2011 TUN/TAP device tap0 opened
RTNETLINK answers: No such process
Thu Jan 6 01:14:05 2011 ERROR: Linux route add command failed: external program exited with error status: 2
Thu Jan 6 01:14:05 2011 UDPv4 link local (bound): [undef]:2008
Thu Jan 6 01:14:05 2011 UDPv4 link remote: xxx.xxx.xxx.xxx:2008
Thu Jan 6 01:14:32 2011 Peer Connection Initiated with xxx.xxx.xxx.xxx:2008
Thu Jan 6 01:14:32 2011 Initialization Sequence Completed
Does it mean that I don't have tun/tap file installed? How can I find the file? I am using ReflexTSense Rom 1.5.1
anyone can help on this?
cnwatch said:
anyone can help on this?
Click to expand...
Click to collapse
if you installed busybox under /system/xbin, you need to create /system/xbin/bb directory and symlink the ifconfig and route command there:
note: if your desire is not S-OFF you need to do this in recovery
Code:
mkdir /system/xbin/bb
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
ln -s /system/xbin/busybox /system/xbin/bb/route
then reinstall openvpn and tell the installation your binaries are under /system/xbin/bb (the default).
Also, make sure to flag the "Fix HTC Routes" in the Advanced options of OpenVPN Settings.
moebius83 said:
if you installed busybox under /system/xbin, you need to create /system/xbin/bb directory and symlink the ifconfig and route command there:
note: if your desire is not S-OFF you need to do this in recovery
Code:
mkdir /system/xbin/bb
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
ln -s /system/xbin/busybox /system/xbin/bb/route
then reinstall openvpn and tell the installation your binaries are under /system/xbin/bb (the default).
Also, make sure to flag the "Fix HTC Routes" in the Advanced options of OpenVPN Settings.
Click to expand...
Click to collapse
booted into recovery and add the ln -s /system/xbin/busybox /system/xbin/bb/ifconfig as route is already linked.
then I tried to reinstall the openvpn installer but it says failed and deletes the openvpn file and I have to recover from nandroid backup. pls advise, also, can you share the settings for openvpn settings, my settings as follows:
Tun modules settings
- Load module using : insmod
- path to un module: /system/lib/modules/tun.ko
Path to configurations: /sdcard/openvpn
Path to openvpn binary: /system/xbin/openvpn
Fix HTC Router: Enabled
cnwatch said:
booted into recovery and add the ln -s /system/xbin/busybox /system/xbin/bb/ifconfig as route is already linked.
then I tried to reinstall the openvpn installer but it says failed and deletes the openvpn file and I have to recover from nandroid backup. pls advise, also, can you share the settings for openvpn settings, my settings as follows:
Tun modules settings
- Load module using : insmod
- path to un module: /system/lib/modules/tun.ko
Path to configurations: /sdcard/openvpn
Path to openvpn binary: /system/xbin/openvpn
Fix HTC Router: Enabled
Click to expand...
Click to collapse
same identical config, I'm using stock froyo htc rom
Hello,
Is is possible to use dd command available under busybox when in recovery mode
to backup partitions?
Examples:
Backup data partition:
dd if=/dev/block/mmcblk0p26 of=/sdcard/data.img
Restore data partition:
dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
If yes, then what the needed mount commands to make the above work.
The reason is that I have a problem with nandroid restore:
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
Note: similar command apparently works for flashing recovery
image (which is partition /dev/block/mmcblk0p21).
Without appropriate answer, I have to try for myself, and finally get the answer to my own question.
The answer is YES, dd command could be used to backup/restore the entire system (so can replace
nandroid part of ClockWorkMod).
You need to know the mapping of the partitions for the Desire HD:
Code:
/dev/block/mmcblk0p21 recovery
/dev/block/mmcblk0p22 boot
/dev/block/mmcblk0p25 system
/dev/block/mmcblk0p26 data
/dev/block/mmcblk0p27 cache
The partitions backupped will result in same size each time, with same backup/restore time
since it is a "raw" backup (bit-to-bit copy, or sector-by-sector copy in hard disk terminology).
I use the .dsk for file extension to avoid confusion with .img extension used by CWM (since they
are not the same format, and cannot be used in fastboot command for example).
Backup sample log:
Code:
ls -l /sdcard/MyBackups/recovery/recovery*.dsk
-rwxrwxrwx 1 root root 8909824 Jun 16 10:17 /sdcard/MyBackups/recovery/recovery_3.0.2.8.dsk
2011-06-17-02:26:24 Backup boot...
512+0 records in
512+0 records out
4194304 bytes (4.0MB) copied, 0.208129 seconds, 19.2MB/s
-rwxrwxrwx 1 root root 4194304 Jun 17 02:26 /sdcard/MyBackups/LeeDroid_Froyo/boot.dsk
2011-06-17-02:26:24 Backup system...
71423+1 records in
71423+1 records out
585104896 bytes (558.0MB) copied, 188.697998 seconds, 3.0MB/s
-rwxrwxrwx 1 root root 585104896 Jun 17 02:29 /sdcard/MyBackups/LeeDroid_Froyo/system.dsk
2011-06-17-02:29:33 Backup data...
150399+1 records in
150399+1 records out
1232076288 bytes (1.1GB) copied, 370.469513 seconds, 3.2MB/s
-rwxrwxrwx 1 root root 1232076288 Jun 17 02:35 /sdcard/MyBackups/LeeDroid_Froyo/data.dsk
2011-06-17-02:35:43 Backup cache...
38399+1 records in
38399+1 records out
314572288 bytes (300.0MB) copied, 97.289337 seconds, 3.1MB/s
-rwxrwxrwx 1 root root 314572288 Jun 17 02:37 /sdcard/MyBackups/LeeDroid_Froyo/cache.dsk
2011-06-17-02:37:21 Done.
Restore sample code:
Code:
ls -l /sdcard/MyBackups/recovery/recovery*.dsk
-rwxrwxrwx 1 root root 8909824 Jun 16 10:17 /sdcard/MyBackups/recovery/recovery_3.0.2.8.dsk
2011-06-17-15:28:33 Restore boot...
-rwxrwxrwx 1 root root 4194304 Jun 17 14:58 /sdcard/MyBackups/LeeDroid_Froyo/boot.dsk
512+0 records in
512+0 records out
4194304 bytes (4.0MB) copied, 1.006897 seconds, 4.0MB/s
2011-06-17-15:28:34 Restore system...
-rwxrwxrwx 1 root root 585104896 Jun 17 15:02 /sdcard/MyBackups/LeeDroid_Froyo/system.dsk
71423+1 records in
71423+1 records out
585104896 bytes (558.0MB) copied, 405.526398 seconds, 1.4MB/s
2011-06-17-15:35:20 Restore data...
-rwxrwxrwx 1 root root 1232076288 Jun 17 15:08 /sdcard/MyBackups/LeeDroid_Froyo/data.dsk
150399+1 records in
150399+1 records out
1232076288 bytes (1.1GB) copied, 434.877655 seconds, 2.7MB/s
2011-06-17-15:42:34 Restore cache...
-rwxrwxrwx 1 root root 314572288 Jun 17 15:09 /sdcard/MyBackups/LeeDroid_Froyo/cache.dsk
38399+1 records in
38399+1 records out
314568704 bytes (300.0MB) copied, 49.197021 seconds, 6.1MB/s
2011-06-17-15:43:24 Done.
Now with "dd" backup, I can now have the liberty to try other ROMs without my dreaded problem with CWM .
Edit: let have a dream. How about using dd binary like nandroid currently invoked by CWM from it's menu?
CWM currently for backup or restore invoke the standalone nandroid binary with appropriate parameters, then it captures
(pipes) the output of e.g. tar utility to extract (restore) or compress (backup) the .img file.
With dd it would be simple to add to CWM menu to provide invocation of dd for a backup/restore using partition imaging method.
By doing this, no more need to plug an USB cable and use adb command.
Edit: Finally there is a simpler solution. Create an installation ZIP script (like the one used to flash ROM). Then in updater_script invoke a command (shell script, extension.sh) with the run_program(). You can provide parameters to this. You can have a zip to backup, a zip to restore etc...
Good idea. I've tried this on my U8510 (Android 2.3.3) but it doesn't work. This is my partition layout:
cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0ba00000 00020000 "system"
mtd5: 03f00000 00020000 "cache"
mtd6: 0a0a0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
mtd8: 01400000 00020000 "cust"
Click to expand...
Click to collapse
And this is "ls -l /dev/block":
brw------- 1 root root 7, 0 Oct 12 21:54 loop0
brw------- 1 root root 7, 1 Oct 12 21:54 loop1
brw------- 1 root root 7, 2 Oct 12 21:54 loop2
brw------- 1 root root 7, 3 Oct 12 21:54 loop3
brw------- 1 root root 7, 4 Oct 12 21:54 loop4
brw------- 1 root root 7, 5 Oct 12 21:54 loop5
brw------- 1 root root 7, 6 Oct 12 21:54 loop6
brw------- 1 root root 7, 7 Oct 12 21:54 loop7
brw------- 1 root root 179, 0 Oct 12 21:54 mmcblk0
brw------- 1 root root 179, 1 Oct 12 21:54 mmcblk0p1
brw------- 1 root root 31, 0 Oct 12 21:54 mtdblock0
brw------- 1 root root 31, 1 Oct 12 21:54 mtdblock1
brw------- 1 root root 31, 2 Oct 12 21:54 mtdblock2
brw------- 1 root root 31, 3 Oct 12 21:54 mtdblock3
brw------- 1 root root 31, 4 Oct 12 21:54 mtdblock4
brw------- 1 root root 31, 5 Oct 12 21:54 mtdblock5
brw------- 1 root root 31, 6 Oct 12 21:54 mtdblock6
brw------- 1 root root 31, 7 Oct 12 21:54 mtdblock7
brw------- 1 root root 31, 8 Oct 12 21:54 mtdblock8
drwxr-xr-x 3 root root 60 Oct 12 21:54 platform
brw------- 1 root root 1, 0 Oct 12 21:54 ram0
brw------- 1 root root 1, 1 Oct 12 21:54 ram1
brw------- 1 root root 1, 2 Oct 12 21:54 ram2
brw------- 1 root root 1, 3 Oct 12 21:54 ram3
brw------- 1 root root 1, 4 Oct 12 21:54 ram4
brw------- 1 root root 1, 5 Oct 12 21:54 ram5
brw------- 1 root root 1, 6 Oct 12 21:54 ram6
brw------- 1 root root 1, 7 Oct 12 21:54 ram7
Click to expand...
Click to collapse
'mmcblk0' is the sdcard.
When i enter 'dd if=/dev/block/mtdblock0 of=/sdcard/mtdblock0-boot.img' i get:
dd: /dev/block/mtdblock0: I/O error
Click to expand...
Click to collapse
CWM Recovery Backup gives me this files. I'm not sure if this are all files so i want to dump partitions manually.
.android_secure.img
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
Click to expand...
Click to collapse
Why is it not working?
Edit: When i enter 'dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img' dd does work but it copies the sdcard to itself.
Why are the other "blocks" not working and how can i get the working ones like your 'mmcblk0p21'?
Edit2: Got it. For the U8510 its 'dd if=/dev/mtd/mtd0 of=/sdcard/mtd0-boot.img bs=4096'.
busybox dd
dnlilas said:
Hello,
Is dd if=/dev/block/mmcblk0p26 of=/sdcard/data.imgis possible to use dd command available under busybox when in recovery mode
to backup partitions?
Examples:
Backup data partition:
dd if=/dev/block/mmcblk0p26 of=/sdcard/data.img
Restore data partition:
dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
If yes, then what the needed mount commands to make the above work.
The reason is that I have a problem with nandroid restore:
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
Note: similar command apparently works for flashing recovery
image (which is partition /dev/block/mmcblk0p21).
Click to expand...
Click to collapse
Hi, I'm interested in using dd command to do a full backup but I don't know how to do.
Where I have to write the command "dd if=/dev/block/mmcblk0 of=/sdcard/data.img"?
In busybox?
Thanks in advance!
Hello,
You need to connect the phone to your PC with USB cable then reboot the phone in recovery. In your PC, start the adb.exe command, you should get a command prompt with root right (# instead of $). Then you can use commands in this prompt.
busybox dd without a pc
dnlilas said:
Hello,
You need to connect the phone to your PC with USB cable then reboot the phone in recovery. In your PC, start the adb.exe command, you should get a command prompt with root right (# instead of $). Then you can use commands in this prompt.
Click to expand...
Click to collapse
Thanks but I've read (http://forum.xda-developers.com/showthread.php?t=1124939) that is possible to use the command "dd" within the smartphone obtaining a full backup in the sdcard.
I've to use a terminal emulator in android, after installing busybox, to launch the command "dd if=/dev/block/mmcblk0 of=/sdcard/data.img"?
Thanks in advance!
OK, so you will need a rooted phone, then in terminal emulator, change to root with su command to get the root # prompt.
But the difference is that you may take a backup of a live (running) system : this may work (as some live online nandroid backup), but of course the safest/surest is to take a backup when the system is shutdown, as in recovery.
Also, to restore, of course you are required to use the recovery, you cannot restore from inside Android with dd.
busybox dd from inside Android
dnlilas said:
OK, so you will need a rooted phone, then in terminal emulator, change to root with su command to get the root # prompt.
But the difference is that you may take a backup of a live (running) system : this may work (as some live online nandroid backup), but of course the safest/surest is to take a backup when the system is shutdown, as in recovery.
Also, to restore, of course you are required to use the recovery, you cannot restore from inside Android with dd.
Click to expand...
Click to collapse
Thanks very much, now I've understand! :victory:
This guide (http://forum.xda-developers.com/showthread.php?t=1818321) says how to do a full backup via pc with the command dd but I don't understand if the phone is in recovery mode!?
Can you tell me if the guide is ok for you? because it says something different from what you have said in your first replay .
To to backup the phone must be powered-on.
But I would suggest you to use this application that will do all the backup for you from inside your running/live Android :
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Great app for full backup
dnlilas said:
To to backup the phone must be powered-on.
But I would suggest you to use this application that will do all the backup for you from inside your running/live Android :
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Click to expand...
Click to collapse
Thanks, great app for a complete backup of the phone!
Just to learn something new: to do a backup with pc and dd command, the phone must be in recovery mode and then connected to the pc?
It is ok for you the guide that I linked in the previous reply?
You said, in your first replay, to use adb.exe: can you explain the procedure (like a small guide) or link a guide (if you know one web page that speaks about it)?
Thanks again!
From what I know :
adb.exe is part of the Android developer toolkit (ADK) that you can download. In fact for plain user (not Android developer), we only need the following 3 files that are usually available in many tools for customed ROM :
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
You would better download the ADK so you will get the latest version. When you connect the phone either in recovery mode with an USB cable to the PC, the PC has (at least under Win7/Win8) automatically Android adb device driver installed, so it recognizes the phone correctly. By launching adb.exe, you will get to an adb command prompt where you can issue several commands like reboot, restart to recovery, flash the partition etc.... (communication is established between adb.exe in PC and the phone ) You can also issue the su command as far as I remember, then you the the "Linux"-like shell prompt. And dd, ls, du, cat commands of busybox etc... are then all available. You exit the shell by 'exit'.
Searching for adb, fastboot etc.. would help you.
Hope this helps,
i'm confused by the code in this message.
it shows a `ls` command but the output of a `dd` one...
has anybody actually tried to write the live system partition this way? has his phone survived?
Is it correct to flash the data.img(user data image) by fastboot with this command:
fastboot flash userdata data.img
??
gcbxda said:
i'm confused by the code in this message.
it shows a `ls` command but the output of a `dd` one...
Click to expand...
Click to collapse
Agreed. I was looking on a way to restore a complete mmcblk0 raw backup to the device, but the restore sample code given is just the `ls -l` command.
i get a whole host of errors when trying to install a sense rom with odexed apps deodexed framework.
i can restore a nandroid of same rom but after running thru kitchen this happens?
anybody no why?
09:35:18.602 Warning PackageManager 350 Unknown permission android.permission.WRITE_SECURE_SETTINGS in package com.htc.android.htcime
09:35:18.602 Warning PackageManager 350 Unknown permission android.permission.GET_ACCOUNTS in package com.htc.android.htcime
09:35:18.602 Warning PackageManager 350 Unknown permission android.permission.RECORD_AUDIO in package com.htc.android.htcime
09:35:18.603 Warning PackageManager 350 Unknown permission android.permission.READ_SMS in package com.android.providers.htcmessage
09:35:18.603 Warning PackageManager 350 Unknown permission android.permission.WRITE_SMS in package com.android.providers.htcmessage
09:35:18.604 Warning PackageManager 350 Unknown permission android.permission.RECEIVE_BOOT_COMPLETED in package com.android.providers.downloads
09:35:18.604 Warning PackageManager 350 Unknown permission android.permission.ACCESS_CACHE_FILESYSTEM in package com.android.providers.downloads
this list goes on
Not sure if its the same permissions, but from ADB in recovery, before boot (and after flash) what happenf if you mount /data then chmod 777 /data/data/com.android.x.x?
Then reboot?
cheers dan whats the last bit android.x.x
also if this worked could i nandroid it run it thru kitchen again and install ok next time, or would u need to run chmod every time?
basically all the package names in your logcat.
IF it does work (i'm not sure if its the permissions of the package or that whats in the package cannot get the permissions) then yes a nandroid is a snap shot so all permissions would be stored.
It may be the actual apks and odex files in system/app that need permissions altering. i really dont know for sure, im guessing.
ok cheers dan, im not sure how im gunna set permisions on apks and odex when i cant get past boot loop be different if i had fc,s
adb via recovery, like i said
chmod777 on apks aswell?
weird apprently no such file as system/app!!
Code:
mount /system
chmod 777 /system/app/application1.apk
etc. Obviously there is no application1.apk, you just put the name of the apk or the odex file (case sensitive) there instead.
Not sure what file isn't in system app that you're talking about?
not just file the whole of system app!
technically it would be /system/app (sorry about that).
In adb
Code:
mount /system
cd /system
ls -lh
this is what i got
cd /system
/system # ls -lh
ls -lh
drwxr-xr-x 1 root root 2.0K Nov 8 11:28 app
drwxr-xr-x 1 root shell 2.0K Nov 8 11:29 bin
-rw-r--r-- 1 root root 8.6K Aug 1 2008 build.pr
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 customiz
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 etc
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 fonts
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 framewor
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 lib
drwxr-xr-x 1 root root 2.0K Nov 8 11:28 lost+fou
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 media
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 sd
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 usr
drwxr-xr-x 1 root shell 2.0K Nov 8 11:29 xbin
dan281082 said:
drwxr-xr-x 1 root root 2.0K Nov 8 11:28 app
Click to expand...
Click to collapse
Well thats the /system/app folder and permission there is normal.
Now:
Code:
cd
cd /system/app
ls -lh
just a snap shot
-rw-r--r-- 1 root root 81.7K Aug 1 2008 AccountSyncManager.apk
-rw-r--r-- 1 root root 62.3K Aug 1 2008 AccountSyncManager.odex
-rw-r--r-- 1 root root 144.3K Aug 1 2008 AppSharing.apk
-rw-r--r-- 1 root root 46.9K Aug 1 2008 AppSharing.odex
-rw-r--r-- 1 root root 11.0K Aug 1 2008 ApplicationsProvider.apk
-rw-r--r-- 1 root root 22.4K Aug 1 2008 ApplicationsProvider.odex
-rw-r--r-- 1 root root 3.9K Aug 1 2008 BRCMBluetoothServices.apk
-rw-r--r-- 1 root root 8.8K Aug 1 2008 BRCMBluetoothServices.ode
x
-rw-r--r-- 1 root root 178.7K Aug 1 2008 Bluetooth.apk
-rw-r--r-- 1 root root 218.0K Aug 1 2008 Bluetooth.odex
-rw-r--r-- 1 root root 494.5K Aug 1 2008 Calendar.apk
-rw-r--r-- 1 root root 729.8K Aug 1 2008 Calendar.odex
-rw-r--r-- 1 root root 31.9K Aug 1 2008 CalendarProvider.apk
-rw-r--r-- 1 root root 951.3K Aug 1 2008 CalendarProvider.odex
-rw-r--r-- 1 root root 20.9K Aug 1 2008 CertInstaller.apk
-rw-r--r-- 1 root root 38.8K Aug 1 2008 CertInstaller.odex
-rw-r--r-- 1 root root 3.5K Aug 1 2008 CheckinProvider.apk
-rw-r--r-- 1 root root 102.7K Aug 1 2008 CheckinProvider.odex
-rw-r--r-- 1 root root 15.8K Aug 1 2008 ContactsProvider.apk
-rw-r--r-- 1 root root 680.4K Aug 1 2008 ContactsProvider.odex
-rw-r--r-- 1 root root 6.5K Aug 1 2008 CustomizationSettingsProv
ider.apk
-rw-r--r-- 1 root root 8.1K Aug 1 2008 CustomizationSettingsProv
ider.odex
-rw-r--r-- 1 root root 35.2K Aug 1 2008 CustomizationSetup.apk
-rw-r--r-- 1 root root 115.1K Aug 1 2008 CustomizationSetup.odex
-rw-r--r-- 1 root root 3.0K Aug 1 2008 DCSImpl.apk
-rw-r--r-- 1 root root 23.1K Aug 1 2008 DCSImpl.odex
-rw-r--r-- 1 root root 3.2K Aug 1 2008 DCSUtility.apk
-rw-r--r-- 1 root root 27.3K Aug 1 2008 DCSUtility.odex
-rw-r--r-- 1 root root 6.2K Aug 1 2008 DebugTool.apk
-rw-r--r-- 1 root root 19.6K Aug 1 2008 DebugTool.odex
-rw-r--r-- 1 root root 4.0K Aug 1 2008 DefaultContainerService.a
pk
-rw-r--r-- 1 root root 16.3K Aug 1 2008 DefaultContainerService.o
dex
-rw-r--r-- 1 root root 31.4K Aug 1 2008 DownloadProvider.apk
-rw-r--r-- 1 root root 877.0K Aug 1 2008 DownloadProvider.odex
-rw-r--r-- 1 root root 31.9K Aug 1 2008 DownloadProviderUi.apk
-rw-r--r-- 1 root root 39.3K Aug 1 2008 DownloadProviderUi.odex
-rw-r--r-- 1 root root 7.0K Aug 1 2008 DrmProvider.apk
-rw-r--r-- 1 root root 59.3K Aug 1 2008 DrmProvider.odex
-rw-r--r-- 1 root root 7.3K Aug 1 2008 FilePicker.apk
-rw-r--r-- 1 root root 4.0K Aug 1 2008 FilePicker.odex
-rw-r--r-- 1 root root 62.5K Aug 1 2008 GSD.apk
-rw-r--r-- 1 root root 101.0K Aug 1 2008 GSD.odex
-rw-r--r-- 1 root root 749.2K Aug 1 2008 Gmail.apk
-rw-r--r-- 1 root root 2.2M Aug 1 2008 Gmail.odex
-rw-r--r-- 1 root root 14.2K Aug 1 2008 GoogleCalendarSyncAdapter
.apk
-rw-r--r-- 1 root root 251.9K Aug 1 2008 GoogleCalendarSyncAdapter
.odex
-rw-r--r-- 1 root root 12.1K Aug 1 2008 GoogleContactsSyncAdapter
.apk
-rw-r--r-- 1 root root 295.7K Aug 1 2008 GoogleContactsSyncAdapter
.odex
-rw-r--r-- 1 root root 34.1K Aug 1 2008 GoogleFeedback.apk
-rw-r--r-- 1 root root 85.3K Aug 1 2008 GoogleFeedback.odex
-rw-r--r-- 1 root root 4.3K Aug 1 2008 GooglePartnerSetup.apk
-rw-r--r-- 1 root root 128.0K Aug 1 2008 GooglePartnerSetup.odex
-rw-r--r-- 1 root root 347.0K Aug 1 2008 GoogleQuickSearchBox.apk
-rw-r--r-- 1 root root 454.3K Aug 1 2008 GoogleQuickSearchBox.odex
-rw-r--r-- 1 root root 501.2K Aug 1 2008 GoogleServicesFramework.a
pk
-rw-r--r-- 1 root root 1.2M Aug 1 2008 GoogleServicesFramework.o
dex
-rw-r--r-- 1 root root 296.5K Aug 1 2008 HTCAlbum.apk
-rw-r--r-- 1 root root 1.3M Aug 1 2008 HTCAlbum.odex
-rw-r--r-- 1 root root 307.4K Aug 1 2008 HTCCamera.apk
-rw-r--r-- 1 root root 656.9K Aug 1 2008 HTCCamera.odex
-rw-r--r-- 1 root root 1.0M Aug 1 2008 HTCSetupWizard.apk
-rw-r--r-- 1 root root 203.6K Aug 1 2008 HTCSetupWizard.odex
-rw-r--r-- 1 root root 7.2M Aug 1 2008 HTC_IME.apk
-rw-r--r-- 1 root root 1.1M Aug 1 2008 HTC_IME.odex
-rw-r--r-- 1 root root 5.5K Aug 1 2008 HTMLViewer.apk
-rw-r--r-- 1 root root 8.3K Aug 1 2008 HTMLViewer.odex
-rw-r--r-- 1 root root 37.6K Aug 1 2008 HtcAddProgramWidget.apk
-rw-r--r-- 1 root root 99.8K Aug 1 2008 HtcAddProgramWidget.odex
-rw-r--r-- 1 root root 10.5K Aug 1 2008 HtcCdmaMccProvider.apk
-rw-r--r-- 1 root root 17.0K Aug 1 2008 HtcCdmaMccProvider.odex
-rw-r--r-- 1 root root 945.3K Aug 1 2008 HtcClockWidget.apk
-rw-r--r-- 1 root root 284.2K Aug 1 2008 HtcClockWidget.odex
-rw-r--r-- 1 root root 813.4K Aug 1 2008 HtcContacts.apk
-rw-r--r-- 1 root root 1.8M Aug 1 2008 HtcContacts.odex
-rw-r--r-- 1 root root 543.4K Aug 1 2008 HtcDialer.apk
-rw-r--r-- 1 root root 604.0K Aug 1 2008 HtcDialer.odex
-rw-r--r-- 1 root root 66.8K Aug 1 2008 HtcLocationPicker.apk
-rw-r--r-- 1 root root 84.5K Aug 1 2008 HtcLocationPicker.odex
-rw-r--r-- 1 root root 37.2K Aug 1 2008 HtcLocationService.apk
seem to be all there
should be rw-r--r-- (chmod 644) so not sure where you first and extra - is from, but also looks correct beyond there.
You cd then chmod 644 -R /system/app/* to be sure.
So cd to /data/data and do again please.
so im cd /system/app
chmod 644 -r/system/app/
then cd /data/data then?
dan281082 said:
so im cd /system/app
chmod 644 -r/system/app/
then cd /data/data then?
Click to expand...
Click to collapse
Code:
cd
chmod 644 -R /system/app/*
cd
mount /data
cd /data/data
ls -lh
By the way this is all case sensitive so ensure -R is capital. Also there is a space after -R
EDIT>
FYI, /data/data content should be rwxr-x--x which if it is not, is a chmod 751
latest error
cd
~ # chmod 644 -R /system/app/*
chmod 644 -R /system/app/*
chmod: /system/app/*: No such file or directory
Are you sure it is typed correctly, definitely? I can even do this on a terminal emulator on my phone itself
as /system still mounted?
EDIT> if it is still mounted and still getting that error, try mounting like below:
Code:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
ok managed the system chmod. propbable being dumbo!!
cant seem to cd /data/data now but did earlier and permisions were how u said
Code:
cd
mount /data
chmod 777 /data/data
chmod 777 -R /data/data/*
Just for good measure (some of the contents of /data/data have higher permissions levels. This will be extreme but should add full permissions to everything.
As everybody knows, Motorola and most of other android phones have locked the bootloader,
so repacking boot.img will not boot.
I see the init.xxx.rc files are modified in Cyanogenmod series ROMS, but I checked they
did not repacked boot.img( files are not from boot.img)
can somebody tell me how did they do that?
I am making a programm that works like bootmenu but I don't want replace logwrapper, I wish
I could add an exec command in the rc file
well, I saw there's 2nd-init. answered by myself..
~ # ls -l /init.rc
ls -l /init.rc
-rw-r--r-- 1 root root 17507 Dec 14 14:26 /init.rc
~ # ls -l /system/bootmenu/2nd-init/init.rc
ls -l /system/bootmenu/2nd-init/init.rc
-rw-r--r-- 1 root root 17507 Aug 1 2008 /system/bootmenu/2nd-init/init.rc
~ #
========
seems I can't make easier than the way bootmenu does..
This really do not know，but deliberately over the top with your Google Translation。。。
SOLVED!
While I was S-OFF, I was not Bootloader Unlocked...
HUGE thanks to Andybones and santod040!!
Solution a few posts down.
--ORIGINAL POST--
I cannot obtain Root on my Marshmallow 6.0 Verizon HTC One M9 phone (HTC6535LVW) . I have tried all the methods, and have flashed all the ROMs.
I have gone through the steps of upgrading to Android 6.0 both manually, and letting OTA do it from the oldest RUU I could find.
Here is some minor info...
Code:
hTC download mode
*** LOCKED ***
htc_himawl PVT S-OFF
CID-11111111
LK-1.0.0.0000
[email protected]
OpenDSP-15.6.1.00522.8994_1026
OS-3.37.605.7
Jan 28 2016,20:52:56(669662)
The recovery.log seems to spit out errors every time it flashes SuperSU which leads me to believe it is an issue with SuperSU, but I cannot for the life of me figure out why...
Here is the outline of my entire process from start to finish, including a suggestion from a forum member in the beginning.
Code:
C:\adb>md5sum 3.37.605.7_FULL_firmware.zip
0285e23f98c44aebe9150f1e2c33a3b4 *3.37.605.7_FULL_firmware.zip
C:\adb>md5sum 3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_DEODEX.zip
6164c613d0fe7eb09fe111944848bc80 *3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_DEO
DEX.zip
C:\adb>md5sum 3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_ODEX.zip
250a94e294a0fc0f10f9b4abf3e456e5 *3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_ODE
X.zip
C:\adb>md5sum 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
2979ebc4e8b64a7b8fc24e99e6f5a2fb *3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
C:\adb>md5sum 3.37.605.7_Stock_BootImg.zip
3272dcc7aee5b38dc335a6cdaf076417 *3.37.605.7_Stock_BootImg.zip
Those are the MD5sums of all the files. They match with what is provided on android file host.
Next, I flashed the Full firmware and booted to the stock recovery and did a wipe.
Code:
C:\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 16(ms)
C:\adb>htc_fastboot flash zip 3.37.605.7_FULL_firmware.zip
sending 'zip'... (74990 KB) OKAY
sending time = 4.796 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
For "hboot-preupdate" response, restart the same procedure for device HT54DSV054
60...
< waiting for device >
sending 'zip'... (74990 KB) OKAY
sending time = 4.826 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
Flash Zip Complete
Execution time is 15(s)
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 3(ms)
Following that, I rebooted to download mode again, and flashed the NoBoot firmware with TWRP.
Code:
C:\adb>htc_fastboot flash zip 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
< waiting for device >
sending 'zip'... (65327 KB) OKAY
sending time = 4.306 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
For "hboot-preupdate" response, restart the same procedure for device HT54DSV054
60...
< waiting for device >
sending 'zip'... (65327 KB) OKAY
sending time = 4.335 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
Flash Zip Complete
Execution time is 17(s)
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 3(ms)
C:\adb>
I booted into Recovery and wiped my SD Card out. Then I copied up the DEODEX'ed ROM 3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_DEODEX.zip to the SD Card. The MD5 is below...
Code:
C:\adb>adb shell md5sum /external_sd/3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_
DEODEX.zip
6164c613d0fe7eb09fe111944848bc80 /external_sd/3.37.605.7_HIMA_WL_M60_SENSE70_VZ
W_MR_Full_DEODEX.zip
I then installed the zip using TWRP. I pulled the /tmp/recovery.log file before rebooting to the System. I was not asked to install SU by TWRP, and there for did not allow TWRP to install Root or SU for me.
Recovery.log file is below...
Code:
ui_print
3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full.zip Successfully Installed!
script succeeded: result was [3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full.zip Successfully Installed!]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 388MB, free: 22144MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
...done
I:Set page: 'flash_done'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:operation_end - status=0
There was not a lot of information in this log file when installing only the ROM.
Next I rebooted into the system, this boot process took a long time (as expected for first boots). I went through the setup of the phone and made sure NOT to RESTORE any old settings or apps. I did not want any old data coming back to haunt me. I checked in my App Drawer for SuperSU and did not see it. I installed Root Checker from the App store and it told me I did not have root.
I decided to try flashing the SuperSU 2.65 zip file manually and seeing if that would give me root. I rebooted to recovery and started the flash process.
I downloaded SuperSU from this thread http://forum.xda-developers.com/showthread.php?t=1538053 and this link https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
SuperSU did not provide an md5sum, so all I can compare it to is the local to the phone ->
Code:
C:\adb>md5sum UPDATE-SuperSU-v2.65-20151226141550.zip
419d48a14d8ae9f247cd9266e14ad8cf *UPDATE-SuperSU-v2.65-20151226141550.zip
C:\adb>adb shell md5sum /external_sd/UPDATE-SuperSU-v2.65-20151226141550.zip
419d48a14d8ae9f247cd9266e14ad8cf /external_sd/UPDATE-SuperSU-v2.65-201512261415
50.zip
C:\adb>
---CONTINUING---
I then installed the SuperSU Zip and pulled the /tmp/recovery.log
--Added as attachment to this post--
I hit Reboot System button and it rebooted right to the System. It did not ask me to install Root or SU
Again I used Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) and was informed I do not have Root.
This is where I sit, with Marshmallow 6.0 Stock and no root method available.
This is my folder structure after the SuperSU.zip tried to install root (Captured using adb while booted into recovery)
Root Structure
Code:
drwxr-xr-x 2 root root 0 Feb 29 04:22 boot
drwxrwx--- 5 system cache 4096 Feb 29 04:14 cache
drwxrwxrwx 2 root root 0 Feb 29 04:22 carrier
lrwxrwxrwx 1 root root 13 Jan 1 1970 charger -> /sbin/healthd
drwxrwxrwx 2 root root 0 Feb 29 04:22 cota
drwxrwx--x 37 system system 4096 Feb 29 04:15 data
-rw-r--r-- 1 root root 3013 Jan 1 1970 default.prop
drwxr-xr-x 11 root root 4340 Feb 29 04:22 dev
drwxrwxrwx 2 root root 0 Feb 29 04:22 devlog
drwxr-xr-x 2 root root 0 Feb 29 04:22 etc
drwxrwxrwx 5 root root 16384 Jan 1 1970 external_sd
-rw-r--r-- 1 root root 14727 Jan 1 1970 file_contexts
-rw-r----- 1 root root 1041 Jan 1 1970 fstab.qcom
-rwxr-x--- 1 root root 1150888 Jan 1 1970 init
-rwxr-x--- 1 root root 2844 Jan 1 1970 init.rc
-rwxr-x--- 1 root root 4061 Jan 1 1970 init.recovery.htc_hima.rc
drwxr-xr-x 3 root root 0 Jan 1 1970 license
drwxr-xr-x 2 root root 0 Jan 1 1970 oem
drwxrwxrwx 2 root root 0 Feb 29 04:22 preload
dr-xr-xr-x 323 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 3350 Jan 1 1970 property_contexts
drwxr-xr-x 2 root root 0 Feb 29 04:22 recovery
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Feb 16 20:51 root
drwxr-x--- 2 root root 0 Feb 29 04:22 sbin
drwxrwxrwx 2 root root 0 Feb 29 04:22 sd-ext
drwxrwx--- 15 media_rw media_rw 4096 Feb 29 04:13 sdcard
-rw-r--r-- 1 root root 703 Jan 1 1970 seapp_contexts
-rw-r--r-- 1 root root 63 Jan 1 1970 selinux_version
-rw-r--r-- 1 root root 143489 Jan 1 1970 sepolicy
-rw-r--r-- 1 root root 9769 Jan 1 1970 service_contexts
drwxr-xr-x 2 root root 0 Feb 29 04:22 sideload
drwxr-xr-x 2 root root 0 Jan 1 1970 supersu
dr-xr-xr-x 25 root root 0 Feb 29 04:22 sys
drwxr-xr-x 5 root root 0 Jan 1 1970 system
drwxrwxr-x 2 root shell 60 Feb 29 04:22 tmp
drwxr-xr-x 5 root root 0 Jan 1 1970 twres
-rw-r--r-- 1 root root 10948 Jan 1 1970 ueventd.qcom.rc
-rw-r--r-- 1 root root 4726 Jan 1 1970 ueventd.rc
drwxrwxrwx 2 root root 0 Feb 29 04:22 usb_otg
drwxr-xr-x 4 root root 0 Jan 1 1970 vendor
/system
Code:
drwxr-xr-x 102 root root 4096 Feb 29 03:33 app
drwxr-xr-x 3 root shell 12288 Feb 29 03:34 bin
-rw-r--r-- 1 root root 13791 Aug 1 2008 build.prop
drwxr-xr-x 8 root root 4096 Feb 29 03:33 customize
drwxr-xr-x 3 root root 4096 Feb 29 03:33 embms
drwxr-xr-x 21 root shell 4096 Feb 29 03:33 etc
drwxr-xr-x 2 root root 12288 Feb 29 03:34 fonts
drwxr-xr-x 3 root root 4096 Feb 29 03:33 framework
drwxr-xr-x 8 root root 20480 Feb 29 03:34 lib
drwxr-xr-x 6 root root 20480 Feb 29 03:34 lib64
drwxr-xr-x 2 root root 16384 Feb 29 03:33 lost+found
drwxr-xr-x 6 root root 4096 Feb 29 03:33 media
drwxr-xr-x 143 root root 4096 Feb 29 03:34 priv-app
drwxr-xr-x 5 root root 4096 Feb 29 03:34 rfs
drwxr-xr-x 3 root root 4096 Feb 29 03:34 tts
drwxr-xr-x 10 root root 4096 Feb 29 03:34 usr
drwxr-xr-x 10 root shell 4096 Feb 29 03:34 vendor
drwxr-xr-x 2 root shell 12288 Feb 29 03:34 xbin
/data
Code:
-rw------- 1 system system 6117378 Feb 29 04:14 SuperSU.apk
drwx------ 2 root root 4096 Feb 29 03:37 adb
drwxrwxr-x 2 system system 4096 Feb 29 03:50 anr
drwxrwx--x 13 system system 4096 Feb 29 04:12 app
drwx------ 2 root root 4096 Feb 29 03:37 app-asec
drwxrwx--x 2 system system 4096 Feb 29 03:37 app-lib
drwxrwx--x 2 system system 4096 Feb 29 03:37 app-private
drwxrwx--- 3 media audio 4096 Feb 29 03:37 audio
drwx------ 5 system system 4096 Feb 29 04:11 backup
drwxr-xr-x 2 shell shell 4096 Feb 29 03:37 bootchart
lrwxrwxrwx 1 root root 45 Feb 29 03:37 bugreports -> /data/data/com.android.shell/files/bugreports
drwxrwx--x 2 system system 4096 Feb 29 03:37 connectivity
drwxrwxrwx 2 system system 4096 Feb 29 03:37 core
drwxrwx--x 5 root root 4096 Feb 29 03:37 dalvik-cache
drwxrwx--x 257 system system 12288 Feb 29 04:11 data
drwxrwx--x 4 system system 4096 Feb 29 03:37 dpm
drwxrwx--- 4 drm drm 4096 Feb 29 03:50 drm
-rw-rw---- 1 system audio 0 Feb 29 04:18 effect_endpoint_update
drwxrwx--x 2 system system 4096 Feb 29 03:37 fota
drwxrwx--- 2 system system 4096 Feb 29 03:37 fpc
drwxrwx--- 2 system wifi 4096 Feb 29 03:37 hostapd
drwxr-x--x 3 root root 4096 Feb 29 03:37 local
drwxrwx--- 2 root root 4096 Jan 1 1970 lost+found
drwxrwx--- 4 media_rw media_rw 4096 Feb 29 03:37 media
drwxrwx--- 3 mediadrm mediadrm 4096 Feb 29 03:53 mediadrm
drwxrwx--t 33 system misc 4096 Feb 29 03:52 misc
drwxrwx--- 3 nfc nfc 4096 Feb 29 03:57 nfc
drwx------ 2 root root 4096 Feb 29 04:19 property
drwxrwx--x 2 system system 4096 Feb 29 03:37 resource-cache
drwx--x--x 2 system system 4096 Feb 29 03:37 security
drwxr-xr-x 2 system system 4096 Feb 29 03:37 shared
drwx------ 2 system system 4096 Feb 29 03:37 ss
-rw------- 1 root root 12525041 Feb 29 04:15 stock_boot_de7d99827c496cadeb26cc0fdb7c50ee7c87aeb6.img.gz
-rw-r--r-- 1 root root 33554432 Feb 29 04:15 su.img
drwxrwxr-x 19 system system 4096 Feb 29 04:19 system
drwx------ 2 system system 4096 Feb 29 03:51 time
drwxrwx--x 6 system system 4096 Feb 29 03:37 tombstones
drwx--x--x 2 system system 4096 Feb 29 03:37 user
drwx------ 2 system system 4096 Feb 29 03:43 usf
drwxrwxr-x 2 wifi wifi 4096 Feb 29 03:37 wifi_log
/data/app
Code:
drwxr-xr-x 4 system system 4096 Feb 29 03:49 air.com.goodgamestudios.empirefourkingdoms-1
drwxr-xr-x 4 system system 4096 Feb 29 04:08 air.com.sgn.cookiejam.gp-2
drwxr-xr-x 4 system system 4096 Feb 29 04:11 com.android.vending-1
drwxr-xr-x 4 system system 4096 Feb 29 04:10 com.joeykrim.rootcheck-1
drwxr-xr-x 4 system system 4096 Feb 29 04:10 com.king.farmheroessaga-2
drwxr-xr-x 4 system system 4096 Feb 29 03:50 com.machinezone.gow-1
drwxr-xr-x 4 system system 4096 Feb 29 04:05 com.moonton.magicrush-2
drwxr-xr-x 4 system system 4096 Feb 29 04:09 com.sgn.geniesandgems.gp-2
drwxr-xr-x 4 system system 4096 Feb 29 03:49 com.usablenet.mobile.walgreen-1
drwxr-xr-x 4 system system 4096 Feb 29 04:04 com.verizonmedia.go90.enterprise-2
drwxrwxr-x 3 system system 4096 Feb 29 03:37 mcRegistry
---CONTINUING---
/system/bin
Code:
-rwxr-xr-x 1 root shell 43432 Aug 1 2008 ATFWD-daemon
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 MOC_ecryptfs_add_passphrase
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 MOC_umount_ecryptfs
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 PktRspTest
-rwxr-xr-x 1 root shell 38576 Aug 1 2008 StoreKeybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 acpi -> toybox
-rwxr-xr-x 1 root shell 10192 Aug 1 2008 adsprpcd
-rwxr-xr-x 1 root shell 210 Aug 1 2008 am
lrwxrwxrwx 1 root root 13 Feb 29 03:34 app_process -> app_process64
-rwxr-xr-x 1 root shell 22108 Aug 1 2008 app_process32
-rwxr-xr-x 1 root shell 22456 Aug 1 2008 app_process64
-rwxr-xr-x 1 root shell 70608 Aug 1 2008 applypatch
-rwxr-xr-x 1 root shell 213 Aug 1 2008 appops
-rwxr-xr-x 1 root shell 215 Aug 1 2008 appwidget
-rwxr-xr-x 1 root shell 30840 Aug 1 2008 atrace
-rwxr-xr-x 1 root shell 26552 Aug 1 2008 audiod
-rwxr-xr-x 1 root shell 38492 Aug 1 2008 awb_camera
lrwxrwxrwx 1 root root 6 Feb 29 03:34 basename -> toybox
-rwxr-xr-x 1 root shell 51152 Aug 1 2008 bcc
-rwxr-xr-x 1 root shell 14224 Aug 1 2008 blkid
lrwxrwxrwx 1 root root 6 Feb 29 03:34 blockdev -> toybox
-rwxr-x--- 1 root system 26480 Aug 1 2008 bma150_usr
-rwxr-xr-x 1 root shell 199 Aug 1 2008 bmgr
-rwxr-xr-x 1 root shell 59328 Aug 1 2008 bootanimation
-rwxr-xr-x 1 root shell 34752 Aug 1 2008 brctl
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 btfmtest
-rwxr-xr-x 1 root shell 156 Aug 1 2008 bu
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 bugreport
lrwxrwxrwx 1 root root 6 Feb 29 03:34 bzcat -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cal -> toybox
-rwxr-xr-x 1 root shell 39224 Aug 1 2008 cand
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cat -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chcon -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chgrp -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chmod -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chown -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chroot -> toybox
-rwxr-xr-x 1 root shell 47160 Aug 1 2008 cir_fw_update
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cksum -> toybox
-rwxr-xr-x 1 root shell 59584 Aug 1 2008 clatd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 clear -> toybox
-rwxr-xr-x 1 root shell 145168 Aug 1 2008 climax_hostSW
-rwxr-xr-x 1 root shell 120792 Aug 1 2008 clockd
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 closediag
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 closemodem
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cmp -> toybox
-rwxr-xr-x 1 root shell 22552 Aug 1 2008 cnd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 comm -> toybox
-rwxr-xr-x 1 root shell 207 Aug 1 2008 content
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cp -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cpio -> toybox
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 cplay
-rwxr-xr-x 1 root shell 464984 Aug 1 2008 curl
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cut -> toybox
lrwxrwxrwx 1 root root 10 Feb 29 03:34 dalvikvm -> dalvikvm64
-rwxr-xr-x 1 root shell 17912 Aug 1 2008 dalvikvm32
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 dalvikvm64
lrwxrwxrwx 1 root root 6 Feb 29 03:34 date -> toybox
-rwxr-xr-x 1 root shell 4572 Aug 1 2008 dbg_corefile.sh
lrwxrwxrwx 1 root root 7 Feb 29 03:34 dd -> toolbox
-rwxr-xr-x 1 root shell 42540 Aug 1 2008 debuggerd
-rwxr-xr-x 1 root shell 47056 Aug 1 2008 debuggerd64
-rwxr-xr-x 1 root shell 112172 Aug 1 2008 dex2oat
lrwxrwxrwx 1 root root 7 Feb 29 03:34 df -> toolbox
-rwxr-xr-x 1 root shell 112736 Aug 1 2008 dhcpcd
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 diag_callback_client
-rwxr-xr-x 1 root shell 22456 Aug 1 2008 diag_dci_sample
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 diag_klog
-rwxr-xr-x 1 root shell 23352 Aug 1 2008 diag_mdlog
-rwxr-xr-x 1 root shell 18480 Aug 1 2008 diag_qshrink4_daemon
-rwxr-xr-x 1 root shell 26896 Aug 1 2008 diag_socket_log
-rwxr-xr-x 1 root shell 14600 Aug 1 2008 diag_uart_log
lrwxrwxrwx 1 root root 6 Feb 29 03:34 dirname -> toybox
-rwxr-xr-x 1 root shell 170280 Aug 1 2008 dmagent
lrwxrwxrwx 1 root root 6 Feb 29 03:34 dmesg -> toybox
-rwxr-xr-x 1 root shell 169040 Aug 1 2008 dnsmasq
lrwxrwxrwx 1 root root 6 Feb 29 03:34 dos2unix -> toybox
-rwxr-xr-x 1 root shell 133240 Aug 1 2008 downloadcs
-rwxr-xr-x 1 root shell 137280 Aug 1 2008 downloadsensorhub
-rwxr-xr-x 1 root shell 133240 Aug 1 2008 downloadtp
-rwxr-xr-x 1 root shell 156 Aug 1 2008 dpm
-rwxr-xr-x 1 root shell 22472 Aug 1 2008 dpmd
-rwxr-xr-x 1 root shell 63096 Aug 1 2008 drmserver
lrwxrwxrwx 1 root root 7 Feb 29 03:34 du -> toolbox
-rwxr-xr-x 1 root shell 54888 Aug 1 2008 dual_camera
-rwxr-xr-x 1 root shell 34352 Aug 1 2008 dualcal_camera
-rwxr-xr-x 1 root shell 67544 Aug 1 2008 dumpstate
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 dumpsys
-rwxr-xr-x 1 root shell 212912 Aug 1 2008 e2fsck
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 ebtables
lrwxrwxrwx 1 root root 6 Feb 29 03:34 echo -> toybox
lrwxrwxrwx 1 root root 4 Feb 29 03:34 egrep -> grep
-rwxr-xr-x 1 root shell 19000 Aug 1 2008 energy-awareness
lrwxrwxrwx 1 root root 6 Feb 29 03:34 env -> toybox
-rwxr-xr-x 1 root shell 333416 Aug 1 2008 exfatck
-rwxr-xr-x 1 root shell 263784 Aug 1 2008 exfatdebug
-rwxr-xr-x 1 root shell 276072 Aug 1 2008 exfatinfo
-rwxr-xr-x 1 root shell 251496 Aug 1 2008 exfatlabel
lrwxrwxrwx 1 root root 6 Feb 29 03:34 expand -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 expr -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 fallocate -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 false -> toybox
lrwxrwxrwx 1 root root 4 Feb 29 03:34 fgrep -> grep
lrwxrwxrwx 1 root root 6 Feb 29 03:34 find -> toybox
-rwxr-xr-x 1 root shell 38840 Aug 1 2008 fingerprintd
-rwxr-xr-x 1 root shell 71272 Aug 1 2008 flash_camera
-rwxr-xr-x 1 root shell 35504 Aug 1 2008 fm_qsoc_patches
-rwxr-xr-x 1 root shell 18368 Aug 1 2008 fmconfig
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 fmfactorytest
-rwxr-xr-x 1 root shell 26480 Aug 1 2008 fmfactorytestserver
lrwxrwxrwx 1 root root 6 Feb 29 03:34 free -> toybox
-rwxr-xr-x 1 root shell 67512 Aug 1 2008 fsck.f2fs
-rwxr-xr-x 1 root shell 34672 Aug 1 2008 fsck_msdos
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 ftm_powertest
-rwxr-xr-x 1 root shell 55248 Aug 1 2008 gatekeeperd
-rwxr-xr-x 1 root shell 397672 Aug 1 2008 gdbserver
lrwxrwxrwx 1 root root 6 Feb 29 03:34 getenforce -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 getevent -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 getprop -> toybox
-rwxr-xr-x 1 root shell 36288 Aug 1 2008 grep
lrwxrwxrwx 1 root root 6 Feb 29 03:34 groups -> toybox
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 gzip
-rwxr-xr-x 1 root shell 17960 Aug 1 2008 hcheck-v2
lrwxrwxrwx 1 root root 6 Feb 29 03:34 head -> toybox
-rwxr-xr-x 1 root shell 213 Aug 1 2008 hid
-rwxr-xr-x 1 root shell 252120 Aug 1 2008 hld
-rwxr-xr-x 1 root shell 593288 Aug 1 2008 hostapd
-rwxr-xr-x 1 root shell 47056 Aug 1 2008 hostapd_cli
lrwxrwxrwx 1 root root 6 Feb 29 03:34 hostname -> toybox
-rwxr-xr-x 1 root shell 260776 Aug 1 2008 htc_ebdlogd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 hwclock -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 id -> toybox
-rwxr-xr-x 1 root shell 34752 Aug 1 2008 idmap
lrwxrwxrwx 1 root root 6 Feb 29 03:34 ifconfig -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 iftop -> toolbox
-rwxr-xr-x 1 root shell 194 Aug 1 2008 ime
-rwxr-xr-x 1 root shell 67616 Aug 1 2008 ims_rtp_daemon
-rwxr-xr-x 1 root shell 6096 Aug 1 2008 imscmservice
-rwxr-xr-x 1 root shell 165936 Aug 1 2008 imsdatadaemon
-rwxr-xr-x 1 root shell 120784 Aug 1 2008 imsqmidaemon
lrwxrwxrwx 1 root root 6 Feb 29 03:34 inotifyd -> toybox
-rwxr-xr-x 1 root shell 203 Aug 1 2008 input
lrwxrwxrwx 1 root root 6 Feb 29 03:34 insmod -> toybox
-rwxr-xr-x 1 root shell 96752 Aug 1 2008 installd
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ioctl -> toolbox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ionice -> toolbox
-rwxr-xr-x 1 root shell 223552 Aug 1 2008 ip
-rwxr-xr-x 1 root shell 398520 Aug 1 2008 ip6tables
-rwxr-xr-x 1 root shell 485344 Aug 1 2008 ipacm
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 ipacm-diag
-rwxr-x--- 1 root system 390016 Aug 1 2008 iptables
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 irsc_util
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 keypress
-rwxr-xr-x 1 root shell 133296 Aug 1 2008 keystore
lrwxrwxrwx 1 root root 6 Feb 29 03:34 kill -> toybox
-rwxr-xr-x 1 root shell 866768 Aug 1 2008 ld.mc
-rwxr-xr-x 1 root shell 177612 Aug 1 2008 linker
-rwxr-xr-x 1 root shell 270144 Aug 1 2008 linker64
-rwxr-xr-x 1 root shell 18296 Aug 1 2008 lmkd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 ln -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 load_policy -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 log -> toolbox
-rwxr-xr-x 1 root shell 26488 Aug 1 2008 logcat
-rwxr-xr-x 1 root shell 79808 Aug 1 2008 logd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 logname -> toybox
-rwxr-xr-x 1 root shell 18320 Aug 1 2008 logwrapper
lrwxrwxrwx 1 root root 6 Feb 29 03:34 losetup -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ls -> toolbox
-rwxr-xr-x 1 root shell 148320 Aug 1 2008 lsc_camera
lrwxrwxrwx 1 root root 6 Feb 29 03:34 lsmod -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 lsof -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 lsusb -> toybox
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 make_ext4fs
-rwxr-xr-x 1 root shell 26712 Aug 1 2008 make_f2fs
-rwxr-xr-x 1 root shell 145336 Aug 1 2008 mcDriverDaemon
-rwxr-xr-x 1 root shell 6088 Aug 1 2008 mcStarter
lrwxrwxrwx 1 root root 6 Feb 29 03:34 md5sum -> toybox
-rwxr-xr-x 1 root shell 653648 Aug 1 2008 mdnsd
-rwxr-xr-x 1 root shell 210 Aug 1 2008 media
-rwxr-xr-x 1 root shell 26204 Aug 1 2008 mediaserver
-rwxr-xr-x 1 root shell 120944 Aug 1 2008 memlock
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mkdir -> toybox
-rwxr-xr-x 1 root shell 284264 Aug 1 2008 mkexfat
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mknod -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mkswap -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mktemp -> toybox
-rwxr-xr-x 1 root shell 87732 Aug 1 2008 mm-qcamera-app
-rwxr-xr-x 1 root shell 22108 Aug 1 2008 mm-qcamera-daemon
-rwxr-xr-x 1 root shell 26152 Aug 1 2008 mm-qjpeg-dec-test
-rwxr-xr-x 1 root shell 26152 Aug 1 2008 mm-qjpeg-enc-test
-rwxr-xr-x 1 root shell 34344 Aug 1 2008 mm-qomx-idec-test
-rwxr-xr-x 1 root shell 38440 Aug 1 2008 mm-qomx-ienc-test
-rwxr-xr-x 1 root shell 445352 Aug 1 2008 mm-vidc-omx-test
-rwxr-xr-x 1 root shell 419 Aug 1 2008 mobicore-startup.sh
lrwxrwxrwx 1 root root 6 Feb 29 03:34 modinfo -> toybox
-rwxr-xr-x 1 root shell 217 Aug 1 2008 monkey
lrwxrwxrwx 1 root root 6 Feb 29 03:34 more -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 mount -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mountpoint -> toybox
-rwxr-xr-x 1 root shell 75432 Aug 1 2008 msm-vidc-test
-rwxr-xr-x 1 root shell 30584 Aug 1 2008 msm_irqbalance
-rwxr-xr-x 1 root shell 26672 Aug 1 2008 mtpd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mv -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 nandread -> toolbox
-rwxr-xr-x 1 root shell 10112 Aug 1 2008 ndc
-rwxr-xr-x 1 root shell 236128 Aug 1 2008 netd
-rwxr-xr-x 1 root shell 439080 Aug 1 2008 netmgrd
-rwxr-xr-x 1 root shell 42960 Aug 1 2008 netsharing
lrwxrwxrwx 1 root root 6 Feb 29 03:34 netstat -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 newfs_msdos -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 nice -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 nl -> toybox
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 nl_listener
lrwxrwxrwx 1 root root 6 Feb 29 03:34 nohup -> toybox
-rwxr-xr-x 1 root shell 215040 Aug 1 2008 oatdump
lrwxrwxrwx 1 root root 6 Feb 29 03:34 od -> toybox
-rwxr-xr-x 1 root shell 34424 Aug 1 2008 oemwvtest
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 opendiag
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 openmodem
lrwxrwxrwx 1 root root 6 Feb 29 03:34 paste -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 patch -> toybox
-rwxr-xr-x 1 root shell 67064 Aug 1 2008 patchoat
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pgrep -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pidof -> toybox
-rwxr-xr-x 1 root root 47240 Aug 1 2008 ping
-rwxr-xr-x 1 root shell 47656 Aug 1 2008 ping6
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pkill -> toybox
-rwxr-xr-x 1 root shell 191 Aug 1 2008 pm
-rwxr-xr-x 1 root shell 10184 Aug 1 2008 pm-proxy
-rwxr-xr-x 1 root shell 43512 Aug 1 2008 pm-service
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pmap -> toybox
-rwxr-xr-x 1 root shell 51328 Aug 1 2008 pnpmgr
-rwxr-xr-x 1 root shell 14216 Aug 1 2008 port-bridge
-rwxr-xr-x 1 root shell 279888 Aug 1 2008 pppd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 printenv -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 printf -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 prlimit -> toolbox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ps -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pwd -> toybox
-rwxr-xr-x 1 root shell 26672 Aug 1 2008 qcom-system-daemon
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 qemu-props
-rwxr-xr-x 1 root shell 18288 Aug 1 2008 qemud
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 qfipsverify
-rwxr-xr-x 1 root shell 22056 Aug 1 2008 qjpeg-dma-test
drwxr-xr-x 2 root shell 4096 Feb 29 03:33 qmi-framework-tests
-rwxr-xr-x 1 root shell 156824 Aug 1 2008 qmuxd
-rwxr-xr-x 1 root shell 10112 Aug 1 2008 qrngtest
-rwxr-xr-x 1 root shell 30872 Aug 1 2008 qseecom_sample_client
-rwxr-xr-x 1 root shell 22064 Aug 1 2008 qseecom_security_test
-rwxr-xr-x 1 root shell 14592 Aug 1 2008 qseecomd
-rwxr-xr-x 1 root shell 283280 Aug 1 2008 racoon
-rwxr-xr-x 1 root shell 63480 Aug 1 2008 radish
lrwxrwxrwx 1 root root 6 Feb 29 03:34 readlink -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 realpath -> toybox
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 reboot
-rwxr-xr-x 1 root shell 10680 Aug 1 2008 regdbdump
lrwxrwxrwx 1 root root 7 Feb 29 03:34 renice -> toolbox
-rwxr-xr-x 1 root shell 188 Aug 1 2008 requestsync
-rwxr-xr-x 1 root shell 42864 Aug 1 2008 resize2fs
lrwxrwxrwx 1 root root 6 Feb 29 03:34 restorecon -> toybox
-rwxr-xr-x 1 root shell 37256 Aug 1 2008 rfs_access
-rwxr-xr-x 1 root shell 18312 Aug 1 2008 rild
lrwxrwxrwx 1 root root 6 Feb 29 03:34 rm -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 rmdir -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 rmmod -> toybox
-rwxr-xr-x 1 root shell 21112 Aug 1 2008 rmnetcli
-rwxr-xr-x 1 root shell 39944 Aug 1 2008 rmt_storage
lrwxrwxrwx 1 root root 6 Feb 29 03:34 route -> toybox
-rwxr-x--- 1 root shell 14192 Aug 1 2008 run-as
lrwxrwxrwx 1 root root 6 Feb 29 03:34 runcon -> toybox
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 schedtest
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 screencap
-rwxr-xr-x 1 root shell 116752 Aug 1 2008 screenrecord
-rwxr-xr-x 1 root shell 30576 Aug 1 2008 sdcard
-rwxr-xr-x 1 root shell 26552 Aug 1 2008 secure_camera_sample_client
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sed -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 sendevent -> toolbox
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 sensorservice
lrwxrwxrwx 1 root root 6 Feb 29 03:34 seq -> toybox
-rwxr-xr-x 1 root shell 18360 Aug 1 2008 service
-rwxr-xr-x 1 root shell 18360 Aug 1 2008 servicemanager
lrwxrwxrwx 1 root root 6 Feb 29 03:34 setenforce -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 setprop -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 setsid -> toybox
-rwxr-xr-x 1 root shell 178 Aug 1 2008 settings
-rwxr-xr-x 1 root shell 10104 Aug 1 2008 setup_fs
-rwxr-xr-x 1 root shell 161736 Aug 1 2008 sgdisk
-rwxr-xr-x 1 root shell 289432 Aug 1 2008 sh
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sha1sum -> toybox
-rwxr-xr-x 1 root shell 194752 Aug 1 2008 shub_dbg
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sleep -> toybox
-rwxr-xr-x 1 root shell 190 Aug 1 2008 sm
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sort -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 split -> toybox
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 ssr_diag
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 ssr_setup
lrwxrwxrwx 1 root root 7 Feb 29 03:34 start -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 stat -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 stop -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 strings -> toybox
-rwxr-xr-x 1 root shell 30632 Aug 1 2008 subsystem_ramdump
-rwxr-xr-x 1 root shell 14208 Aug 1 2008 surfaceflinger
-rwxr-xr-x 1 root shell 192 Aug 1 2008 svc
lrwxrwxrwx 1 root root 6 Feb 29 03:34 swapoff -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 swapon -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sync -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sysctl -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tac -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tail -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tar -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 taskset -> toybox
-rwxr-x--- 1 root system 96880 Aug 1 2008 tc
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tee -> toybox
-rwxr-xr-x 1 root shell 172 Aug 1 2008 telecom
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 test_diag
-rwxr-xr-x 1 root shell 26152 Aug 1 2008 test_module_pproc
-rwxr-xr-x 1 root shell 84232 Aug 1 2008 tftp_server
-rwxr-xr-x 1 root shell 18360 Aug 1 2008 thermal-monitor
lrwxrwxrwx 1 root root 6 Feb 29 03:34 time -> toybox
-rwxr-xr-x 1 root shell 34768 Aug 1 2008 time_daemon
lrwxrwxrwx 1 root root 6 Feb 29 03:34 timeout -> toybox
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 tinycap
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 tinymix
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 tinypcminfo
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 tinyplay
-rwxr-xr-x 1 root shell 148184 Aug 1 2008 toolbox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 top -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 touch -> toybox
-rwxr-xr-x 1 root shell 310800 Aug 1 2008 toybox
-rwxr-xr-x 1 root shell 170224 Aug 1 2008 tpd_daemon
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tr -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 true -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 truncate -> toybox
-rwxr-xr-x 1 root shell 18288 Aug 1 2008 tzdatacheck
-rwxr-xr-x 1 root shell 3814 Aug 1 2008 uiautomator
lrwxrwxrwx 1 root root 6 Feb 29 03:34 umount -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 uname -> toybox
-rwxr-x--- 1 root root 39344 Aug 1 2008 uncrypt
lrwxrwxrwx 1 root root 6 Feb 29 03:34 uniq -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 unix2dos -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 uptime -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 usleep -> toybox
-rwxr-xr-x 1 root shell 10112 Aug 1 2008 vdc
lrwxrwxrwx 1 root root 6 Feb 29 03:34 vmstat -> toybox
-rwxr-xr-x 1 root shell 514712 Aug 1 2008 vold
lrwxrwxrwx 1 root root 7 Feb 29 03:34 watchprops -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 wc -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 which -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 whoami -> toybox
-rwxr-xr-x 1 root shell 18064 Aug 1 2008 wifi_otp_programming
-rwxr-xr-x 1 root shell 68344 Aug 1 2008 wifitest
-rwxr-xr-x 1 root shell 190 Aug 1 2008 wm
-rwxr-xr-x 1 root shell 118512 Aug 1 2008 wpa_cli
-rwxr-xr-x 1 root shell 1805728 Aug 1 2008 wpa_supplicant
lrwxrwxrwx 1 root root 6 Feb 29 03:34 xargs -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 yes -> toybox
I can provide any other data upon request...
Thank you for your time.
Why is your bootloader locked?
Is it really or is that my faux hboot?
Sent from my HTC6535LVW using Tapatalk
santod040 said:
Why is your bootloader locked?
Is it really or is that my faux hoot?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I'm guessing its really locked? ....I'll shoot myself in the foot if this is the entire issue. When I used the XTC2 Clip I enabled S-OFF and everything was unlocked to my knowledge.
MrTrip said:
I'm guessing its really locked? ....I'll shoot myself in the foot if this is the entire issue. When I used the XTC2 Clip I enabled S-OFF and everything was unlocked to my knowledge.
Click to expand...
Click to collapse
Pretty sure that's your problem...it's still locked, although s-off.
Sent from my HTC6535LVW using Tapatalk
santod040 said:
Pretty sure that's your problem...it's still locked, although s-off.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I'm making a flying trip across town to grab my Clip, I will report back ASAP. I will absolutely be floored if this was the issue...
MrTrip said:
I'm making a flying trip across town to grab my Clip, I will report back ASAP. I will absolutely be floored if this was the issue...
Click to expand...
Click to collapse
Hopefully this fixes it.
This is a thread to unlock BL using terminal.
But if already on your way and prefer using the clip I'd go that method.
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
Actually, you need SU for that to work, my bad.
Glad you have a clip.
santod040 said:
Pretty sure that's your problem...it's still locked, although s-off.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
andybones said:
Hopefully this fixes it.
This is a thread to unlock BL using terminal.
But if already on your way and prefer using the clip I'd go that method.
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
Actually, you need SU for that to work, my bad.
Glad you have a clip.
Click to expand...
Click to collapse
This fixed it. Holy crud. Did I miss somewhere in the thread that S-OFF and ALSO Bootloader Unlocked?!
I thought Locked meant I was SIM locked, not BOOTLOADER locked...Oh...my...god I'm retarded...It is official :silly::silly::good::silly::silly::good::good:
4 days of total hell because of a locked bootloader, even though S-OFF let me do everything else... :silly::silly::silly:
Thank you guys SO MUCH, I'm sorry I've been a pill. I never needed Bootloader unlocked for Root before because it was system-mode not system-less...
CRUDDDD
Edit: I executed those commands in the Recovery, as I had root in Recovery and was able to set Bootloader to unlocked.
How were you using TWRP ?
I knew there were (2) steps involved in rooting the M9, one was getting S-OFF and the other was unlocking the bootloader. Since you were using TWRP, I thought that meant your bootloader must be unlocked. Or, I'm confusing what's needed...
hallstevenson said:
How were you using TWRP ?
I knew there were (2) steps involved in rooting the M9, one was getting S-OFF and the other was unlocking the bootloader. Since you were using TWRP, I thought that meant your bootloader must be unlocked. Or, I'm confusing what's needed...
Click to expand...
Click to collapse
Once S-OFF you can flash whatever you want, minus modifying bootloader. When I became S-OFF on Android 5 I flashed Recovery, installed Root, and went on my day. The bootloader was never unlocked, and I was unaware of this because I had root and everything seemed to function normally. Come to find out I missed out on a lot having a locked bootloader still, even though I had root.
Once 6.0 came along, root went system-less and required patching boot, but I couldn't do this because the bootloader was locked, hence no root. :good:
It should be noted, because I know I followed a guide somewhere, that 6.0+ REQUIRES unlocked bootloader to achieve Root.
hallstevenson said:
How were you using TWRP ?
I knew there were (2) steps involved in rooting the M9, one was getting S-OFF and the other was unlocking the bootloader. Since you were using TWRP, I thought that meant your bootloader must be unlocked. Or, I'm confusing what's needed...
Click to expand...
Click to collapse
Even on the m8 you could flash twrp while locked but s-off. Number one reason I kept ruu mode flashable twrp zips posted. M9 simply came not caring while in download mode.
Fwiw, this was my number one concern with the mass influx of clip holders working on other members phones. The troubleshooting experience is not there to support the operations taking place. This statement is not meant to chide the op...just food for thought.
Motorola
Envoyé de mon XT1563 en utilisant Tapatalk
Having the same bit of trouble as MrTrip did, I'm very confused, before I made the attempt to go to Marshmellow from Lollipop I has SU and everything was fine and dandy. Can't remember if I had my Booloader unlocked before, but now it certinaly shows up as locked now which is confusing. Regardless, maybe someone knows here, since I am S-OFF I should be able to go the HTCDev route and unlock the bootloader correct?
**Edit** Crap, forgot the whole Verizon is garbage and locks their phones from HTCDev. Still confusing, because I did have it unlocked at one point with a Java Card...
wingman1487 said:
Having the same bit of trouble as MrTrip did, I'm very confused, before I made the attempt to go to Marshmellow from Lollipop I has SU and everything was fine and dandy. Can't remember if I had my Booloader unlocked before, but now it certinaly shows up as locked now which is confusing. Regardless, maybe someone knows here, since I am S-OFF I should be able to go the HTCDev route and unlock the bootloader correct?
**Edit** Crap, forgot the whole Verizon is garbage and locks their phones from HTCDev. Still confusing, because I did have it unlocked at one point with a Java Card...
Click to expand...
Click to collapse
You only need to run a single adb command to unlock that boot loader as long as you are s-off.
Sent from my HTC6545LVW using Tapatalk
dottat said:
You only need to run a single adb command to unlock that boot loader as long as you are s-off.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
But don't you have to be Rooted to run that?
http://forum.xda-developers.com/verizon-one-m9/help/m9-s-0ff-unlock-t3385095
wingman1487 said:
But don't you have to be Rooted to run that?
http://forum.xda-developers.com/verizon-one-m9/help/m9-s-0ff-unlock-t3385095
Click to expand...
Click to collapse
Easiest way is to boot to twrp and do it. You need an ruu mode version of twrp to flash?
Flash this like you would an ruu or firmware zip. Then boot to recovery and run your adb command. Note you won't need to su as you already have root privs in twrp.
https://www.androidfilehost.com/?fid=24457741883933189
Sent from my HTC6545LVW using Tapatalk
dottat said:
Easiest way is to boot to twrp and do it. You need an ruu mode version of twrp to flash?
Flash this like you would an ruu or firmware zip. Then boot to recovery and run your adb command. Note you won't need to su as you already have root privs in twrp.
https://www.androidfilehost.com/?fid=24457741883933189
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Humm, think I'm missing something.
Code:
c:\ADB>fastboot flash zip RUUmodeTWRP3_0_0_1.zip
target reported max download size of 800000000 bytes
sending 'zip' (12898 KB)...
OKAY [ 1.671s]
writing 'zip'...
(bootloader) HOSD CL#669662
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
finished. total time: 2.767s
Try this zip instead
https://www.androidfilehost.com/?fid=24438995911973227
Same result