Hi,
I use KALI Linux and an Android 4.1.2 Tablet for my test. I want to install an App like this:
drops.wooyun.org/papers/548
At Kali Linux i use the exploit webview_addjavascriptinterface and get a response from my tablet (same WLAN).
msf exploit(webview_addjavascriptinterface) > [*] 192.168.178.23 webview_addjavascriptinterface - Gathering target information.
[*] 192.168.178.23 webview_addjavascriptinterface - Sending response HTML.
[*] 192.168.178.23 webview_addjavascriptinterface - Serving exploit HTML
[*] Command shell session 1 opened (192.168.178.39:35534 -> 192.168.178.23:8080) at 2014-05-16 11:27:41 +0000
msf exploit(webview_addjavascriptinterface) > sessions -i 1
[*] Starting interaction with 1...
export PATH=/system/bin:$PATH
ls -al
drwxr-xr-x root root 2014-05-15 16:56 acct
-rw-r--r-- root root 332 2014-05-15 16:56 boot.txt
drwxrwx--x system cache 2014-05-10 09:22 cache
dr-x------ root root 2014-05-15 16:56 config
lrwxrwxrwx root root 2014-05-15 16:56 d -> /sys/kernel/debug
drwxrwx--x system system 2014-05-12 09:41 data
-rw-r--r-- root root 129 2014-05-15 16:56 default.prop
drwxr-xr-x root root 2014-05-15 17:12 dev
drwxr-xr-x radio radio 2014-05-09 13:55 efs
lrwxrwxrwx root root 2014-05-15 16:56 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2014-05-15 16:56 etc -> /system/etc
-rwxr-x--- root root 105292 2014-05-15 16:56 init
-rwxr-x--- root root 1107 2014-05-15 16:56 init.cm.rc
-rwxr-x--- root root 2344 2014-05-15 16:56 init.goldfish.rc
-rwxr-x--- root root 5171 2014-05-15 16:56 init.p1-common.rc
-rwxr-x--- root root 5389 2014-05-15 16:56 init.p1.rc
-rwxr-x--- root root 936 2014-05-15 16:56 init.p1.usb.rc
-rwxr-x--- root root 17862 2014-05-15 16:56 init.rc
-rwxr-x--- root root 1637 2014-05-15 16:56 init.trace.rc
-rwxr-x--- root root 3915 2014-05-15 16:56 init.usb.rc
-rw-r--r-- root root 1664 2014-05-15 16:56 lpm.rc
drwxrwxr-x root system 2014-05-15 16:56 mnt
dr-xr-xr-x root root 1970-01-01 00:00 proc
drwxr-xr-x root root 2014-05-09 13:55 radio
drwxr-x--- root root 2014-05-15 16:56 sbin
lrwxrwxrwx root root 2014-05-15 16:56 sdcard -> /storage/sdcard0
d---r-x--- system sdcard_r 2014-05-15 16:56 storage
drwxr-xr-x root root 2014-05-15 16:56 sys
drwxr-xr-x root root 2014-05-09 13:56 system
-rw-r--r-- root root 272 2014-05-15 16:56 ueventd.goldfish.rc
-rw-r--r-- root root 2035 2014-05-15 16:56 ueventd.p1.rc
-rw-r--r-- root root 5075 2014-05-15 16:56 ueventd.rc
lrwxrwxrwx root root 2014-05-15 16:56 vendor -> /system/vendor
I want to copy some pictures to my KALI system but there is the problem:
dd if=/sdcard/DCIM/Camera of=/dev/sdc bs=1M
/dev/sdc: cannot open for write: Permission denied
Or i want to run adb (no device!)
adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
Can someone help or explain me how to do this?
Best regards
Related
SOLVED - Moved to Q&A section: http://forum.xda-developers.com/showthread.php?t=896514
I had this problem with an earlier version, have gone back to CM where it was fine and now, when trying v.16 (after a FULL WIPE), have the exact same problem.
Settings show I have plenty of storage but when I try to install/update from the Market or via adb install or Titanium restore I get the message Install failed insufficient storage.
Settings shows 126MB free.
If I adb push to /system/app there is no problem (but the apps do not show uninstall or move to SD options)
Also get exactly the same error with PhoenRom v1.0 (but not CyanogenMod 6.1.1)
Any help would be most appreciated!
Check /system/ space available.
Sent from my Nexus One using XDA App
Treatcon said:
Check /system/ space available.
Click to expand...
Click to collapse
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 126M 18M 4096
/data 196M 53M 142M 4096
/cache 95M 3M 91M 4096
/system/sd 955M 11M 943M 4096
/mnt/sdcard 6G 3G 3G 4096
/mnt/secure/asec 6G 3G 3G 4096
ls -l of the root directory:
dr-x------ root root 2011-01-01 17:23 config
drwxrwx--- system cache 2011-01-01 17:30 cache
lrwxrwxrwx root root 2011-01-01 17:23 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2011-01-01 17:23 acct
drwxrwxr-x root system 2011-01-01 17:23 mnt
lrwxrwxrwx root root 2011-01-01 17:23 vendor -> /system/vendor
lrwxrwxrwx root root 2011-01-01 17:23 d -> /sys/kernel/debug
lrwxrwxrwx root root 2011-01-01 17:23 etc -> /system/etc
-rw-r--r-- root root 3764 1970-01-01 01:00 ueventd.rc
-rw-r--r-- root root 26 1970-01-01 01:00 ueventd.mahimahi.rc
-rw-r--r-- root root 0 1970-01-01 01:00 ueventd.goldfish.rc
drwxr-xr-x root root 2011-01-01 17:22 system
drwxr-xr-x root root 2011-01-01 17:23 sys
drwxr-x--- root root 1970-01-01 01:00 sbin
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rwxr-x--- root root 13944 1970-01-01 01:00 init.rc
-rwxr-x--- root root 3323 1970-01-01 01:00 init.mahimahi.rc
-rwxr-x--- root root 1677 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 90084 1970-01-01 01:00 init
-rw-r--r-- root root 118 1970-01-01 01:00 default.prop
drwxrwx--x system system 2011-01-01 17:24 data
drwx------ root root 2010-10-20 00:01 root
drwxr-xr-x root root 2011-01-01 17:23 dev
ls -l of /system:
drwxr-xr-x root root 2011-01-01 17:21 etc
-rw-r--r-- root root 2019 2008-08-01 13:00 build.prop
drwxr-xr-x root root 2011-01-01 17:21 media
drwxr-xr-x root shell 2011-01-01 17:22 xbin
drwxr-xr-x root shell 2011-01-01 17:22 vendor
drwxr-xr-x root shell 2011-01-01 17:22 bin
drwxr-xr-x root root 2011-01-01 17:21 lib
drwxr-xr-x root root 2011-01-01 17:22 usr
drwxr-xr-x root root 2011-01-01 17:21 framework
drwxr-xr-x root root 2011-01-01 17:21 fonts
drwxr-xr-x root root 2011-01-01 17:21 tts
drwxrwxrwx root root 1970-01-01 01:00 sd
drwxr-xr-x root root 2011-01-01 17:21 lost+found
drwxr-xr-x root root 2011-01-01 17:21 app
You have 18MB free in /system
andonnguyen said:
You have 18MB free in /system
Click to expand...
Click to collapse
Yes and Settings shows 126MB free but it won't even let me update.
126MB is /data storage. Not /system.
I think it is APP2EXT problem...
Try 'a2sd remove' then 'a2sd reinstall'
And wrong forum..
Apps are supposed to be installed to data, not system.
Pushing apps to system means you can't uninstall them normally as they will become part of the system apps.
In any case you still seem to have sufficient space in your /data so you shouldn't have any problems installing a few more apps, which is weird.
Are you using Dark Tremor's apps2sd? Also what did you use to check your free space?
You can try going to recovery and clear cache and dalvik cache and reboot your phone.
wisechild said:
126MB is /data storage. Not /system.
I think it is APP2EXT problem...
Try 'a2sd remove' then 'a2sd reinstall'
And wrong forum..
Click to expand...
Click to collapse
Thanks for the reply.
Tried 'a2sd remove' then 'a2sd reinstall' but no change.
Sorry about it being in the wrong forum, I originally thought the problem was related to the MM Gingerbread ROM, until I tried the PhoenRom and had the same problem with that.
musashiken said:
Apps are supposed to be installed to data, not system.
Pushing apps to system means you can't uninstall them normally as they will become part of the system apps.
In any case you still seem to have sufficient space in your /data so you shouldn't have any problems installing a few more apps, which is weird.
Are you using Dark Tremor's apps2sd? Also what did you use to check your free space?
You can try going to recovery and clear cache and dalvik cache and reboot your phone.
Click to expand...
Click to collapse
Thanks for your reply.
Yes, Dark Tremor's apps2sd is on there - (which I didn't realise!)
My SD card is partitioned 7GB Windows/1GB Linux.
Booting Linux on my PC I can see the apps in the Linux partition.
Tried clearing cache and dalvik cache but no change.
Going into Settings/Applications/Downloaded shows "72MB used / 124MB free"
On SD card shows "3.2GB used / 3.3GB free"
I currently have the PhoenRom installed, this is what df now shows:
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 141M 3M 4096
/data 196M 75M 120M 4096
/cache 95M 4M 90M 4096
/system/sd 955M 26M 928M 4096
/mnt/sdcard 6G 3G 3G 4096
/mnt/secure/asec 6G 3G 3G 4096
/mnt/asec/com.android.BlackMarketApp-1 3M 1M 1M 4096
When wiping user data in recovery I get the message
E:Can't mount /dev/block/mmcblk0p2 (or /dev/bloc/mmcblk0)
(Invalid argument)
Error mounting /sd-ext/!
Skipping format
I don't know if this is significant.
happened on me once, retried a few times and they updated no problem.
running MM v.10 with his themed addons v.1.3 and old market.
ran a2sd reinstall, a2sd zipalign and a2sd cachepart.
btw i had been flashing between the new market and old market, and ran a2sd resetcache many times too.
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!
Hi, someone else get this problem?
my galaxy p7500 have a peculiar problem.
it boots and works, but when i install some app or unnistal, create/delete file or do a factory reset.
all back to the old defect state, like this tab gets frozen in time.
So, i try to use odin, and then:
use the files:
P7500_P7510_android_fastboot_emmc_full_p4_16G_32G.pit
and
stock rom P7500ZTOLP4_P7500UBLP9_P7500UBLP3_HOME.tar
but when I put to flash, it goes and fail, this is what show on the tab: pls see the pics
I think I have a permissions trouble.
The tablet is working for about 10 minutes, then stop, if i check the volume space the tab freeze.
so... I'm using adb from recovery, and acessing tab's shell.
If I use : ll -a
shows->
drwxr-xr-x root root 2015-08-02 15:23 cache
drwxr-xr-x root root 1970-01-01 00:00 data
-rw-r--r-- root root 2302 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2015-08-02 15:23 dev
drwxr-xr-x root root 2015-08-02 15:23 efs
drwxr-xr-x root root 1970-01-01 00:00 etc
-rwxr-x--- root root 148088 1970-01-01 00:00 init
-rwxr-x--- root root 1431 1970-01-01 00:00 init.rc
drwxr-xr-x root root 1970-01-01 00:00 lib
-rw-r--r-- root root 1861 1970-01-01 00:00 lpm.rc
drwxr-xr-x root root 2015-08-02 15:23 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2012-10-15 13:06 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2015-08-02 15:23 sdcard
drwxr-xr-x root root 2015-08-02 15:23 sdcard1
drwxr-xr-x root root 2015-08-02 15:23 sys
drwxr-xr-x root root 2014-02-10 03:52 system
drwxr-xr-x root root 2015-08-02 15:23 tmp
-rw-r--r-- root root 272 1970-01-01 00:00 ueventd.goldfish.rc
-rw-r--r-- root root 1276 1970-01-01 00:00 ueventd.p3.rc
-rw-r--r-- root root 3825 1970-01-01 00:00 ueventd.rc
I tried to usb adb sideload too, but this apear not working, it keep loading: 'update.zip"
The odin gets btc_sync error, nvflash 0x04 error,
someone know what can I do??
i got this using dmesg, someone can bring some light?
3>[ 3.342022] init: [disk_config] ext_check -> /system/bin/e2fsck -v -y /dev/block/platform/sdhci-tegra.3/by-num/p5
<3>[ 3.469928] init: [disk_config] Error ::execute :: Error in (Status 8)
<3>[ 3.470261] init: [disk_config] Error ::* failed to check -1
<6>[ 3.492495] EXT4-fs (mmcblk0p5): recovery complete
<6>[ 3.494914] EXT4-fs (mmcblk0p5): mounted filesystem with writeback data mode. Opts: journal_async_commit,data=writeback,nodelalloc,errors=panic
<3>[ 3.496302] init: Device Encryption status is (0)!!
<3>[ 3.496402] init: [disk_config] :::: fsck -> /dev/block/platform/sdhci-tegra.3/by-num/p8 (ext4):::::
<3>[ 3.496764] init: [disk_config] ext_check -> /system/bin/e2fsck -v -y /dev/block/platform/sdhci-tegra.3/by-num/p8
<3>[ 6.611433] init: [disk_config] Error ::execute :: Error in (Status 8)
<3>[ 6.611779] init: [disk_config] Error ::* failed to check -1
OK - it seems that it is fairly easy to load Facer and all the Facer faces that you have onto your Watch. I won't go into much detail here - you can search other threads on this site or others for details on how to do this (many of the steps can be found in this thread: http://forum.xda-developers.com/android-wear/development/getting-watchmaker-watch-android-wear-t3262448). But the basic idea is to load the wearable .apk file extracted from the Facer app on the Android host (the device which you run Facer and create/load/modify your watch faces) onto the watch, and then copy the key watch folders to the watch as well. You will need the Android SDK tools to do this, along with a USB connection to the watch (most watches except the original Moto 360 come with one - the charging cable, which also contains data lines). You can use two free tools from the Play Store to help with these tasks - ES File Manager and AirDroid.
The basic idea is to first create all the faces that you wish to use on either an Android device or Emulator (Android host).
After this, if you examine your Android host device, you will see two Facer folders in the /sdcard folder - Facer, and Facer2. You only need to use part of the Facer folder.
Steps:
1. Install Facer from the Play Store on the Android host device and develop your watches.
2. Install the wearable .apk (*adb install ...*) onto the watch.
3. Copy the /sdcard/Facer folder to your PC or Mac. Then remove everything except the long hex-string folders - these are the watch face folders.
4. Copy this modified Facer folder to the watch using *adb push ...*
5. Reboot the watch, then press the watch face (brings up the watch face selector), scroll until you find the Facer icon, press the settings
button and then select the Facer watch face that you want to use.
That should be it. If you examine the file structure on the watch after this, you will find a couple of new folders - none_selected and sync.
and a watchface_1.zip file.
As you add new watches, new hex-string folders will be created on the host Android device. Just transfer those folders to your PC or Mac and
then transfer them back to your watch.
Kevin
Please can somebody upload wholeFacer directory from watch with few installed watchfaces ? i need to see how look folder structure with multiple load faces. Thanks a lot.
x5ox1 said:
Please can somebody upload wholeFacer directory from watch with few installed watchfaces ? i need to see how look folder structure with multiple load faces. Thanks a lot.
Click to expand...
Click to collapse
Here are some directory structures from my Android host and watch. First, the host:
adb -e shell ls -al /sdcard/Facer
-rwxrwx--- root sdcard_r 0 2016-01-25 14:59 .nomedia
drwxrwx--- root sdcard_r 2016-01-25 14:59 135d95fb-06cb-4a2a-832c-5fc45e9b9fb0
drwxrwx--- root sdcard_r 2016-01-25 14:59 6b07b86c-ebda-49af-bb31-d9ec8a71da03
drwxrwx--- root sdcard_r 2016-01-25 14:59 848a2270-9d55-4353-a62b-b153badcce69
drwxrwx--- root sdcard_r 2016-01-25 14:59 9358cc22-8f49-411c-a725-607636a1b0ee
-rwxrwx--- root sdcard_r 331653 2016-01-25 14:59 Colorful.zip
-rwxrwx--- root sdcard_r 524582 2016-01-25 14:59 Digiloge.zip
-rwxrwx--- root sdcard_r 101885 2016-01-25 14:59 E3 Military.zip
-rwxrwx--- root sdcard_r 357285 2016-01-25 14:59 E3 Supply Co Aviator.zip
-rwxrwx--- root sdcard_r 94620 2016-01-25 14:59 Moto Dark.zip
drwxrwx--- root sdcard_r 2016-01-25 14:59 b7c9deb0-e43d-4892-ae96-2b826681c2f4
I have 5 installed watch faces - the Moto Dark resides in the b7c9deb0... folder
adb -e shell ls -al /sdcard/Facer/b7c9deb0-e43d-4892-ae96-2b826681c2f4
-rwxrwx--- root sdcard_r 562 2016-01-25 16:21 description.json
drwxrwx--- root sdcard_r 2016-01-25 14:59 fonts
drwxrwx--- root sdcard_r 2016-01-25 14:59 images
-rwxrwx--- root sdcard_r 9342 2016-01-25 15:23 preview.png
-rwxrwx--- root sdcard_r 1874 2016-01-25 15:23 watchface.json
-rwxrwx--- root sdcard_r 238 2016-01-25 15:23 watchface_settings.json
Now, the watch:
adb -d shell ls -al /sdcard/Facer
drwxrwx--- root sdcard_r 2016-01-25 15:25 135d95fb-06cb-4a2a-832c-5fc45e9b9fb0
drwxrwx--- root sdcard_r 2016-01-25 15:25 6b07b86c-ebda-49af-bb31-d9ec8a71da03
drwxrwx--- root sdcard_r 2016-01-25 15:25 848a2270-9d55-4353-a62b-b153badcce69
drwxrwx--- root sdcard_r 2016-01-25 15:25 9358cc22-8f49-411c-a725-607636a1b0ee
drwxrwx--- root sdcard_r 2016-01-25 15:25 b7c9deb0-e43d-4892-ae96-2b826681c2f4
drwxrwx--- root sdcard_r 2016-01-25 14:40 none_selected
drwxrwx--- root sdcard_r 2016-01-25 14:40 sync
-rw-rw---- root sdcard_r 652974 2016-01-25 14:40 watchface_1.zip
Note that I only copied the first 5 (hex) folders from the host to the watch; the rest was created by Facer after starting it on the watch.
And finally:
adb -d shell ls -al /sdcard/Facer/b7c9deb0-e43d-4892-ae96-2b826681c2f4
-rw-rw---- root sdcard_r 562 2016-01-27 22:01 description.json
drwxrwx--- root sdcard_r 2016-01-25 15:25 fonts
drwxrwx--- root sdcard_r 2016-01-25 15:25 images
-rw-rw---- root sdcard_r 9342 2016-01-25 15:25 preview.png
-rw-rw---- root sdcard_r 1874 2016-01-25 15:25 watchface.json
-rw-rw---- root sdcard_r 238 2016-01-25 15:25 watchface_settings.json
This appears to be exactly the same as on the host.
Hope this helps.
Kevin
Hi,
i have a small problem a i hope someone here would be able to help me or enlighten me of what i have done wrong
I took my old Huawei Media pad s7-301u from the shelf to test if its still working or what condition he is in. The table booted normally into the system and everything seemed to be working but i have decided to hard-reset the tablet for future work. Since i had TWRP installed the system went to the recovery where i have decided to install a fresh stock ROM and therefore i have wiped all data using the recovery. After rebooting the touchscreen stopped to work, in TWRP, and overall anything. Hence, i have pushed the stock recovery into it and updated to the stock ROM using the inbuilt updater - everything went OK but the tablet was dead. After lots of trying i red somewhere that the wipe through TRWP could do something with one of the partition and thus i tried to convert them to ext2 and back to ext4 to fix the issue and truly it fixed the issue with the system and after updating the tablet went in to the system, however, the touchscreen is not working at all.
I have used the TWRP: 2.8.4.0
Stock ROM: S7-301u V100R002C232B005 ICS Android 4.0.3 General Version
What i have tried during my work was to push all the files for flash through fastboot
Code:
fastboot.exe flash modem non-hlos.bin
fastboot.exe flash sbl1 sbl1.mbn
fastboot.exe flash sbl2 sbl2.mbn
fastboot.exe flash ext oeminfo
fastboot.exe flash rpm rpm.mbn
fastboot.exe flash sbl3 sbl3.mbn
fastboot.exe flash aboot emmc_appsboot.mbn
fastboot.exe flash tz tz.mbn
fastboot.exe flash logo logo.img
fastboot.exe flash modem_st1 modem_st1.mbn
fastboot.exe flash modem_st2 modem_st2.mbn
fastboot.exe flash cust cust.img.ext4
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img.ext4
fastboot.exe flash persist persist.img.ext4
fastboot.exe flash cache cache.img.ext4
fastboot.exe flash userdata userdata.img.ext4
fastboot.exe flash tombstones tombstones.img.ext4
fastboot.exe flash recovery recovery.img
fastboot.exe flash recovery2 recovery.img
The tablet reports, after update, that the "touchscreen firmware upgrade failed" but i cant figure out why it is not working. In the log from the update is:
Code:
Huawei product info file found ......
software version is not need to check!
Huawei software version Verfying success......
hardware version is not need to check!
Huawei hardware version Verfying success......
update parti num = 26
try to update coulmeter firmware!
try to update touchscreen firmware!
Success to fork coulmeter child process!
Huawei could not found coulmeter firmware version file......
coulmeter write return 9
wait for child processes return!
sys parti num = 26, update parti num =26
partition table not change
Success to fork touchscreen child process!
start huawei_update_touchscreen_firmware
minzip: Extracted dir "/tmp/touchscreen/"
minzip: Extracted file "/tmp/touchscreen/atmel_cmi_pro.img"
minzip: Extracted file "/tmp/touchscreen/s7020_suc.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1828_001.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1885_004.img"
mzExtractRecursive return 0
touchscreen update Can't copy /tmp/touchscreen
touchscreen write return 4
update zip package has boot img
Huawei contain bootloader's img......
Huawei begin structuring the update partition list......
And the update file/pack include a folder with the "touchscreen" img, however, iam not sure why its reporting the error about "copy" which is above. Using adb i have listed some files/folders and found the img files inside etc/firmware. The files are listed with extension *.img and are four: atmel_cmi_pro.img, t1320_tm1885_004.img, t1320_tm1828_001.img a t1320_tm1828_001.img.
Code:
ls -la
-rw-r--r-- root root 3750 2012-06-07 18:17 atmel_cmi_pro.img
-rw-r--r-- root root 72020 2012-06-07 18:17 cyttsp_8660_ffa.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p2.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p3.hex
-rw-r--r-- root root 180 2012-06-07 18:17 dsps_fluid.b00
-rw-r--r-- root root 120 2012-06-07 18:17 dsps_fluid.b01
-rw-r--r-- root root 105484 2012-06-07 18:17 dsps_fluid.b02
-rw-r--r-- root root 6256 2012-06-07 18:17 dsps_fluid.b03
-rw-r--r-- root root 428 2012-06-07 18:17 dsps_fluid.mdt
-rw-r--r-- root root 1156 2012-06-07 18:17 leia_pfp_470.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 leia_pm4_470.fw
lrwxrwxrwx root root 2011-01-01 19:49 modem.b00 -> /firmware/image/modem.b00
lrwxrwxrwx root root 2011-01-01 19:49 modem.b01 -> /firmware/image/modem.b01
lrwxrwxrwx root root 2011-01-01 19:49 modem.b02 -> /firmware/image/modem.b02
lrwxrwxrwx root root 2011-01-01 19:49 modem.b03 -> /firmware/image/modem.b03
lrwxrwxrwx root root 2011-01-01 19:49 modem.b04 -> /firmware/image/modem.b04
lrwxrwxrwx root root 2011-01-01 19:49 modem.b05 -> /firmware/image/modem.b05
lrwxrwxrwx root root 2011-01-01 19:49 modem.b06 -> /firmware/image/modem.b06
lrwxrwxrwx root root 2011-01-01 19:49 modem.b07 -> /firmware/image/modem.b07
lrwxrwxrwx root root 2011-01-01 19:49 modem.b08 -> /firmware/image/modem.b08
lrwxrwxrwx root root 2011-01-01 19:49 modem.b09 -> /firmware/image/modem.b09
lrwxrwxrwx root root 2011-01-01 19:49 modem.b10 -> /firmware/image/modem.b10
lrwxrwxrwx root root 2011-01-01 19:49 modem.mdt -> /firmware/image/modem.mdt
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b00 -> /firmware/image/playrdy.b00
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b01 -> /firmware/image/playrdy.b01
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b02 -> /firmware/image/playrdy.b02
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.mdt -> /firmware/image/playrdy.mdt
lrwxrwxrwx root root 2011-01-01 19:49 q6.b00 -> /firmware/image/q6.b00
lrwxrwxrwx root root 2011-01-01 19:49 q6.b01 -> /firmware/image/q6.b01
lrwxrwxrwx root root 2011-01-01 19:49 q6.b02 -> /firmware/image/q6.b02
lrwxrwxrwx root root 2011-01-01 19:49 q6.b03 -> /firmware/image/q6.b03
lrwxrwxrwx root root 2011-01-01 19:49 q6.b04 -> /firmware/image/q6.b04
lrwxrwxrwx root root 2011-01-01 19:49 q6.b05 -> /firmware/image/q6.b05
lrwxrwxrwx root root 2011-01-01 19:49 q6.b06 -> /firmware/image/q6.b06
lrwxrwxrwx root root 2011-01-01 19:49 q6.b07 -> /firmware/image/q6.b07
lrwxrwxrwx root root 2011-01-01 19:49 q6.mdt -> /firmware/image/q6.mdt
-rw-r--r-- root root 46848 2012-06-07 18:17 s7020_suc.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1828_001.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1885_004.img
-rw-r--r-- root root 510300 2012-06-07 18:17 vidc_1080p.fw
drwxr-xr-x root root 2012-06-07 18:17 wcd9310
-rw-r--r-- root root 1156 2012-06-07 18:17 yamato_pfp.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 yamato_pm4.fw
however, iam not sure if this is ok or not or whatsoever. All other firmwares are in some other format so iam not sure about this. All the issues started with my TWRP wipe and during my flashing i have always used the official ROMs intended for this model.
any help or suggestion would be appreciated!
thx, Tomas
Anyone have any idea what i could do to make this working?
SOVA_SX said:
Hi,
i have a small problem a i hope someone here would be able to help me or enlighten me of what i have done wrong
I took my old Huawei Media pad s7-301u from the shelf to test if its still working or what condition he is in. The table booted normally into the system and everything seemed to be working but i have decided to hard-reset the tablet for future work. Since i had TWRP installed the system went to the recovery where i have decided to install a fresh stock ROM and therefore i have wiped all data using the recovery. After rebooting the touchscreen stopped to work, in TWRP, and overall anything. Hence, i have pushed the stock recovery into it and updated to the stock ROM using the inbuilt updater - everything went OK but the tablet was dead. After lots of trying i red somewhere that the wipe through TRWP could do something with one of the partition and thus i tried to convert them to ext2 and back to ext4 to fix the issue and truly it fixed the issue with the system and after updating the tablet went in to the system, however, the touchscreen is not working at all.
I have used the TWRP: 2.8.4.0
Stock ROM: S7-301u V100R002C232B005 ICS Android 4.0.3 General Version
What i have tried during my work was to push all the files for flash through fastboot
Code:
fastboot.exe flash modem non-hlos.bin
fastboot.exe flash sbl1 sbl1.mbn
fastboot.exe flash sbl2 sbl2.mbn
fastboot.exe flash ext oeminfo
fastboot.exe flash rpm rpm.mbn
fastboot.exe flash sbl3 sbl3.mbn
fastboot.exe flash aboot emmc_appsboot.mbn
fastboot.exe flash tz tz.mbn
fastboot.exe flash logo logo.img
fastboot.exe flash modem_st1 modem_st1.mbn
fastboot.exe flash modem_st2 modem_st2.mbn
fastboot.exe flash cust cust.img.ext4
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img.ext4
fastboot.exe flash persist persist.img.ext4
fastboot.exe flash cache cache.img.ext4
fastboot.exe flash userdata userdata.img.ext4
fastboot.exe flash tombstones tombstones.img.ext4
fastboot.exe flash recovery recovery.img
fastboot.exe flash recovery2 recovery.img
The tablet reports, after update, that the "touchscreen firmware upgrade failed" but i cant figure out why it is not working. In the log from the update is:
Code:
Huawei product info file found ......
software version is not need to check!
Huawei software version Verfying success......
hardware version is not need to check!
Huawei hardware version Verfying success......
update parti num = 26
try to update coulmeter firmware!
try to update touchscreen firmware!
Success to fork coulmeter child process!
Huawei could not found coulmeter firmware version file......
coulmeter write return 9
wait for child processes return!
sys parti num = 26, update parti num =26
partition table not change
Success to fork touchscreen child process!
start huawei_update_touchscreen_firmware
minzip: Extracted dir "/tmp/touchscreen/"
minzip: Extracted file "/tmp/touchscreen/atmel_cmi_pro.img"
minzip: Extracted file "/tmp/touchscreen/s7020_suc.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1828_001.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1885_004.img"
mzExtractRecursive return 0
touchscreen update Can't copy /tmp/touchscreen
touchscreen write return 4
update zip package has boot img
Huawei contain bootloader's img......
Huawei begin structuring the update partition list......
And the update file/pack include a folder with the "touchscreen" img, however, iam not sure why its reporting the error about "copy" which is above. Using adb i have listed some files/folders and found the img files inside etc/firmware. The files are listed with extension *.img and are four: atmel_cmi_pro.img, t1320_tm1885_004.img, t1320_tm1828_001.img a t1320_tm1828_001.img.
Code:
ls -la
-rw-r--r-- root root 3750 2012-06-07 18:17 atmel_cmi_pro.img
-rw-r--r-- root root 72020 2012-06-07 18:17 cyttsp_8660_ffa.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p2.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p3.hex
-rw-r--r-- root root 180 2012-06-07 18:17 dsps_fluid.b00
-rw-r--r-- root root 120 2012-06-07 18:17 dsps_fluid.b01
-rw-r--r-- root root 105484 2012-06-07 18:17 dsps_fluid.b02
-rw-r--r-- root root 6256 2012-06-07 18:17 dsps_fluid.b03
-rw-r--r-- root root 428 2012-06-07 18:17 dsps_fluid.mdt
-rw-r--r-- root root 1156 2012-06-07 18:17 leia_pfp_470.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 leia_pm4_470.fw
lrwxrwxrwx root root 2011-01-01 19:49 modem.b00 -> /firmware/image/modem.b00
lrwxrwxrwx root root 2011-01-01 19:49 modem.b01 -> /firmware/image/modem.b01
lrwxrwxrwx root root 2011-01-01 19:49 modem.b02 -> /firmware/image/modem.b02
lrwxrwxrwx root root 2011-01-01 19:49 modem.b03 -> /firmware/image/modem.b03
lrwxrwxrwx root root 2011-01-01 19:49 modem.b04 -> /firmware/image/modem.b04
lrwxrwxrwx root root 2011-01-01 19:49 modem.b05 -> /firmware/image/modem.b05
lrwxrwxrwx root root 2011-01-01 19:49 modem.b06 -> /firmware/image/modem.b06
lrwxrwxrwx root root 2011-01-01 19:49 modem.b07 -> /firmware/image/modem.b07
lrwxrwxrwx root root 2011-01-01 19:49 modem.b08 -> /firmware/image/modem.b08
lrwxrwxrwx root root 2011-01-01 19:49 modem.b09 -> /firmware/image/modem.b09
lrwxrwxrwx root root 2011-01-01 19:49 modem.b10 -> /firmware/image/modem.b10
lrwxrwxrwx root root 2011-01-01 19:49 modem.mdt -> /firmware/image/modem.mdt
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b00 -> /firmware/image/playrdy.b00
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b01 -> /firmware/image/playrdy.b01
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b02 -> /firmware/image/playrdy.b02
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.mdt -> /firmware/image/playrdy.mdt
lrwxrwxrwx root root 2011-01-01 19:49 q6.b00 -> /firmware/image/q6.b00
lrwxrwxrwx root root 2011-01-01 19:49 q6.b01 -> /firmware/image/q6.b01
lrwxrwxrwx root root 2011-01-01 19:49 q6.b02 -> /firmware/image/q6.b02
lrwxrwxrwx root root 2011-01-01 19:49 q6.b03 -> /firmware/image/q6.b03
lrwxrwxrwx root root 2011-01-01 19:49 q6.b04 -> /firmware/image/q6.b04
lrwxrwxrwx root root 2011-01-01 19:49 q6.b05 -> /firmware/image/q6.b05
lrwxrwxrwx root root 2011-01-01 19:49 q6.b06 -> /firmware/image/q6.b06
lrwxrwxrwx root root 2011-01-01 19:49 q6.b07 -> /firmware/image/q6.b07
lrwxrwxrwx root root 2011-01-01 19:49 q6.mdt -> /firmware/image/q6.mdt
-rw-r--r-- root root 46848 2012-06-07 18:17 s7020_suc.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1828_001.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1885_004.img
-rw-r--r-- root root 510300 2012-06-07 18:17 vidc_1080p.fw
drwxr-xr-x root root 2012-06-07 18:17 wcd9310
-rw-r--r-- root root 1156 2012-06-07 18:17 yamato_pfp.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 yamato_pm4.fw
however, iam not sure if this is ok or not or whatsoever. All other firmwares are in some other format so iam not sure about this. All the issues started with my TWRP wipe and during my flashing i have always used the official ROMs intended for this model.
any help or suggestion would be appreciated!
thx, Tomas
Anyone have any idea what i could do to make this working?
Click to expand...
Click to collapse
Hi @SOVA_SX,
Have you been able to solve your issue?
I would appreciate, if you could share the TWRP 2.8.4.0.
The touch function on my S7-301u is also broken. I used to use a mouse via an OTG-USB.
Unfortunately, I decided to update the ROM. After updating the mediapad is stuck in a bootloop ...
Thank you!
SOVA_SX said:
Hi,
i have a small problem a i hope someone here would be able to help me or enlighten me of what i have done wrong
I took my old Huawei Media pad s7-301u from the shelf to test if its still working or what condition he is in. The table booted normally into the system and everything seemed to be working but i have decided to hard-reset the tablet for future work. Since i had TWRP installed the system went to the recovery where i have decided to install a fresh stock ROM and therefore i have wiped all data using the recovery. After rebooting the touchscreen stopped to work, in TWRP, and overall anything. Hence, i have pushed the stock recovery into it and updated to the stock ROM using the inbuilt updater - everything went OK but the tablet was dead. After lots of trying i red somewhere that the wipe through TRWP could do something with one of the partition and thus i tried to convert them to ext2 and back to ext4 to fix the issue and truly it fixed the issue with the system and after updating the tablet went in to the system, however, the touchscreen is not working at all.
I have used the TWRP: 2.8.4.0
Stock ROM: S7-301u V100R002C232B005 ICS Android 4.0.3 General Version
What i have tried during my work was to push all the files for flash through fastboot
Code:
fastboot.exe flash modem non-hlos.bin
fastboot.exe flash sbl1 sbl1.mbn
fastboot.exe flash sbl2 sbl2.mbn
fastboot.exe flash ext oeminfo
fastboot.exe flash rpm rpm.mbn
fastboot.exe flash sbl3 sbl3.mbn
fastboot.exe flash aboot emmc_appsboot.mbn
fastboot.exe flash tz tz.mbn
fastboot.exe flash logo logo.img
fastboot.exe flash modem_st1 modem_st1.mbn
fastboot.exe flash modem_st2 modem_st2.mbn
fastboot.exe flash cust cust.img.ext4
fastboot.exe flash boot boot.img
fastboot.exe flash system system.img.ext4
fastboot.exe flash persist persist.img.ext4
fastboot.exe flash cache cache.img.ext4
fastboot.exe flash userdata userdata.img.ext4
fastboot.exe flash tombstones tombstones.img.ext4
fastboot.exe flash recovery recovery.img
fastboot.exe flash recovery2 recovery.img
The tablet reports, after update, that the "touchscreen firmware upgrade failed" but i cant figure out why it is not working. In the log from the update is:
Code:
Huawei product info file found ......
software version is not need to check!
Huawei software version Verfying success......
hardware version is not need to check!
Huawei hardware version Verfying success......
update parti num = 26
try to update coulmeter firmware!
try to update touchscreen firmware!
Success to fork coulmeter child process!
Huawei could not found coulmeter firmware version file......
coulmeter write return 9
wait for child processes return!
sys parti num = 26, update parti num =26
partition table not change
Success to fork touchscreen child process!
start huawei_update_touchscreen_firmware
minzip: Extracted dir "/tmp/touchscreen/"
minzip: Extracted file "/tmp/touchscreen/atmel_cmi_pro.img"
minzip: Extracted file "/tmp/touchscreen/s7020_suc.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1828_001.img"
minzip: Extracted file "/tmp/touchscreen/t1320_tm1885_004.img"
mzExtractRecursive return 0
touchscreen update Can't copy /tmp/touchscreen
touchscreen write return 4
update zip package has boot img
Huawei contain bootloader's img......
Huawei begin structuring the update partition list......
And the update file/pack include a folder with the "touchscreen" img, however, iam not sure why its reporting the error about "copy" which is above. Using adb i have listed some files/folders and found the img files inside etc/firmware. The files are listed with extension *.img and are four: atmel_cmi_pro.img, t1320_tm1885_004.img, t1320_tm1828_001.img a t1320_tm1828_001.img.
Code:
ls -la
-rw-r--r-- root root 3750 2012-06-07 18:17 atmel_cmi_pro.img
-rw-r--r-- root root 72020 2012-06-07 18:17 cyttsp_8660_ffa.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p2.hex
-rw-r--r-- root root 72538 2012-06-07 18:17 cyttsp_8660_fluid_p3.hex
-rw-r--r-- root root 180 2012-06-07 18:17 dsps_fluid.b00
-rw-r--r-- root root 120 2012-06-07 18:17 dsps_fluid.b01
-rw-r--r-- root root 105484 2012-06-07 18:17 dsps_fluid.b02
-rw-r--r-- root root 6256 2012-06-07 18:17 dsps_fluid.b03
-rw-r--r-- root root 428 2012-06-07 18:17 dsps_fluid.mdt
-rw-r--r-- root root 1156 2012-06-07 18:17 leia_pfp_470.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 leia_pm4_470.fw
lrwxrwxrwx root root 2011-01-01 19:49 modem.b00 -> /firmware/image/modem.b00
lrwxrwxrwx root root 2011-01-01 19:49 modem.b01 -> /firmware/image/modem.b01
lrwxrwxrwx root root 2011-01-01 19:49 modem.b02 -> /firmware/image/modem.b02
lrwxrwxrwx root root 2011-01-01 19:49 modem.b03 -> /firmware/image/modem.b03
lrwxrwxrwx root root 2011-01-01 19:49 modem.b04 -> /firmware/image/modem.b04
lrwxrwxrwx root root 2011-01-01 19:49 modem.b05 -> /firmware/image/modem.b05
lrwxrwxrwx root root 2011-01-01 19:49 modem.b06 -> /firmware/image/modem.b06
lrwxrwxrwx root root 2011-01-01 19:49 modem.b07 -> /firmware/image/modem.b07
lrwxrwxrwx root root 2011-01-01 19:49 modem.b08 -> /firmware/image/modem.b08
lrwxrwxrwx root root 2011-01-01 19:49 modem.b09 -> /firmware/image/modem.b09
lrwxrwxrwx root root 2011-01-01 19:49 modem.b10 -> /firmware/image/modem.b10
lrwxrwxrwx root root 2011-01-01 19:49 modem.mdt -> /firmware/image/modem.mdt
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b00 -> /firmware/image/playrdy.b00
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b01 -> /firmware/image/playrdy.b01
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.b02 -> /firmware/image/playrdy.b02
lrwxrwxrwx root root 2011-01-01 19:49 playrdy.mdt -> /firmware/image/playrdy.mdt
lrwxrwxrwx root root 2011-01-01 19:49 q6.b00 -> /firmware/image/q6.b00
lrwxrwxrwx root root 2011-01-01 19:49 q6.b01 -> /firmware/image/q6.b01
lrwxrwxrwx root root 2011-01-01 19:49 q6.b02 -> /firmware/image/q6.b02
lrwxrwxrwx root root 2011-01-01 19:49 q6.b03 -> /firmware/image/q6.b03
lrwxrwxrwx root root 2011-01-01 19:49 q6.b04 -> /firmware/image/q6.b04
lrwxrwxrwx root root 2011-01-01 19:49 q6.b05 -> /firmware/image/q6.b05
lrwxrwxrwx root root 2011-01-01 19:49 q6.b06 -> /firmware/image/q6.b06
lrwxrwxrwx root root 2011-01-01 19:49 q6.b07 -> /firmware/image/q6.b07
lrwxrwxrwx root root 2011-01-01 19:49 q6.mdt -> /firmware/image/q6.mdt
-rw-r--r-- root root 46848 2012-06-07 18:17 s7020_suc.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1828_001.img
-rw-r--r-- root root 28928 2012-06-07 18:17 t1320_tm1885_004.img
-rw-r--r-- root root 510300 2012-06-07 18:17 vidc_1080p.fw
drwxr-xr-x root root 2012-06-07 18:17 wcd9310
-rw-r--r-- root root 1156 2012-06-07 18:17 yamato_pfp.fw
-rw-r--r-- root root 9220 2012-06-07 18:17 yamato_pm4.fw
however, iam not sure if this is ok or not or whatsoever. All other firmwares are in some other format so iam not sure about this. All the issues started with my TWRP wipe and during my flashing i have always used the official ROMs intended for this model.
any help or suggestion would be appreciated!
thx, Tomas
Anyone have any idea what i could do to make this working?
Click to expand...
Click to collapse
Huawei has issues with twrp during factory reset. This happed to me too with p9. Flash the original system recovery and reset it from there.
Nicknackpaddywack101 said:
Huawei has issues with twrp during factory reset. This happed to me too with p9. Flash the original system recovery and reset it from there.
Click to expand...
Click to collapse
Yes, thats a good idea.
Actually, I was able to replace TWRP with the stock recovery and flashed the stock ROM.
The touch function is still broken. I reckon it is a HW issue rather than SW, but I can use a [email protected] USB as a work-around which is just fine for my use case.
In fact, the best thing is that I got curious and started to check more in detail again, and after approx. 8 years having the S7-301u stored away, I just noticed the CWM recovery works with the HW buttons just fine and no touch needed ( ... seems I forgot about this once I switched over to TWRP then ... )
So, I am testing the various available custom ROMs now