Related
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
A bit further: There's a chroot involved! And the adas account password is randomly set!
... Buuuuuuuuut, Motorola was smart and got rid of telnetd, etc in this production script...
See /usr/local/sbin/webtop-product.sh.
It's the script that makes the "production" webtop - and removes the fun stuff via dpkg in the process.
But here's a hint - if you can run an app within Webtop, get it to run /usr/bin/.lxterminal - they HID the terminal app.
EDIT: Hm. /usr/local/share/motorola/fireboxmake/ has some interesting readmes... on what .sh does what in /usr/local/sbin.
EDIT2: Check out what's in the OSH_tools.tgz. Motorola left a bootloader BIN in there along with some interesting flashing scripts for both Webtop and the Android side... and some interesting config files in nvflash...
Also, can I get the root filesystem for /etc/?
I have not downloaded the archive yet but did a search for RM_SM_DOCKED on google and came up with a hit elsewhere.
I can't post the link to this directly due to it being one of my first posts. It's only one of 3/4 hits on google.
I am guessing it is in the archive you posted.
Code:
#
#
on property:dev.bootcomplete=1
#
setprop ro.webtop.boot 1
#
start loadpreinstalls
#
#
on property:ro.webtop.boot=1
#
exec /system/bin/logwrapper /ubuntu.sh
#
#
on property:sys.SystemMode=RM_SM_DOCKED
#
exec /osh/etc/init.d/startX.sh
#
uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr,
Excellent work & post, have a Thanks.
It's a shame that the webtop will probably flop (and I sure as heck won't buy one for the price they're asking). Here's to hoping a dockless hack comes up.
uskr,
Great post, Thanks
labsONE said:
Also, can I get the root filesystem for /etc/?
Click to expand...
Click to collapse
http://www.usk.bz/android/etc.tar.bz2
You will notice some files are just links to /system/etc. You can find the /system dump on another thread on this forum. If you cant, let me know and I will get a link here.
Can someone take a good look at the contents of:
/usr/local/share/motorola/fireboxmake/OSH_tools.tgz
There's lots of interesting stuff in there & I am completely unfamiliar with tegra and Motorola cruft.
uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr, appreciate if you could also get us the root partition dump
Actually, sorry for not posting this before. But right after I posted the first dump I noticed that pretty much everything on the root partition is just a link to /osh, like you can see here:
Code:
lrwxrwxrwx root root 2011-02-22 23:54 lib -> /osh/lib
lrwxrwxrwx root root 2011-02-22 23:54 etc -> /osh/etc
lrwxrwxrwx root root 2011-02-22 23:54 thumb2 -> /osh/thumb2
lrwxrwxrwx root root 2011-02-22 23:54 srv -> /osh/srv
lrwxrwxrwx root root 2011-02-22 23:54 usr -> /osh/usr
lrwxrwxrwx root root 2011-02-22 23:54 media -> /osh/media
lrwxrwxrwx root root 2011-02-22 23:54 upath.sh -> /osh/upath.sh
lrwxrwxrwx root root 2011-02-22 23:54 boot -> /osh/boot
lrwxrwxrwx root root 2011-02-22 23:54 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-02-22 23:54 var -> /osh/var
lrwxrwxrwx root root 2011-02-22 23:54 root -> /osh/root
lrwxrwxrwx root root 2011-02-22 23:54 apath.sh -> /osh/apath.sh
lrwxrwxrwx root root 2011-02-22 23:54 bin -> /osh/bin
lrwxrwxrwx root root 2011-02-22 23:54 opt -> /osh/opt
lrwxrwxrwx root root 2011-02-22 23:54 selinux -> /osh/selinux
lrwxrwxrwx root root 2011-02-22 23:54 ubuntu.sh -> /osh/ubuntu.sh
lrwxrwxrwx root root 2011-02-22 23:54 lost+found -> /osh/lost+found
lrwxrwxrwx root root 2011-02-22 23:54 home -> /data/home
dr-x------ root root 2011-02-22 23:54 config
drwxrwx--- system misc 2011-02-22 23:54 misc
drwxrwx--- system cache 2011-02-23 00:58 cache
drwxr-xr-x root root 2011-01-30 05:54 pds
lrwxrwxrwx root root 2011-02-22 23:54 sdcard-ext -> /mnt/sdcard-ext
lrwxrwxrwx root root 2011-02-22 23:54 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2011-02-22 23:54 acct
lrwxrwxrwx root root 2011-02-22 23:54 tmp -> /data/tmp
drwxr-xr-x root root 2010-12-22 17:39 preinstall
drwxr-xr-x root root 2011-01-20 21:49 osh
drwxrwxr-x root system 2011-02-22 23:54 mnt
lrwxrwxrwx root root 2011-02-22 23:54 d -> /sys/kernel/debug
drwxr-xr-x root root 2011-02-05 05:07 system
drwxr-xr-x root root 1969-12-31 19:00 sys
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rwxr-x--- root root 32498 1969-12-31 19:00 init.rc
-rwxr-x--- root root 1954 1969-12-31 19:00 init.goldfish.rc
-rwxr-x--- root root 118156 1969-12-31 19:00 init
-rw-r--r-- root root 153 1969-12-31 19:00 default.prop
drwxrwx--x system system 2011-02-22 23:54 data
drwxr-xr-x root root 2011-02-22 23:54 dev
But for some reason when I dump the /osh partition, a couple of those folders come corrupted. Let me know if any of the folders you are interested are damaged on the dump and I will post a tar.bz2 like I did with /etc
Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks
transact said:
Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks
Click to expand...
Click to collapse
Have you tried wiping data again from recovery and then boot?
ishangoyal said:
Have you tried wiping data again from recovery and then boot?
Click to expand...
Click to collapse
Yeah, multiple times.
I tried to flash stock firmware back but I think system is read only now.
When I flashed stockfirmware from samfirmware also with odin and pit file, I was able to go to stock recovery but phone never booted to stock firmware. Then I flashed semaphore . this time I could see semaphore logo and then cyanogenmod animation. Seeing cyanogen animation was a surprise as it should have been wiped when i flashed stockfirmare.
I went to recovery mode again did factory reset, cache wipe, dalvik cache. Then mounted usb and copied latest nightly of 10.1 and gapps to customroms folder on my sdcard.
After copying I rebooted into recovery mode again and selected install from zip on sdcard but to my surprise the new files I copied were not there but the files I deleted were still there.
It seems like phone didn't allow me to alter content of sdcard. To test I mounted the usb storage again and created some dummy files like default.txt, default.ini and default.zip in root of sdcard and deleted some files from my backup files of fuellog folder. After unmounting and going through files on phone I discovered that new files are not there and old files are still present.
Another thing is that I have factory reset multiple times, wiped cache partition and cleared dalvik cache as well but every time I mount usb from recovery I have .android_secure folder filled with my previous apps from CM 10.0, which I think shouldn't be there after factory reset.
So I guess it is something to do with permissions. I have done 'fix permissions' multiple times but that also didn't helped.
One more thing I noticed is that after I flash CM10.1 from old file still in my sdcard, on first boot I get com.phone.android error but then on second boot I saw option to complete action using apex, nova or trebuchet laucnher behing the com.android.phone error. I think I shouldn't see that message as it is suppose to be new install with factory reset.
after I click ok on the error message, the phone reboots again but this time it stuck on cyanogen animation. it never goes past animation on 3rd boot.
I have really no idea what is happening.
Is there a way to reset everything through adb? or reset file permissions? I could access my device using adb but had no idea what I could do or not do.
File system view when phone is booting and stuck at cyanogen animation
Code:
drwxr-xr-x root root 2013-01-15 10:29 acct
-rw-r--r-- root root 614 2013-01-15 10:29 boot.txt
drwxrwx--x system cache 2013-01-15 10:29 cache
-rwxr-x--- root root 264080 2013-01-15 10:29 charger
dr-x------ root root 2013-01-15 10:29 config
lrwxrwxrwx root root 2013-01-15 10:29 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-11 17:08 data
drwxrwx--x system system 2013-01-15 10:29 datadata
-rw-r--r-- root root 163 2013-01-15 10:29 default.prop
drwxr-xr-x root root 2013-01-15 10:29 dev
drwxr-xr-x radio radio 2013-01-14 21:30 efs
lrwxrwxrwx root root 2013-01-15 10:29 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2013-01-15 10:29 etc -> /system/etc
-rw-r----- root root 568 2013-01-15 10:29 fstab.aries
-rwxr-x--- root root 109484 2013-01-15 10:29 init
-rwxr-x--- root root 555 2013-01-15 10:29 init.aries.gps.rc
-rwxr-x--- root root 5375 2013-01-15 10:29 init.aries.rc
-rwxr-x--- root root 3899 2013-01-15 10:29 init.aries.usb.rc
-rwxr-x--- root root 1238 2013-01-15 10:29 init.cm.rc
-rwxr-x--- root root 2487 2013-01-15 10:29 init.goldfish.rc
-rwxr-x--- root root 18768 2013-01-15 10:29 init.rc
-rwxr-x--- root root 1795 2013-01-15 10:29 init.trace.rc
-rwxr-x--- root root 3915 2013-01-15 10:29 init.usb.rc
-rw-r--r-- root root 340 2013-01-15 10:29 lpm.rc
drwxr-xr-x root root 2013-01-14 22:02 lvm
drwxrwxr-x root system 2013-01-15 10:29 mnt
dr-xr-xr-x root root 1970-01-01 10:00 proc
drwxr-xr-x root root 2013-01-14 21:28 radio
drwxr-xr-x root root 2013-01-15 10:29 res
drwxr-x--- root root 2013-01-15 10:29 sbin
lrwxrwxrwx root root 2013-01-15 10:29 sdcard -> /storage/sdcard0
d---r-x--- root sdcard_r 2013-01-15 10:29 storage
drwxr-xr-x root root 2013-01-15 10:29 sys
drwxr-xr-x root root 2013-01-11 17:01 system
-rw-r--r-- root root 1489 2013-01-15 10:29 ueventd.aries.rc
-rw-r--r-- root root 272 2013-01-15 10:29 ueventd.goldfish.rc
-rw-r--r-- root root 5220 2013-01-15 10:29 ueventd.rc
lrwxrwxrwx root root 2013-01-15 10:29 vendor -> /system/vendor
file system view when in recovery
Code:
drwxr-xr-x 18 root root 0 Jan 15 00:12 .
drwxr-xr-x 18 root root 0 Jan 15 00:12 ..
drwxr-xr-x 3 root root 0 Jan 15 00:12 acct
-rw-r--r-- 1 root root 586 Jan 15 00:12 boot.txt
drwxrwx--x 1 system cache 4096 Jan 14 23:29 cache
-rwxr-x--- 1 root root 264080 Jan 15 00:12 charger
dr-x------ 2 root root 0 Jan 15 00:12 config
lrwxrwxrwx 1 root root 17 Jan 15 00:12 d -> /sys/kernel/debug
drwxrwx--x 12 system system 0 Jan 15 00:12 data
-rw-r--r-- 1 root root 2887 Jan 15 00:12 default.prop
drwxr-xr-x 13 root root 3040 Jan 15 00:12 dev
drwxr-xr-x 2 root root 0 Jan 15 00:12 efs
d--------- 2 system system 0 Jan 15 00:12 emmc
drwxr-xr-x 2 root root 0 Jan 15 00:12 etc
-rw-r----- 1 root root 568 Jan 15 00:12 fstab.aries
-rwxr-x--- 1 root root 109484 Jan 15 00:12 init
-rwxr-x--- 1 root root 10349 Jan 15 00:12 init.rc
-rw-r--r-- 1 root root 340 Jan 15 00:12 lpm.rc
drwxr-xr-x 4 root root 0 Jan 14 11:02 lvm
dr-xr-xr-x 73 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 15 00:12 res
drwxr-x--- 2 root root 0 Jan 15 00:12 sbin
d--------- 2 system system 0 Jan 15 00:12 sdcard
drwxr-xr-x 12 root root 0 Jan 15 00:12 sys
drwxr-xr-x 3 root root 0 Jan 15 00:12 system
drwxr-xr-x 2 root root 0 Jan 15 00:12 tmp
-rw-r--r-- 1 root root 1489 Jan 15 00:12 ueventd.aries.rc
-rw-r--r-- 1 root root 272 Jan 15 00:12 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5220 Jan 15 00:12 ueventd.rc
-rw-r--r-- 1 root root 3899 Jan 15 00:12 usb.rc
lrwxrwxrwx 1 root root 14 Jan 15 00:12 vendor -> /system/vendor
I hope they give some kind of clue.
please help.
thanks
transact said:
Yeah, multiple times.
I hope they give some kind of clue.
please help.
thanks
Click to expand...
Click to collapse
That's a really weird and detailed explanation .. however I am unable to explain the behaviour of your phone.. what I can suggest is formating the sd card too (if you have backup of data that is) and format /system too manually along with wiping data, cache and dalvik cache.. after that flash CM10.1 nightly twice.. don't flash gapps atm.. after that reboot recovery.. wipe data, cache again (not /system this time) and flash nightly again.. fix permissions and then reboot..
I know repetition like this doesn't make much sense but nor does your problem..
Hope this will help.
if you are comeing from cm10.0 ant flashing cm10.1 it is recommend to wipe /system befor flashing
Okay, so my phone's screen broke and would no longer respond. I bought a replacement screen and disassembled it and reassembled it with a new screen. It is no longer booting and or charging. Basically, when powering on with the power button, there will be a vibrate but no response on the screen. The device is no longer recognized on my computer.
When holding down the power button for a force restart, the power buttons will flash. Then vibrate to tell be it restarted. Still nothing on the screen. When holding down the power + vol down, it will flash and not vibrate (indicating i'm in fastboot). This is where it gets weird, when using fastboot, the phone will not be recognized/detected. After rebooting a whole load of times (using fastboot devices after each restart), it will eventually detect my device. It will detect my device but the screen is still blank. So, I played around with fastboot. I updated the RUU and updated TWRP and erased cache. No dice. When restarting a whole load again, eventually it will be recognized by adb and take adb commands. Screen still blank. I tried some adb commands but nothing useful. Sideload is not working, giving "error closed", probably cause I can't put it to sideload mode cause the screen is blank. I tried using adb backup but it requires to be unlocked on the phone (which is again impossible due to blank screen). Then I tried extracting files manually. For some reason, the SDCARD is not being found (also I don't know if, or how to mount it). When plugging in to laptop or wall charger, it will give a flashing red light indicating low battery but i've charged it on wall for 3 days straight already with no change.
Here are the "fixes" i've tired:
Resetting battery logics (Power + Vol up + Vol Down)
Under bright light
Installed windows 8 drivers.
Info:
HTC One (Australia)
S-Off, unlocked, Hboot 1.57, ARHD, ElementalX, original usb cable, using a laptop with only usb 3.0 ports.
https://www.youtube.com/watch?v=jVUAr5hLiEE
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
Please help! I have photos on their from my holiday that I don't have a backup of!
The Smexican said:
Okay, so my phone's screen broke and would no longer respond. I bought a replacement screen and disassembled it and reassembled it with a new screen. It is no longer booting and or charging. Basically, when powering on with the power button, there will be a vibrate but no response on the screen. The device is no longer recognized on my computer.
Resetting battery logics (Power + Vol up + Vol Down)
Under bright light
Installed windows 8 drivers.
Info:
HTC One (Australia)
S-Off, unlocked, Hboot 1.57, ARHD, ElementalX, original usb cable, using a laptop with only usb 3.0 ports.
Please help! I have photos on their from my holiday that I don't have a backup of!
Click to expand...
Click to collapse
Try to find a computer with USB 2.0 ports. Are you sure you reassembled the phone properly? Did you inadvertently damage one of the circuits? Failing a change in computers, you might have to send it to a repair center.
Okay, I try to find a computer with USB 2.0 ports. Will it help me get stuff out of the phone via adb? What should I try when I connect it?
I was extremely careful when disassembling it, no sudden, rash movements that could have caused damage and I double checked screws and connectors to be 100% connected. I really really do not want to send it to a repair center as it will guarantee a wipe and I really don't want to lose my files :/
I'm just confused as why nothing is coming up on the screen despite being in fastboot mode. I mean, if the capacitive buttons are flashing, that means it must have:
- Power from the battery
- Connection (at least to the top board with the power button/camera/vibration motor
Oh, forgot to mention, when I boot it and leave it for a while, the CPU does get hot.
The Smexican said:
Okay, I try to find a computer with USB 2.0 ports. Will it help me get stuff out of the phone via adb? What should I try when I connect it?
I was extremely careful when disassembling it, no sudden, rash movements that could have caused damage and I double checked screws and connectors to be 100% connected. I really really do not want to send it to a repair center as it will guarantee a wipe and I really don't want to lose my files :/
I'm just confused as why nothing is coming up on the screen despite being in fastboot mode. I mean, if the capacitive buttons are flashing, that means it must have:
- Power from the battery
- Connection (at least to the top board with the power button/camera/vibration motor
Oh, forgot to mention, when I boot it and leave it for a while, the CPU does get hot.
Click to expand...
Click to collapse
Here is what one individual did when he had a blank screen: http://forum.xda-developers.com/showpost.php?p=55166141&postcount=13
Did you have USB Debugging enabled in Developer's Option? If not, then adb will not work unless the phone is in Recovery Mode.
The screen maybe damaged, was it bought new or used?
The new screen was bought first hand from Fixez, they claim it be a good as it can get. I've had my phone in recovery mode, when using the command "adb devices" it will report that it is in recovery.
I don't think it's possible for me to get to that option, after the phone is booted, when i use the volume up then down (to switch it from silent back to vibrate) it doesn't vibrate, and taking a screenshot does not play a sound.
oh, extra info.
Sometimes, when plugged into the computer, it will be sensed as a CD Rom drive and can't be browsed.
How did you break your screen? If it had taken a heavy impact damage itwill not only crack yr screen but also cause yr ph to go dead. Anything could have come loose or damaged internally.
You should have check whether it is still working, by that i mean you can still hear the phone boot sound or sometimes you can try calling and it will still ring despite not being able to see on screen.
This way u can ascertain that the phone is still ok and only need screen replacement.
I suppose its too late to tell now,
Hope u can resolve yr problem.
That is a good theory, I hit it extremely hard. It had a case on and the case was destroyed. It was combination of bad luck and timing. I was running very fast (I'm a fast runner) and it fell out of my pocket and landed on a corner of a curb. The phone was perfectly fine, no touch problems or anything, just a cracked screen. I actually used it for 4 weeks before deciding to replace it because it slowly became unresponsive, so much that I couldn't touch the numbers on the lock pad. During that time, I was also able to take photos in and out of the phone and was sensed by the laptop as it normally would.
Currently, I am not able to take any calls to that phone because I'm overseas for a long time with no sim. Well, I do but in Japan, they don't use phone calling, they use an app called Line. Some sim cards in japan do not come with a phone number so unlucky there.
Being unable to see anything onscreen makes it extremely hard to fix anything.
Further more HTC phones are a ***** to disassemble to detect chip failure unlike Samsung phones where it's all on one board. Or being easy to just switch another board over to see if yr screen works.
I think yrs is a million to one chance of reviving. Don't mean to pour cold water.
Cheers
Someone please advise what I can do. Fastboot devices is currently telling me that my phone is in fastboot. What should I do now?
-CMD-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
@majmoz Help me out here
The Smexican said:
@majmoz Help me out here
Click to expand...
Click to collapse
Sorry I am stumped, in fastboot USB there is no way to move your personal files off of the phone. If you can get it to reboot into the OS/Android with the phone connected to the PC, you might be able to copy your files from the phone.
If your able to get adb commands to work , did you try adb pull /sdcard ? I'm not 100% on the command but I kno it's something to that effect.
Okay, in recovery. Give me some commands. Willing to try anything at this point.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ # ls
ls
acct
cache
config
cwkeys
d
data
default.prop
dev
devlog
etc
file_contexts
firmware
fstab.m7
init
init.environ.rc
init.gyrocali.sh
init.network.sh
init.power.rc
init.qcom.firmware_links.sh
init.rc
init.target.rc
init.target.recovery.rc
init.trace.rc
init.usb.rc
init.usbdiag.sh
mnt
proc
property_contexts
ramdump
root
sbin
sdcard
seapp_contexts
sepolicy
storage
sys
system
tmp-mksh
tombstones
ueventd.rc
ueventd.target.rc
vendor
[email protected]:/ # exit
exit
C:\Program Files (x86)\Minimal ADB and Fastboot>adb pull sdcard
remote object 'sdcard' not a file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>adb pull /sdcard/
pull: building file list...
0 files pulled. 0 files skipped.
C:\Program Files (x86)\Minimal ADB and Fastboot>
If no-one has any ideas, can anyone tell me how to flash or load up a backup. I don't have a back up but can someone give me a stock nandroid or something?
Don't mean to be a crying baby calling for his mommy, but the lack of any response is quite demoralizing. Any response is good, please give me something to go on!
The Smexican said:
Don't mean to be a crying baby calling for his mommy, but the lack of any response is quite demoralizing. Any response is good, please give me something to go on!
Click to expand...
Click to collapse
you did the adb pull command, but looks like nothing is there.
open an adb shell
and use a combination of
cd
ls -l (that's lowercase LS -L)
to get to /data/media/0 and list the contents to see if anything is there to begin with, maybe everything was wiped?
oh and if you are using a custom recovery, also make sure /data is mounted, for example:
C:....> adb shell
mount /data
cd /data/media
ls -l
cd 0
ls -l
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ # ls -l
ls -l
drwxr-xr-x root root 2014-01-15 01:17 acct
drwxrwx--- system cache 1970-01-01 00:00 cache
dr-x------ root root 2014-01-15 01:17 config
-rw-r--r-- root root 1395 1970-01-01 00:00 cwkeys
lrwxrwxrwx root root 2014-01-15 01:17 d -> /sys/kernel/debug
drwxrwx--x system system 2014-01-15 01:17 data
-rw-r--r-- root root 331 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2014-01-15 01:17 dev
drwx------ root root 2014-01-12 03:29 devlog
lrwxrwxrwx root root 2014-01-15 01:17 etc -> /system/etc
-rw-r--r-- root root 9112 1970-01-01 00:00 file_contexts
drwxrwx--x system system 2014-01-15 01:17 firmware
-rw-r--r-- root root 507 1970-01-01 00:00 fstab.m7
-rwxr-x--- root root 217028 1970-01-01 00:00 init
-rwxr-x--- root root 1185 1970-01-01 00:00 init.environ.rc
-rwxr-x--- root root 2567 1970-01-01 00:00 init.gyrocali.sh
-rwxr-x--- root root 1797 1970-01-01 00:00 init.network.sh
-rwxr-x--- root root 4540 1970-01-01 00:00 init.power.rc
-rwxr-x--- root root 2910 1970-01-01 00:00 init.qcom.firmware_links.
sh
-rwxr-x--- root root 35445 1970-01-01 00:00 init.rc
-rwxr-x--- root root 27036 1970-01-01 00:00 init.target.rc
-rwxr-x--- root root 8218 1970-01-01 00:00 init.target.recovery.rc
-rwxr-x--- root root 2320 1970-01-01 00:00 init.trace.rc
-rwxr-x--- root root 29548 1970-01-01 00:00 init.usb.rc
-rwxr-x--- root root 2013 1970-01-01 00:00 init.usbdiag.sh
drwxrwxr-x root system 2014-01-15 01:17 mnt
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r-- root root 2161 1970-01-01 00:00 property_contexts
drwx------ root root 2014-01-15 01:17 ramdump
drwx------ root root 2014-07-28 10:55 root
drwxr-x--- root root 1970-01-01 00:00 sbin
lrwxrwxrwx root root 2014-01-15 01:17 sdcard -> /mnt/sdcard
-rw-r--r-- root root 1435 1970-01-01 00:00 seapp_contexts
-rw-r--r-- root root 76775 1970-01-01 00:00 sepolicy
drwxr-x--x root sdcard_r 2014-01-15 01:17 storage
dr-xr-xr-x root root 2014-01-15 01:17 sys
drwxr-xr-x root root 2014-08-14 13:50 system
drwxr-xr-x root root 2014-01-15 01:17 tmp-mksh
lrwxrwxrwx root root 2014-01-15 01:17 tombstones -> /data/tombs
tones
-rw-r--r-- root root 7179 1970-01-01 00:00 ueventd.rc
-rw-r--r-- root root 5504 1970-01-01 00:00 ueventd.target.rc
drwxrwx--x system system 2014-01-15 01:17 vendor
[email protected]:/ #
[email protected]:/ # mount /data
mount /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount /data/
mount /data/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount data/
mount data/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount data
mount data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # cd data
cd data
[email protected]:/data # ls -l
ls -l
dr-xr-xr-x root root 2014-01-15 01:17 DxDrm
drwxrwx--x system system 2014-01-01 03:11 app
drwx------ root root 2014-01-01 03:11 app-asec
drwxrwx--x system system 2014-01-01 03:11 app-lib
drwxrwx--x system system 2014-01-01 03:11 app-private
drwxr-xr-x media audio 2014-01-01 03:11 audio
lrwxrwxrwx root root 2014-01-01 03:11 bugreports -> /data/data/
com.android.shell/files/bugreports
drwxrwxrwx root root 2014-01-12 03:37 core
drwxrwx--x system system 2014-01-15 01:17 cryptobox
drwxrwx--x system system 2014-01-15 01:17 dalvik-cache
drwxrwx--x system system 2014-01-01 03:12 data
drwxr-x--- root log 2014-01-01 03:11 dontpanic
drwxrwx--- drm drm 2014-01-01 03:11 drm
drwxr-x--- root system 2014-01-15 01:17 efs
drwx------ system system 2014-01-01 03:11 hdcp
drwxr-x--x root root 2014-01-01 03:11 local
drwxrwx--- root root 2014-01-01 03:11 lost+found
drwxrwx--- media_rw media_rw 2014-01-15 01:17 media
drwxrwx--- mediadrm mediadrm 2014-01-01 03:11 mediadrm
drwxrwx--t system misc 2014-01-01 03:11 misc
drwx------ root root 2014-01-15 01:17 property
drwxr-x--- root system 2014-01-15 01:17 qcks
drwxrws--- radio radio 2014-01-01 03:11 radio
drwxrwx--x system system 2014-01-01 03:11 resource-cache
drwxr-xr-x system system 2014-01-01 03:11 secure
drwx--x--x system system 2014-01-01 03:11 security
-rw-r--r-- root root 240 2014-01-15 01:17 sqlite.log
drwxr-x--- root shell 2014-01-01 03:11 ssh
drwxrwxr-x system system 2014-01-15 01:17 system
drwxrwx--x system system 2014-01-06 23:09 tombstones
drwx--x--x system system 2014-01-01 03:11 user
[email protected]:/data # cd data/media
cd data/media
/system/bin/sh: cd: /data/data/media: No such file or directory
2|[email protected]:/data # cd media
cd media
[email protected]:/data/media # ls -l
ls -l
drwxrwx--- media_rw media_rw 2014-01-01 03:11 0
drwxrwx--- media_rw media_rw 2014-01-01 03:11 obb
[email protected]:/data/media # cd 0
cd 0
[email protected]:/data/media/0 # ls -l
ls -l
drwxrwxr-x media_rw media_rw 2014-01-01 03:11 obb
[email protected]:/data/media/0 #
Same thing happened to me.
The Smexican said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
2|[email protected]:/data # cd media
cd media
[email protected]:/data/media # ls -l
ls -l
drwxrwx--- media_rw media_rw 2014-01-01 03:11 0
drwxrwx--- media_rw media_rw 2014-01-01 03:11 obb
[email protected]:/data/media # cd 0
cd 0
[email protected]:/data/media/0 # ls -l
ls -l
drwxrwxr-x media_rw media_rw 2014-01-01 03:11 obb
[email protected]:/data/media/0 #
Click to expand...
Click to collapse
looks like nothing is there anymore
not even sure why you have an obb directory in /data/media/0
my output for example:
Code:
C:\ADB2>adb shell
[email protected]/# cd /data/media
cd /data/media
[email protected]/data/media# ls -l
ls -l
drwxrwx--- media_rw media_rw 2014-11-05 09:42 0
drwxrwxr-x media_rw media_rw 2014-05-31 20:04 legacy
drwxrwxr-x media_rw media_rw 2014-11-05 17:53 obb
[email protected]/data/media# cd 0
cd 0
[email protected]/data/media/0# ls -l
ls -l
drwxrwxr-x media_rw media_rw 2014-10-05 17:24 001
drwxrwxr-x media_rw media_rw 2014-11-03 17:34 0NKK
drwxrwxr-x media_rw media_rw 2014-09-04 10:16 AI Factory Stats
drwxrwxr-x media_rw media_rw 2014-05-31 20:04 Alarms
drwxrwxr-x media_rw media_rw 2014-05-31 20:05 Android
-rw-rw-r-- media_rw media_rw 380 2014-11-03 17:00 AppSettings-Backup.xml
drwxrwxr-x media_rw media_rw 2014-11-03 17:04 CallLogBackupRestore
drwxrwxr-x media_rw media_rw 2014-10-29 18:08 DCIM
drwxrwxr-x media_rw media_rw 2014-10-23 13:27 Documents
drwxrwxr-x media_rw media_rw 2014-11-06 13:32 Download
drwxrwxr-x media_rw media_rw 2014-11-04 12:37 LazyList
drwxrwxr-x media_rw media_rw 2014-09-04 10:29 MdotMTempCache
drwxrwxr-x media_rw media_rw 2014-06-01 15:11 Media
drwxrwxr-x media_rw media_rw 2014-05-31 20:04 Movies
drwxrwxr-x media_rw media_rw 2014-06-01 15:11 Music
drwxrwxr-x media_rw media_rw 2014-06-09 09:21 MxBrowser
drwxrwxr-x media_rw media_rw 2014-09-04 10:24 Nandroid_Manager
drwxrwxr-x media_rw media_rw 2014-09-04 10:24 NetworkSignal
drwxrwxr-x media_rw media_rw 2014-05-31 20:04 Notifications
-rw-rw-r-- media_rw media_rw 4320 2014-11-04 12:42 PPLog.txt
drwxrwxr-x media_rw media_rw 2014-10-26 22:22 Photo Grid
drwxrwxr-x media_rw media_rw 2014-10-25 19:12 Pictures
drwxrwxr-x media_rw media_rw 2014-05-31 20:04 Podcasts
drwxrwxr-x media_rw media_rw 2014-05-31 20:04 Ringtones
drwxrwxr-x media_rw media_rw 2014-11-03 17:04 SMSBackupRestore
drwxrwxr-x media_rw media_rw 2014-10-03 16:03 SeagateMedia
drwxrwxr-x media_rw media_rw 2014-11-03 16:59 SenseToolbox
drwxrwxr-x media_rw media_rw 2014-10-08 17:53 SynchronizeUltimate
drwxrwxr-x media_rw media_rw 2014-11-04 07:49 Syntomo
drwxrwxrwx root root 2014-06-09 18:14 TWRP
drwxrwxr-x media_rw media_rw 2014-11-03 17:22 TitaniumBackup
drwxrwxr-x media_rw media_rw 2014-09-04 10:31 TuneIn Radio
drwxrwxr-x media_rw media_rw 2014-11-03 22:27 TunnyBrowser
drwxrwxr-x media_rw media_rw 2014-07-29 23:20 TurboIRC
drwxrwxr-x media_rw media_rw 2014-07-24 15:11 VPlayer
drwxrwxrwx root root 2014-11-04 15:17 Venom
drwxrwxr-x media_rw media_rw 2014-10-25 21:55 Video
drwxrwxr-x media_rw media_rw 2014-06-01 14:55 Video Highlight
drwxrwxr-x media_rw media_rw 2014-06-02 18:34 VideoDieter
drwxrwxr-x media_rw media_rw 2014-05-31 20:18 WhatsApp
drwxrwxr-x media_rw media_rw 2014-06-01 14:52 WineScans
drwxrwxr-x media_rw media_rw 2014-05-31 20:05 _nero_sync
drwxrwxr-x media_rw media_rw 2014-09-01 17:35 airdroid
-rw-rw-r-- media_rw media_rw 3656 2014-09-12 14:56 awb_cal_test
drwxrwxr-x media_rw media_rw 2014-09-27 14:33 backups
drwxrwxr-x media_rw media_rw 2014-10-17 15:21 baidu
drwxrwxr-x media_rw media_rw 2014-05-31 20:20 data
drwxrwxr-x media_rw media_rw 2014-06-01 15:13 downloads
-rw-rw-r-- media_rw media_rw 220 2014-06-24 21:24 functiontestlog.txt
-rw-rw-r-- media_rw media_rw 335320 2014-09-30 13:17 iCare_share.jpg
drwxrwxr-x media_rw media_rw 2014-05-31 23:54 jorte
drwxrwxr-x media_rw media_rw 2014-10-15 16:16 lastpass
drwxrwxr-x media_rw media_rw 2014-05-31 20:47 mdm
drwxrwx--- root root 2014-11-04 15:12 multirom
-rwxrwxrwx root root 115111 2014-10-05 21:34 multirom_log.txt
drwxrwxr-x media_rw media_rw 2014-09-08 20:52 net.andchat
-rw-rw-r-- media_rw media_rw 38 2014-05-31 20:05 nmdsdcid
drwxrwxr-x media_rw media_rw 2014-09-11 15:51 osmand
drwxrwxr-x media_rw media_rw 2014-11-03 22:27 pnr_report
-rwxr-xr-x root root 110837 2014-09-30 17:35 recovery.log
drwxrwxr-x media_rw media_rw 2014-05-31 20:17 rerware
drwxrwxr-x media_rw media_rw 2014-08-10 13:03 roidapp
-rw-rw-r-- media_rw media_rw 13514 2014-10-06 11:04 romic_firefox.png
-rw-rw-rw- root root 110742 2014-11-03 18:57 sideload.zip.log.txt
drwxrwxr-x media_rw media_rw 2014-11-04 14:08 temp
So how about reviving it? Any ideas? Being able to access adb and fastboot must lead somewhere :/
Thanks to @miau9202 I just finished an automated script for installing Xposed Framework on ZE500KL and on ZE500KG
Prerequisite:
>Root
>BusyBox Installed
>ADB driver installed(old method only, but you'll have them from root)
>USB debugging activated in 'Developer Settings' (old method only)
NEW METHOD
Right now, the best way to flash xposed now is to download and install the TWRP recovery from HERE and then reboot in to it and flash the official xposed zip you can find HERE (It's important to download the sdk21-arm64 version, so check twice)
OLD METHOD
How To:
>Connect your phone while switched on to your pc
>Run "InstallXposedInstaller.bat" first (Optional: you can download it yourself and install by hand, this is just to make thing faster)
>Run "InstallXposedFramework.bat" second
-You need to press a button after each passage, to proceed. This is done for debugging purpose, so that if you have an error you have the possibility to copy it
-NOTE: the error "WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "gz
ip"; caused by library "libsigchain.so" not found" is NORMAL, you can simply ignore it and proceed
Your phone will reboot and after a while (it coul require even 10 minutes), it should appear the "Android Upgrade" pop-up.
Wait for him to complete and then you are ready to go!
Download:
Official Version - for .118
Unofficial Shakalaca Version - for .156
Manual Procedure:
If you prefer (or need) to manually insert the commands, here you a re a copy-paste friendly transcription:
adb shell
su
mount -o remount,rw /
mount -o remount,rw /system
mkdir /system/tmp
mkdir /sdcard/tmp2
exit
adb push assets/xposed-sdk21-arm64 /sdcard/tmp2
adb shell
su
cp -r /sdcard/tmp2/* /system/tmp/
chmod -R 777 /system/tmp
chmod 777 /system/tmp/flash-script.sh
./system/tmp/flash-script.sh
rm -rd /sdcard/tmp2
rm -rd /system/tmp
exit
adb reboot
Click to expand...
Click to collapse
Tested Modules:
Code:
Snapprefs - NOT Working (Bootloop)
XInternalSD - NOT Working (Bootloop)
BootManager - Working
Intelli3g - Working
PowerNap - Working
VolumeSteps+ - Working
YoutubeAdaway - Working
Disclaimer:
This tool could stuck your phone in a bootloop.
I'm not responsible nor accountable for any possible damage, loss of data or any problem could appear on your phone.
Use this tool at your own risk
Update:
15/11/2015 - Updated guide and binary for last asus update (12.8.5.156), thanks to @shakalaca, @rajlko, @96DANGER96 and @berkobra
13/02/2016 - Updated with the TWRP method
Need Xposed for ZE500KG
Some body can help me to send link Xposed for ZE500KG.
Thanks..
cannyvio said:
Some body can help me to send link Xposed for ZE500KG.
Thanks..
Click to expand...
Click to collapse
Since root procedure is the same and the phones are very look-alike.
I suppose that the same package sould work even on ZE500KG
Give it a try and report here the result
Thanks for the effort, I'll try this.
I have this error running your script:
tmp-mksh: ./flash-script.sh: not found
so tried manually, but encountered an error when starting the install script, here the entire log:
Code:
C:\Users\luca.bosso\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ $ su -c mount -o remount,rw /system
su -c mount -o remount,rw /system
[email protected]_Z00E_1:/ $ su -c mkdir /system/tmp
su -c mkdir /system/tmp
mkdir failed for /system/tmp, File exists
255|[email protected]_Z00E_1:/ $ su -c mkdir /sdcard/tmp2
su -c mkdir /sdcard/tmp2
mkdir failed for /sdcard/tmp2, File exists
255|[email protected]_Z00E_1:/ $ su -c chmod 777 /system/tmp
su -c chmod 777 /system/tmp
[email protected]_Z00E_1:/ $ exit
exit
C:\Users\luca.bosso\Desktop\Xposed ZE500KL>adb push assets/xposed-sdk21-arm64 /
dcard/tmp2
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/updater-script -> /
dcard/tmp2/META-INF/com/google/android/updater-script
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/update-binary -> /s
card/tmp2/META-INF/com/google/android/update-binary
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/flash-script.sh ->
sdcard/tmp2/META-INF/com/google/android/flash-script.sh
push: assets/xposed-sdk21-arm64/META-INF/MANIFEST.MF -> /sdcard/tmp2/META-INF/M
NIFEST.MF
push: assets/xposed-sdk21-arm64/META-INF/CERT.SF -> /sdcard/tmp2/META-INF/CERT.
F
push: assets/xposed-sdk21-arm64/META-INF/CERT.RSA -> /sdcard/tmp2/META-INF/CERT
RSA
push: assets/xposed-sdk21-arm64/system/bin/patchoat -> /sdcard/tmp2/system/bin/
atchoat
push: assets/xposed-sdk21-arm64/system/bin/oatdump -> /sdcard/tmp2/system/bin/o
tdump
push: assets/xposed-sdk21-arm64/system/bin/dex2oat -> /sdcard/tmp2/system/bin/d
x2oat
push: assets/xposed-sdk21-arm64/system/bin/app_process64_xposed -> /sdcard/tmp2
system/bin/app_process64_xposed
push: assets/xposed-sdk21-arm64/system/bin/app_process32_xposed -> /sdcard/tmp2
system/bin/app_process32_xposed
push: assets/xposed-sdk21-arm64/system/framework/XposedBridge.jar -> /sdcard/tm
2/system/framework/XposedBridge.jar
push: assets/xposed-sdk21-arm64/system/lib/libxposed_art.so -> /sdcard/tmp2/sys
em/lib/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib/libsigchain.so -> /sdcard/tmp2/syste
/lib/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib/libart.so -> /sdcard/tmp2/system/lib
libart.so
push: assets/xposed-sdk21-arm64/system/lib/libart-compiler.so -> /sdcard/tmp2/s
stem/lib/libart-compiler.so
push: assets/xposed-sdk21-arm64/system/lib64/libxposed_art.so -> /sdcard/tmp2/s
stem/lib64/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib64/libsigchain.so -> /sdcard/tmp2/sys
em/lib64/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib64/libart.so -> /sdcard/tmp2/system/l
b64/libart.so
push: assets/xposed-sdk21-arm64/system/lib64/libart-disassembler.so -> /sdcard/
mp2/system/lib64/libart-disassembler.so
push: assets/xposed-sdk21-arm64/system/xposed.prop -> /sdcard/tmp2/system/xpose
.prop
push: assets/xposed-sdk21-arm64/flash-script.sh -> /sdcard/tmp2/flash-script.sh
22 files pushed. 0 files skipped.
5543 KB/s (12807304 bytes in 2.256s)
C:\Users\luca.bosso\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c cp -r /sdcard/tmp2/* /system/tmp/
su -c cp -r /sdcard/tmp2/* /system/tmp/
[email protected]_Z00E_1:/ $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ $ dir
dir
/system/bin/sh: dir: not found
127|[email protected]_Z00E_1:/ $ ls -la
ls -la
drwxrwxr-x system system 2015-01-01 01:01 ADF
drwxrwxr-x system system 1970-01-01 01:00 APD
drwxr-xr-x root system 2015-10-28 09:55 Removable
drwxr-xr-x root root 1970-02-14 02:30 acct
drwxrwxrwx root root 2015-10-27 17:30 asdf
drwxrwxr-x system system 1970-01-01 01:00 asusfw
drwxr-xr-x root root 1970-01-01 01:00 bin
drwxrwx--- system cache 2015-10-27 15:05 cache
lrwxrwxrwx root root 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ root root 1970-02-14 02:30 config
lrwxrwxrwx root root 1970-02-14 02:30 d -> /sys/kernel/debug
drwxrwx--x system system 2015-10-21 17:25 data
-rw-r--r-- root root 363 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2015-10-28 09:55 dev
lrwxrwxrwx root root 1970-02-14 02:30 etc -> /system/etc
drwxrwxrwx shell shell 1970-01-01 05:04 factory
-rw-r--r-- root root 36566 1970-01-01 01:00 file_contexts
dr-xr-x--- system system 1970-01-01 01:00 firmware
-rw-r----- root root 922 1970-01-01 01:00 fstab.goldfish
-rw-r----- root root 1063 1970-01-01 01:00 fstab.qcom
-rwxr-x--- root root 408616 1970-01-01 01:00 init
-rwxr-x--- root root 3058 1970-01-01 01:00 init.asus.debugtool.rc
-rwxr-x--- root root 15324 1970-01-01 01:00 init.asus.rc
-rwxr-x--- root root 1577 1970-01-01 01:00 init.asus.thermald.rc
-rwxr-x--- root root 13380 1970-01-01 01:00 init.asus.usb.rc
-rwxr-x--- root root 3265 1970-01-01 01:00 init.class_main.sh
-rwxr-x--- root root 1178 1970-01-01 01:00 init.environ.rc
-rwxr-x--- root root 2836 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 1730 1970-01-01 01:00 init.mdm.sh
-rwxr-x--- root root 7054 1970-01-01 01:00 init.qcom.class_core.sh
-rwxr-x--- root root 6920 1970-01-01 01:00 init.qcom.early_boot.sh
-rwxr-x--- root root 12878 1970-01-01 01:00 init.qcom.factory.sh
-rwxr-x--- root root 31160 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- root root 6987 1970-01-01 01:00 init.qcom.sh
-rwxr-x--- root root 2965 1970-01-01 01:00 init.qcom.syspart_fixup.
h
-rwxr-x--- root root 60593 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- root root 10516 1970-01-01 01:00 init.qcom.usb.sh
-rwxr-x--- root root 24085 1970-01-01 01:00 init.rc
-rwxr-x--- root root 7223 1970-01-01 01:00 init.target.rc
-rwxr-x--- root root 1927 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 3910 1970-01-01 01:00 init.usb.rc
-rwxr-x--- root root 301 1970-01-01 01:00 init.zygote32.rc
-rwxr-x--- root root 531 1970-01-01 01:00 init.zygote64_32.rc
drwxrwxr-x root system 1970-02-14 02:30 mnt
drwxrwx--x system system 1970-01-01 01:00 persist
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2832 1970-01-01 01:00 property_contexts
drwxr-xr-x root root 1970-01-01 01:00 res
drwx------ root root 2015-09-15 07:03 root
drwxr-x--- root root 1970-01-01 01:00 sbin
lrwxrwxrwx root root 1970-02-14 02:30 sdcard -> /storage/emula
ed/legacy
-rw-r--r-- root root 746 1970-01-01 01:00 seapp_contexts
-rw-r--r-- root root 76 1970-01-01 01:00 selinux_version
-rw-r--r-- root root 187085 1970-01-01 01:00 sepolicy
-rw-r--r-- root root 10475 1970-01-01 01:00 service_contexts
drwxr-x--x root sdcard_r 1970-02-14 02:30 storage
dr-xr-xr-x root root 1970-02-14 02:30 sys
drwxr-xr-x root root 2015-10-28 09:56 system
drwxr-xr-x root root 2015-10-28 09:55 tmp-mksh
lrwxrwxrwx root root 1970-02-14 02:30 tombstones -> /data/tomb
tones
-rw-r--r-- root root 323 1970-01-01 01:00 ueventd.goldfish.rc
-rw-r--r-- root root 11724 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- root root 4546 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 1970-02-14 02:30 vendor -> /system/vendor
-rw-r--r-- root root 524 1970-01-01 01:00 verity_key
[email protected]_Z00E_1:/ $ ls -la tmp-mksh
ls -la tmp-mksh
-rwxr-xr-x root root 285016 2015-10-28 09:55 tmp-mksh
[email protected]_Z00E_1:/ $ ls -la system/tmp
ls -la system/tmp
drwxrwx--- root root 2015-10-28 09:57 META-INF
-rw------- root root 5602 2015-10-28 10:05 flash-script.sh
drwxrwx--- root root 2015-10-28 09:57 system
[email protected]_Z00E_1:/ $ cp system/tmp/flash-script.sh tmp-mksh
cp system/tmp/flash-script.sh tmp-mksh
cp: system/tmp/flash-script.sh: Permission denied
1|[email protected]_Z00E_1:/ $ cd system/tmp
cd system/tmp
[email protected]_Z00E_1:/system/tmp $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/system/tmp $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/system/tmp $ su
su
[email protected]_Z00E_1:/system/tmp # ./flash-script.sh
./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/system/tmp #
C:\Users\luca.bosso\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ $ chmod 777 tmp-mksh
chmod 777 tmp-mksh
Unable to chmod tmp-mksh: Read-only file system
10|[email protected]_Z00E_1:/ $ su
su
[email protected]_Z00E_1:/ # mount -o remount,rw /tmp-mksh
mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # mount -o remount,rw /
mount -o remount,rw /
[email protected]_Z00E_1:/ # su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ # su -c mount -o remount,rw /tmp-mksh
su -c mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # shell
shell
tmp-mksh: shell: not found
127|[email protected]_Z00E_1:/ # su -c mount -o remount,rw /tmp-mksh
su -c mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # su -c mount -o remount,rw /tmp-mksh
su -c mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # su -c mount -o remount,rw /system
su -c mount -o remount,rw /system
[email protected]_Z00E_1:/ # su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ # chmod 777 tmp-mksh
chmod 777 tmp-mksh
[email protected]_Z00E_1:/ # su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ # su -c cp system/tmp/flash-script.sh /tmp-mksh
su -c cp system/tmp/flash-script.sh /tmp-mksh
[email protected]_Z00E_1:/ # su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ # ls -la /tmp-mksh
ls -la /tmp-mksh
-rw------- root root 5602 2015-10-28 10:16 flash-script.sh
-rwxr-xr-x root root 285016 2015-10-28 09:55 tmp-mksh
[email protected]_Z00E_1:/ # shell
shell
tmp-mksh: shell: not found
127|[email protected]_Z00E_1:/ # cd tmp-mksh
cd tmp-mksh
[email protected]_Z00E_1:/tmp-mksh # ./flash-script.sh
./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/tmp-mksh # chmod 777 flash-script.sh
chmod 777 flash-script.sh
[email protected]_Z00E_1:/tmp-mksh # ./flash-script.sh
./flash-script.sh
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
./flash-script.sh[113]: head: not found
./flash-script.sh[113]: sed: not found
./flash-script.sh[115]: cut: not found
./flash-script.sh[115]: head: not found
./flash-script.sh[115]: sed: not found
./flash-script.sh[116]: cut: not found
./flash-script.sh[116]: sed: not found
./flash-script.sh[116]: head: not found
./flash-script.sh[117]: head: not found
./flash-script.sh[117]: sed: not found
./flash-script.sh[119]: head: not found
./flash-script.sh[119]: sed: not found
./flash-script.sh[120]: sed: not found
./flash-script.sh[120]: head: not found
./flash-script.sh[121]: sed: not found
./flash-script.sh[121]: head: not found
./flash-script.sh[122]: head: not found
./flash-script.sh[122]: sed: not found
Xposed version:
! Wrong platform: arm
! This file is for:
! Please download the correct package
! for your platform/ROM!
1|[email protected]_Z00E_1:/tmp-mksh # ./flash-script.sh
Xposed ZE500KG
Jhyrachy said:
Since root procedure is the same and the phones are very look-alike.
I suppose that the same package sould work even on ZE500KG
Give it a try and report here the result
Click to expand...
Click to collapse
I already installed xposed on ZE500KG but still can not because framework didn't active in xposed
when i installed error "tmp-mksh: ./flash-script.sh: not found
Thanks.
cannyvio said:
I already installed xposed on ZE500KG but still can not because framework didn't active in xposed
when i installed error "tmp-mksh: ./flash-script.sh: not found
Thanks.
Click to expand...
Click to collapse
Had the same problem, I successfully installed xposed but I'm also having problem with
tmp-mksh: ./flash-script.sh: not found.... We hope we'll have update to fix this. Thank you and God bless
96DANGER96 said:
I have this error running your script:
tmp-mksh: ./flash-script.sh: not found
so tried manually, but encountered an error when starting the install script, here the entire log:
Code:
C:\Users\*************\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ $ su -c mount -o remount,rw /system
su -c mount -o remount,rw /system
[email protected]_Z00E_1:/ $ su -c mkdir /system/tmp
su -c mkdir /system/tmp
mkdir failed for /system/tmp, File exists
255|[email protected]_Z00E_1:/ $ su -c mkdir /sdcard/tmp2
su -c mkdir /sdcard/tmp2
mkdir failed for /sdcard/tmp2, File exists
255|[email protected]_Z00E_1:/ $ su -c chmod 777 /system/tmp
su -c chmod 777 /system/tmp
[email protected]_Z00E_1:/ $ exit
exit
C:\Users\***********\Desktop\Xposed ZE500KL>adb push assets/xposed-sdk21-arm64 /
dcard/tmp2
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/updater-script -> /
dcard/tmp2/META-INF/com/google/android/updater-script
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/update-binary -> /s
card/tmp2/META-INF/com/google/android/update-binary
push: assets/xposed-sdk21-arm64/META-INF/com/google/android/flash-script.sh ->
sdcard/tmp2/META-INF/com/google/android/flash-script.sh
push: assets/xposed-sdk21-arm64/META-INF/MANIFEST.MF -> /sdcard/tmp2/META-INF/M
NIFEST.MF
push: assets/xposed-sdk21-arm64/META-INF/CERT.SF -> /sdcard/tmp2/META-INF/CERT.
F
push: assets/xposed-sdk21-arm64/META-INF/CERT.RSA -> /sdcard/tmp2/META-INF/CERT
RSA
push: assets/xposed-sdk21-arm64/system/bin/patchoat -> /sdcard/tmp2/system/bin/
atchoat
push: assets/xposed-sdk21-arm64/system/bin/oatdump -> /sdcard/tmp2/system/bin/o
tdump
push: assets/xposed-sdk21-arm64/system/bin/dex2oat -> /sdcard/tmp2/system/bin/d
x2oat
push: assets/xposed-sdk21-arm64/system/bin/app_process64_xposed -> /sdcard/tmp2
system/bin/app_process64_xposed
push: assets/xposed-sdk21-arm64/system/bin/app_process32_xposed -> /sdcard/tmp2
system/bin/app_process32_xposed
push: assets/xposed-sdk21-arm64/system/framework/XposedBridge.jar -> /sdcard/tm
2/system/framework/XposedBridge.jar
push: assets/xposed-sdk21-arm64/system/lib/libxposed_art.so -> /sdcard/tmp2/sys
em/lib/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib/libsigchain.so -> /sdcard/tmp2/syste
/lib/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib/libart.so -> /sdcard/tmp2/system/lib
libart.so
push: assets/xposed-sdk21-arm64/system/lib/libart-compiler.so -> /sdcard/tmp2/s
stem/lib/libart-compiler.so
push: assets/xposed-sdk21-arm64/system/lib64/libxposed_art.so -> /sdcard/tmp2/s
stem/lib64/libxposed_art.so
push: assets/xposed-sdk21-arm64/system/lib64/libsigchain.so -> /sdcard/tmp2/sys
em/lib64/libsigchain.so
push: assets/xposed-sdk21-arm64/system/lib64/libart.so -> /sdcard/tmp2/system/l
b64/libart.so
push: assets/xposed-sdk21-arm64/system/lib64/libart-disassembler.so -> /sdcard/
mp2/system/lib64/libart-disassembler.so
push: assets/xposed-sdk21-arm64/system/xposed.prop -> /sdcard/tmp2/system/xpose
.prop
push: assets/xposed-sdk21-arm64/flash-script.sh -> /sdcard/tmp2/flash-script.sh
22 files pushed. 0 files skipped.
5543 KB/s (12807304 bytes in 2.256s)
C:\Users\**************\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c cp -r /sdcard/tmp2/* /system/tmp/
su -c cp -r /sdcard/tmp2/* /system/tmp/
[email protected]_Z00E_1:/ $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ $ dir
dir
/system/bin/sh: dir: not found
127|[email protected]_Z00E_1:/ $ ls -la
ls -la
drwxrwxr-x system system 2015-01-01 01:01 ADF
drwxrwxr-x system system 1970-01-01 01:00 APD
drwxr-xr-x root system 2015-10-28 09:55 Removable
drwxr-xr-x root root 1970-02-14 02:30 acct
drwxrwxrwx root root 2015-10-27 17:30 asdf
drwxrwxr-x system system 1970-01-01 01:00 asusfw
drwxr-xr-x root root 1970-01-01 01:00 bin
drwxrwx--- system cache 2015-10-27 15:05 cache
lrwxrwxrwx root root 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ root root 1970-02-14 02:30 config
lrwxrwxrwx root root 1970-02-14 02:30 d -> /sys/kernel/debug
drwxrwx--x system system 2015-10-21 17:25 data
-rw-r--r-- root root 363 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2015-10-28 09:55 dev
lrwxrwxrwx root root 1970-02-14 02:30 etc -> /system/etc
drwxrwxrwx shell shell 1970-01-01 05:04 factory
-rw-r--r-- root root 36566 1970-01-01 01:00 file_contexts
dr-xr-x--- system system 1970-01-01 01:00 firmware
-rw-r----- root root 922 1970-01-01 01:00 fstab.goldfish
-rw-r----- root root 1063 1970-01-01 01:00 fstab.qcom
-rwxr-x--- root root 408616 1970-01-01 01:00 init
-rwxr-x--- root root 3058 1970-01-01 01:00 init.asus.debugtool.rc
-rwxr-x--- root root 15324 1970-01-01 01:00 init.asus.rc
-rwxr-x--- root root 1577 1970-01-01 01:00 init.asus.thermald.rc
-rwxr-x--- root root 13380 1970-01-01 01:00 init.asus.usb.rc
-rwxr-x--- root root 3265 1970-01-01 01:00 init.class_main.sh
-rwxr-x--- root root 1178 1970-01-01 01:00 init.environ.rc
-rwxr-x--- root root 2836 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 1730 1970-01-01 01:00 init.mdm.sh
-rwxr-x--- root root 7054 1970-01-01 01:00 init.qcom.class_core.sh
-rwxr-x--- root root 6920 1970-01-01 01:00 init.qcom.early_boot.sh
-rwxr-x--- root root 12878 1970-01-01 01:00 init.qcom.factory.sh
-rwxr-x--- root root 31160 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- root root 6987 1970-01-01 01:00 init.qcom.sh
-rwxr-x--- root root 2965 1970-01-01 01:00 init.qcom.syspart_fixup.
h
-rwxr-x--- root root 60593 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- root root 10516 1970-01-01 01:00 init.qcom.usb.sh
-rwxr-x--- root root 24085 1970-01-01 01:00 init.rc
-rwxr-x--- root root 7223 1970-01-01 01:00 init.target.rc
-rwxr-x--- root root 1927 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 3910 1970-01-01 01:00 init.usb.rc
-rwxr-x--- root root 301 1970-01-01 01:00 init.zygote32.rc
-rwxr-x--- root root 531 1970-01-01 01:00 init.zygote64_32.rc
drwxrwxr-x root system 1970-02-14 02:30 mnt
drwxrwx--x system system 1970-01-01 01:00 persist
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2832 1970-01-01 01:00 property_contexts
drwxr-xr-x root root 1970-01-01 01:00 res
drwx------ root root 2015-09-15 07:03 root
drwxr-x--- root root 1970-01-01 01:00 sbin
lrwxrwxrwx root root 1970-02-14 02:30 sdcard -> /storage/emula
ed/legacy
-rw-r--r-- root root 746 1970-01-01 01:00 seapp_contexts
-rw-r--r-- root root 76 1970-01-01 01:00 selinux_version
-rw-r--r-- root root 187085 1970-01-01 01:00 sepolicy
-rw-r--r-- root root 10475 1970-01-01 01:00 service_contexts
drwxr-x--x root sdcard_r 1970-02-14 02:30 storage
dr-xr-xr-x root root 1970-02-14 02:30 sys
drwxr-xr-x root root 2015-10-28 09:56 system
drwxr-xr-x root root 2015-10-28 09:55 tmp-mksh
lrwxrwxrwx root root 1970-02-14 02:30 tombstones -> /data/tomb
tones
-rw-r--r-- root root 323 1970-01-01 01:00 ueventd.goldfish.rc
-rw-r--r-- root root 11724 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- root root 4546 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 1970-02-14 02:30 vendor -> /system/vendor
-rw-r--r-- root root 524 1970-01-01 01:00 verity_key
[email protected]_Z00E_1:/ $ ls -la tmp-mksh
ls -la tmp-mksh
-rwxr-xr-x root root 285016 2015-10-28 09:55 tmp-mksh
[email protected]_Z00E_1:/ $ ls -la system/tmp
ls -la system/tmp
drwxrwx--- root root 2015-10-28 09:57 META-INF
-rw------- root root 5602 2015-10-28 10:05 flash-script.sh
drwxrwx--- root root 2015-10-28 09:57 system
[email protected]_Z00E_1:/ $ cp system/tmp/flash-script.sh tmp-mksh
cp system/tmp/flash-script.sh tmp-mksh
cp: system/tmp/flash-script.sh: Permission denied
1|[email protected]_Z00E_1:/ $ cd system/tmp
cd system/tmp
[email protected]_Z00E_1:/system/tmp $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/system/tmp $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/system/tmp $ su
su
[email protected]_Z00E_1:/system/tmp # ./flash-script.sh
./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/system/tmp #
C:\Users\**********\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ $ chmod 777 tmp-mksh
chmod 777 tmp-mksh
Unable to chmod tmp-mksh: Read-only file system
10|[email protected]_Z00E_1:/ $ su
su
[email protected]_Z00E_1:/ # mount -o remount,rw /tmp-mksh
mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # mount -o remount,rw /
mount -o remount,rw /
[email protected]_Z00E_1:/ # su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ # su -c mount -o remount,rw /tmp-mksh
su -c mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # shell
shell
tmp-mksh: shell: not found
127|[email protected]_Z00E_1:/ # su -c mount -o remount,rw /tmp-mksh
su -c mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # su -c mount -o remount,rw /tmp-mksh
su -c mount -o remount,rw /tmp-mksh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]_Z00E_1:/ # su -c mount -o remount,rw /system
su -c mount -o remount,rw /system
[email protected]_Z00E_1:/ # su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ # chmod 777 tmp-mksh
chmod 777 tmp-mksh
[email protected]_Z00E_1:/ # su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ # su -c cp system/tmp/flash-script.sh /tmp-mksh
su -c cp system/tmp/flash-script.sh /tmp-mksh
[email protected]_Z00E_1:/ # su -c ./flash-script.sh
su -c ./flash-script.sh
tmp-mksh: ./flash-script.sh: not found
127|[email protected]_Z00E_1:/ # ls -la /tmp-mksh
ls -la /tmp-mksh
-rw------- root root 5602 2015-10-28 10:16 flash-script.sh
-rwxr-xr-x root root 285016 2015-10-28 09:55 tmp-mksh
[email protected]_Z00E_1:/ # shell
shell
tmp-mksh: shell: not found
127|[email protected]_Z00E_1:/ # cd tmp-mksh
cd tmp-mksh
[email protected]_Z00E_1:/tmp-mksh # ./flash-script.sh
./flash-script.sh
tmp-mksh: ./flash-script.sh: can't execute: Permission denied
126|[email protected]_Z00E_1:/tmp-mksh # chmod 777 flash-script.sh
chmod 777 flash-script.sh
[email protected]_Z00E_1:/tmp-mksh # ./flash-script.sh
./flash-script.sh
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
./flash-script.sh[113]: head: not found
./flash-script.sh[113]: sed: not found
./flash-script.sh[115]: cut: not found
./flash-script.sh[115]: head: not found
./flash-script.sh[115]: sed: not found
./flash-script.sh[116]: cut: not found
./flash-script.sh[116]: sed: not found
./flash-script.sh[116]: head: not found
./flash-script.sh[117]: head: not found
./flash-script.sh[117]: sed: not found
./flash-script.sh[119]: head: not found
./flash-script.sh[119]: sed: not found
./flash-script.sh[120]: sed: not found
./flash-script.sh[120]: head: not found
./flash-script.sh[121]: sed: not found
./flash-script.sh[121]: head: not found
./flash-script.sh[122]: head: not found
./flash-script.sh[122]: sed: not found
Xposed version:
! Wrong platform: arm
! This file is for:
! Please download the correct package
! for your platform/ROM!
1|[email protected]_Z00E_1:/tmp-mksh # ./flash-script.sh
Click to expand...
Click to collapse
SOLVED!
Code:
C:\Users\********\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ $ su
su
[email protected]_Z00E_1:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]_Z00E_1:/ # mkdir /system/tmp
mkdir /system/tmp
mkdir failed for /system/tmp, File exists
255|[email protected]_Z00E_1:/ # mkdir /sdcard/tmp2
mkdir /sdcard/tmp2
mkdir failed for /sdcard/tmp2, File exists
255|[email protected]_Z00E_1:/ # ls -la /sdcard/tmp2
ls -la /sdcard/tmp2
drwxrwx--- root sdcard_r 2015-10-28 11:04 META-INF
-rw-rw---- root sdcard_r 5602 2015-10-28 11:04 flash-script.sh
drwxrwx--- root sdcard_r 2015-10-28 11:04 system
[email protected]_Z00E_1:/ # ls -la system/tmp
ls -la system/tmp
drwxrwx--- root root 2015-10-28 11:01 META-INF
-rwxrwxrwx root root 5602 2015-10-28 11:04 flash-script.sh
drwxrwx--- root root 2015-10-28 11:01 system
[email protected]_Z00E_1:/ # chmod 777 system/tmp/flash-script.sh
chmod 777 system/tmp/flash-script.sh
[email protected]_Z00E_1:/ # cd system/tmp
cd system/tmp
[email protected]_Z00E_1:/system/tmp # ./flash-script.sh
./flash-script.sh
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version: 75
- Placing files
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "gz
ip"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "ch
own"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "ch
mod"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "cp
"; caused by library "libsigchain.so" not found
- Done
[email protected]_Z00E_1:/system/tmp # reboot
reboot
To fix your problems you can try this, it worked for me, download this file and place it in the Jyrachy's Xposed ZE500KL folder (with "InstallXposedFramework" and "InstallXposedInstaller" files)
File: https://drive.google.com/file/d/0B7qd8mpcLFB2UGoxS1MwZExJOVk/view?usp=sharing
then after opening it write these commands in the shell
Code:
su
mount -o remount,rw /
mount -o remount,rw /system
chmod 777 system/tmp/flash-script.sh
cd system/tmp
./flash-script.sh
reboot
Click Here!
It's my way to install it. Thank you miau9202 and Jhyrarchy!
I'll update my tool.
but is strange worked onnmine at first try XD
Ok, i noticed one serious problem
Don't install Snapprefs with xposed. I did it, and when i wanted to reboot, some error appeared. So i click on soft reboot, and... android doesn't want to start
I'm flashing now my phone, and i hope it will boot
Ok, added a list of working and not working modules.
Also fixed the problem, i just added a recursive chmod to the /system/tmp folder before launching the script
96DANGER96 said:
SOLVED!
Code:
C:\Users\********\Desktop\Xposed ZE500KL>adb shell
[email protected]_Z00E_1:/ $ su -c mount -o remount,rw /
su -c mount -o remount,rw /
[email protected]_Z00E_1:/ $ su
su
[email protected]_Z00E_1:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]_Z00E_1:/ # mkdir /system/tmp
mkdir /system/tmp
mkdir failed for /system/tmp, File exists
255|[email protected]_Z00E_1:/ # mkdir /sdcard/tmp2
mkdir /sdcard/tmp2
mkdir failed for /sdcard/tmp2, File exists
255|[email protected]_Z00E_1:/ # ls -la /sdcard/tmp2
ls -la /sdcard/tmp2
drwxrwx--- root sdcard_r 2015-10-28 11:04 META-INF
-rw-rw---- root sdcard_r 5602 2015-10-28 11:04 flash-script.sh
drwxrwx--- root sdcard_r 2015-10-28 11:04 system
[email protected]_Z00E_1:/ # ls -la system/tmp
ls -la system/tmp
drwxrwx--- root root 2015-10-28 11:01 META-INF
-rwxrwxrwx root root 5602 2015-10-28 11:04 flash-script.sh
drwxrwx--- root root 2015-10-28 11:01 system
[email protected]_Z00E_1:/ # chmod 777 system/tmp/flash-script.sh
chmod 777 system/tmp/flash-script.sh
[email protected]_Z00E_1:/ # cd system/tmp
cd system/tmp
[email protected]_Z00E_1:/system/tmp # ./flash-script.sh
./flash-script.sh
******************************
Xposed framework installer zip
******************************
- Mounting /system and /vendor read-write
- Checking environment
Xposed version: 75
- Placing files
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "gz
ip"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "ch
own"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "ch
mod"; caused by library "libsigchain.so" not found
WARNING: linker: could not load library "libsigchain.so" from LD_PRELOAD for "cp
"; caused by library "libsigchain.so" not found
- Done
[email protected]_Z00E_1:/system/tmp # reboot
reboot
To fix your problems you can try this, it worked for me, download this file and place it in the Jyrachy's Xposed ZE500KL folder (with "InstallXposedFramework" and "InstallXposedInstaller" files)
File: https://drive.google.com/file/d/0B7qd8mpcLFB2UGoxS1MwZExJOVk/view?usp=sharing
then after opening it write these commands in the shell
Code:
su
mount -o remount,rw /
mount -o remount,rw /system
chmod 777 system/tmp/flash-script.sh
cd system/tmp
./flash-script.sh
reboot
Click to expand...
Click to collapse
How come when I type the commands, the output is just a copy of what I just typed?
---------- Post added at 01:52 AM ---------- Previous post was at 01:15 AM ----------
bohenian said:
How come when I type the commands, the output is just a copy of what I just typed?
Click to expand...
Click to collapse
nevermind, I just figured it. Thanks again!
can you tell us as well what you've done ? thx
is this possible for ZE550KL? thanks
Added to index, thanks for your work!
is it safe for ze500kg? and how about gravitybox module does it working well?
cpuz99 said:
is it safe for ze500kg? and how about gravitybox module does it working well?
Click to expand...
Click to collapse
I couldn't get gravity box to works 100%.
I never tried personally on ZE500KG, but someone else said it works.
Why not work with a Stock Rom 1:13?
Mandrakerj said:
Why not work with a Stock Rom 1:13?
Click to expand...
Click to collapse
what do you mean?
I'm on stock and it worked
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?
pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!
Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!
You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.