Hey all!
Yesterday my new Nexus 4 arrived and I flashed Ubuntu Touch on it following the official instruciotns (on wiki.ubuntu.com/Touch/Install) using
Code:
phablet-flash cdimage-touch -b
It worked like a charm. But today I figured out that I should use "ubuntu-system" instead, because I would be able to update directly out of Ubuntu Touch using my phone.
Unfortunately this didn't work.
At first I tried to use this command
Code:
phablet-flash ubuntu-system -b
but this didn't work.
Code:
[email protected]:~$ sudo phablet-flash ubuntu-system -b
usage: phablet-flash [-h] ...
phablet-flash: error: unrecognized arguments: -b
Google couldn't help me so I tried it without the
Code:
-b
At the beginning everything looked good and basically it was done
Code:
INFO:phablet-flash:Installation complete
but than it started to use the recovery!
Here is the full Terminal output:
Code:
[email protected]:~$ sudo phablet-flash ubuntu-system
INFO:phablet-flash:Device detected as mako
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): system-image.ubuntu.com
INFO:phablet-flash:Download directory set to /home/max/Downloads/phablet-flash/imageupdates
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-master.tar.xz to /tmp/tmpayL2tR/image-master.tar.xz
--2013-09-10 21:06:14-- https://system-image.ubuntu.com/gpg/image-master.tar.xz
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 884 [application/x-tar]
Saving to: `/tmp/tmpayL2tR/image-master.tar.xz'
100%[======================================>] 884 --.-K/s in 0s
2013-09-10 21:06:14 (33,1 MB/s) - `/tmp/tmpayL2tR/image-master.tar.xz' saved [884/884]
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-signing.tar.xz to /tmp/tmpayL2tR/image-signing.tar.xz
--2013-09-10 21:06:14-- https://system-image.ubuntu.com/gpg/image-signing.tar.xz
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 904 [application/x-tar]
Saving to: `/tmp/tmpayL2tR/image-signing.tar.xz'
100%[======================================>] 904 --.-K/s in 0s
2013-09-10 21:06:15 (34,5 MB/s) - `/tmp/tmpayL2tR/image-signing.tar.xz' saved [904/904]
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc to /home/max/Downloads/phablet-flash/imageupdates/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/daily/mako/mako-20130905.1.full.tar.xz.asc to /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/daily/mako/mako-20130905.1.full.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/daily/mako/version-4.tar.xz.asc to /home/max/Downloads/phablet-flash/imageupdates/daily/mako/version-4.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/daily/mako/version-4.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable
The file is already fully retrieved; nothing to do.
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc to /tmp/tmpayL2tR/image-master.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 836 [text/plain]
Saving to: `/tmp/tmpayL2tR/image-master.tar.xz.asc'
100%[======================================>] 836 --.-K/s in 0s
2013-09-10 21:06:15 (28,0 MB/s) - `/tmp/tmpayL2tR/image-master.tar.xz.asc' saved [836/836]
INFO:phablet-flash:Downloading https://system-image.ubuntu.com/gpg/image-signing.tar.xz.asc to /tmp/tmpayL2tR/image-signing.tar.xz.asc
--2013-09-10 21:06:15-- https://system-image.ubuntu.com/gpg/image-signing.tar.xz.asc
Resolving system-image.ubuntu.com (system-image.ubuntu.com)... 91.189.88.35
Connecting to system-image.ubuntu.com (system-image.ubuntu.com)|91.189.88.35|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 490 [text/plain]
Saving to: `/tmp/tmpayL2tR/image-signing.tar.xz.asc'
100%[======================================>] 490 --.-K/s in 0s
2013-09-10 21:06:16 (16,6 MB/s) - `/tmp/tmpayL2tR/image-signing.tar.xz.asc' saved [490/490]
INFO:phablet-flash:Saving backup to /tmp/tmpt8NMk2
INFO:phablet-flash:Pulling /tmp/backup.tar.gz to /tmp/tmpt8NMk2
3702 KB/s (9366352 bytes in 2.470s)
INFO:phablet-flash:Restarting device... wait
INFO:phablet-flash:Restarting device... wait complete
INFO:phablet-flash:Clearing /data and /cache
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/ubuntu/ubuntu-20130905.1.full.tar.xz to /cache/recovery/
5606 KB/s (285224820 bytes in 49.677s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/ubuntu/ubuntu-20130905.1.full.tar.xz.asc to /cache/recovery/
12 KB/s (490 bytes in 0.039s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz to /cache/recovery/
5692 KB/s (37087976 bytes in 6.362s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz.asc to /cache/recovery/
11 KB/s (490 bytes in 0.040s)
INFO:phablet-flash:Decompressing partitions/recovery.img from /home/max/Downloads/phablet-flash/imageupdates/daily/mako/mako-20130905.1.full.tar.xz
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/version-4.tar.xz to /cache/recovery/
7 KB/s (288 bytes in 0.039s)
INFO:phablet-flash:Pushing /home/max/Downloads/phablet-flash/imageupdates/daily/mako/version-4.tar.xz.asc to /cache/recovery/
11 KB/s (490 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-master.tar.xz to /cache/recovery/
21 KB/s (884 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-master.tar.xz.asc to /cache/recovery/
20 KB/s (836 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-signing.tar.xz to /cache/recovery/
21 KB/s (904 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpayL2tR/image-signing.tar.xz.asc to /cache/recovery/
11 KB/s (490 bytes in 0.040s)
INFO:phablet-flash:Pushing /tmp/tmpBaPjCx to /cache/recovery/ubuntu_command
8 KB/s (353 bytes in 0.039s)
INFO:phablet-flash:Restarting device... wait
INFO:phablet-flash:Restarting device... wait complete
INFO:phablet-flash:Flashing recovery to /tmp/tmpME9mUn/partitions/recovery.img
< waiting for device >
sending 'recovery' (8604 KB)...
OKAY [ 0.540s]
writing 'recovery'...
OKAY [ 0.446s]
finished. total time: 0.986s
INFO:phablet-flash:Booting /tmp/tmpME9mUn/partitions/recovery.img
downloading 'boot.img'...
OKAY [ 0.546s]
booting...
OKAY [ 0.025s]
finished. total time: 0.572s
INFO:phablet-flash:Waiting for install to finish on device. Please do not unplug device until phablet-flash finishes.
INFO:phablet-flash:Installation complete
WARNING:phablet-flash:Restoring from backup
INFO:phablet-flash:Pushing /tmp/tmpt8NMk2 to /tmp/backup.tar.gz
3995 KB/s (9366352 bytes in 2.289s)
INFO:phablet-flash:Restoring from /tmp/tmpt8NMk2
INFO:phablet-flash:Restarting device... wait
INFO:phablet-flash:Restarting device... wait complete
Removing directory /tmp/tmpME9mUn
Removing directory /tmp/tmpayL2tR
So where is the problem? How do I switch over to the ubuntu-system build?
Looking forward to your help!
Greetings
Max
edit:
I although checked my current phablet-tools version but it's up to date
Code:
[email protected]:~$ dpkg -s phablet-tools | grep Version
Version: 1.0+13.10.20130909.2-0ubuntu1
edit2:
Found a newer version and updated but the problem is still the same
Code:
[email protected]:~$ dpkg -s phablet-tools | grep Version
Version: 1.0+13.10.20130910.4-0ubuntu1
Open the terminal on your device and run
sudo apt-get update && sudo apt-get dist-upgrade
No need really to do full image updates.
Sent from my LG-LS970 using xda app-developers app
What is wrong with using the recovery? To flash the new image it needs CWM. Just wait and let it reboot and you'll have the ubuntu-system image on your device.
To98 said:
What is wrong with using the recovery? ...
Click to expand...
Click to collapse
I think now I get it. He's flashing the new image and afterwards he's using the personal data (settings, networks etc.) from the recovery? I thought that if he's using the recovery, it would mean that he would undo all changes and bring me back to the initial stage.
blmvxer said:
Open the terminal on your device and run
sudo apt-get update && sudo apt-get dist-upgrade
Click to expand...
Click to collapse
I could try this to be sure.
Is there a way to find out that I now have the ubuntu-system build? Or do I have to wait for an update and if the update process is working directly from the phone, than it's the ubuntu-system build?
Greetings
Max
edit:
Code:
sudo apt-get dist-upgrade
Code:
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: Unable to write to /var/cache/apt/
E: The package lists or status file could not be parsed or opened.
edit 2:
Okay, I'm confused here but I can install updates from the phone now. So I guess it's working
Thank you guys!
Even if you have solved it already you can see if you are using the system-image with copying one file into /etc.
sudo cp /home/phablet/{filename} /etc/
Click to expand...
Click to collapse
If it doesn't work everything is OK.
Related
Hello,
I'm using EasyRootTool v11.zip from http://forum.xda-developers.com/showthread.php?t=2784900. When I run it, it shows that:
Code:
=============================================
Getting device variables
=============================================
Device model is L50u
Firmware is 17.1.1.F.0.39
=============================================
Sending files
=============================================
36 KB/s (1585 bytes in 0.042s)
25 KB/s (1133 bytes in 0.042s)
207 KB/s (9496 bytes in 0.044s)
275 KB/s (13672 bytes in 0.048s)
2788 KB/s (657704 bytes in 0.230s)
Copying kernel module...
819 KB/s (34473 bytes in 0.041s)
17 KB/s (767 bytes in 0.042s)
291 KB/s (13592 bytes in 0.045s)
Kernel version is 3.4.0-perf-g1cb2b9a-01879-gd0acb0a
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading geohot's towelroot (modified by zxz0O0)
=============================================
281 KB/s (13592 bytes in 0.047s)
2660 KB/s (197320 bytes in 0.072s)
=============================================
Waiting for towelroot to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error)
mount: Operation not permitted
/system/bin/chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
sh: /system/xbin/su: not found
cleaning up
done
Checking if device is rooted...
Error: device not rooted
yanjingtao said:
Hello,
I'm using EasyRootTool v11.zip from http://forum.xda-developers.com/showthread.php?t=2784900. When I run it, it shows that:
Code:
=============================================
Getting device variables
=============================================
Device model is L50u
Firmware is 17.1.1.F.0.39
=============================================
Sending files
=============================================
36 KB/s (1585 bytes in 0.042s)
25 KB/s (1133 bytes in 0.042s)
207 KB/s (9496 bytes in 0.044s)
275 KB/s (13672 bytes in 0.048s)
2788 KB/s (657704 bytes in 0.230s)
Copying kernel module...
819 KB/s (34473 bytes in 0.041s)
17 KB/s (767 bytes in 0.042s)
291 KB/s (13592 bytes in 0.045s)
Kernel version is 3.4.0-perf-g1cb2b9a-01879-gd0acb0a
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading geohot's towelroot (modified by zxz0O0)
=============================================
281 KB/s (13592 bytes in 0.047s)
2660 KB/s (197320 bytes in 0.072s)
=============================================
Waiting for towelroot to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
insmod: init_module '/data/local/tmp/wp_mod.ko' failed (Exec format error)
mount: Operation not permitted
/system/bin/chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: No such file or directory
sh: /system/xbin/su: not found
cleaning up
done
Checking if device is rooted...
Error: device not rooted
Click to expand...
Click to collapse
You cannot use EasyRootTool for the newest ROM's - you might be able to use How To Root the newest firmware (.314)
Btw. .39 is for the Chinese Z2?
Well I rooted my Z2. 314 firmware last night and it worked. I used ERT V11. It took 2 attempts mind you, cause I wasn't watching what I was doing the 1st time lol ?
Sent from my D6503 using xda premium from "Somewhere, but not here..."
harfot said:
You cannot use EasyRootTool for the newest ROM's - you might be able to use How To Root the newest firmware (.314)
Btw. .39 is for the Chinese Z2?
Click to expand...
Click to collapse
Thanks, is this tool unlocked the bootloader? I don't want to unlocked the bootloader.
.39 is Chinese Z2 LTE version's last fireware.
Z2 in China has three version, 3G/TD-LTE/LTE
Hi guys,
So I have an Xperia z2 (android 5.0.2) running on firmware 23.1.A.0.690 (downgraded from 23.1.A.0.726)
I'm attempting to my root my .690 fw using community rootkit v01, however it is with no avail, despite having the correct adb drivers installed, USB debugging & unknown sources enabled & ADK installed. Here is what rootkit keeps telling me...
# Semi-Automated script written by Sacha.
# With exploit method developed by GranPC.
# I assume you have adb installed, etc etc..
# I also assume you are using a Z2 on .69 firmware
# with contributions from DooMLoRD, norti and RyokoN
Installing exploit app.
3616 KB/s (348942 bytes in 0.094s)
pkg: /data/local/tmp/exploit.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Copying small files...
4538 KB/s (1109128 bytes in 0.238s)
3378 KB/s (121260 bytes in 0.035s)
3336 KB/s (13672 bytes in 0.004s)
93 KB/s (569 bytes in 0.005s)
1306 KB/s (9496 bytes in 0.007s)
401 KB/s (2050 bytes in 0.004s)
18 KB/s (97 bytes in 0.005s)
1478 KB/s (13672 bytes in 0.009s)
82 KB/s (505 bytes in 0.005s)
66 KB/s (404 bytes in 0.005s)
123 KB/s (764 bytes in 0.006s)
2906 KB/s (83364 bytes in 0.028s)
991 KB/s (3089 bytes in 0.003s)
122 KB/s (629 bytes in 0.005s)
5 KB/s (33 bytes in 0.006s)
5089 KB/s (2326385 bytes in 0.446s)
Copying BIG file... please have patience, this might take a while...
6223 KB/s (63931904 bytes in 10.031s)
Correcting permissions...
Starting Part 1
--- DooMing device: PART 1!
--- Correcting permissions
--- Running services
/data/local/tmp/vdcCreate[5]: vdc: not found
ln: /data/app-lib/ServiceMenu/libservicemenu.so: No such file or directory
ln: /data/local/tmp/vlib: Permission denied
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.s
ervicemenu/.ServiceMainMenu }
Test VDC #1:
Failure
PART 1 complete!
Complete!
----------------[ ATTENTION ]----------------
Please 'crash' the Service Menu app to complete.
For example: Service Info - Configuration.
The screen will probably blink when it has worked.
Press any key to continue . . .
Click to expand...
Click to collapse
I cannot 'crash' the service menu. When I hit 'configuration', the screen does not blink, despite restarting the entire process. I've tried this probably 20 times.
Any help would be greatly appreciated.
if i'm not mistaken the rootkit v01 is for Kitkat firmwares not for Lollipop, to root Lollipop you could try this http://forum.xda-developers.com/xperia-z2/general/root-t3108230
Code:
:::'###::::'##::::'##::::'###::::'########:'########:::'#######:::'#######:::'######::'########:
::'## ##::: ###::'###:::'## ##:::..... ##:: ##.... ##:'##.... ##:'##.... ##:'##... ##:... ##..::
:'##:. ##:: ####'####::'##:. ##:::::: ##::: ##:::: ##: ##:::: ##: ##:::: ##: ##:::..::::: ##::::
'##:::. ##: ## ### ##:'##:::. ##:::: ##:::: ########:: ##:::: ##: ##:::: ##:. ######::::: ##::::
#########: ##. #: ##: #########::: ##::::: ##.... ##: ##:::: ##: ##:::: ##::..... ##:::: ##::::
##.... ##: ##:.:: ##: ##.... ##:: ##:::::: ##:::: ##: ##:::: ##: ##:::: ##:'##::: ##:::: ##::::
##:::: ##: ##:::: ##: ##:::: ##: ########: ########::. #######::. #######::. ######::::: ##::::
..:::::..::..:::::..::..:::::..::........::........::::.......::::.......::::......::::::..:::::
Make your watch lightning fast!
What is AmazBoost?
To begin, hi all guys! It's been a long time since i don't post on this forum!
AmazBoost™ was born from my own necessity to get a faster and lag-free watch since i guess that every possessor of AmazFit watches sometimes complained about performaces. Mostly of te time the watch is fast enough to let us do everything in a good way, but expecially with roms and other extra features enabled while navigating the smartwatch some lags or small freezes may occur.
So what i've tought is: This watch is running a modified version of Android 4.4 kitkat this means that with right build.prop and init.d tweaks performances may benefit! And why not battery life too! So i've tested myself all the tweaks i founf in one of my old rom projects and i found out the best combinations between battery and performances!
Features of AmazBoost™
- Battery tweaks to improve SmartWatch battery life!
- Kernel Tweaks to improve kernel performance
- RAM tweaks for smarter RAM management
- Scrolling tweaks for smoother scrolling
- EXT4 tweaks for better filesystem perfomance
- Entropy tweaks for a SUPER smooth and fast experience
- IO Tweaks for improved EMMC perfomance
- Dalvik VM Tweaks for better system performance
- Clean smartwatch junk at every boot
- Misc performance tweaks for overall better watch navigation
- Faster screen raise to wake up
- Disabled logcat to improve battery life
What you need
- AmazFit Stratos/Pace
- Permanently rooted ROM
- init.d support
( if you don't have it use my MOD to enable it! goo.gl/2tVQFW )
How to install/Remove
1) Download the mod zip from download link and unzip it
2) Connect he wath to the PC
3) Run the installer.bat file to install the mod or Remover.bat to remove it
4) Done!
5) You NEED to reinstall the mod running the installer after every ROM update!
Changelog
Version 3.2
- SUPER smootheness and screen resposiveness like never before using Android entropy tweaks!
- Removed 3D tweaks: We have a very weak GPU and any modifications made for its configs makes UI more laggy
- Improved scrolling tweaks to reduce lags
- Improved VM tweaks
- Improved kenrnel tweaks
Version 3.1:
- Fixed ALL lags got from latest v3.1 tweaks (i'm sorry guys lol)
- Improved Overal UI smotheness
- Improved tweaks with 512MB RAM values
- Improved VM tweaks for beter perfomance and reduced battery consumption
- Got back and fixed EXT4 tweaks! So enjoy now the best filesystem perfomance of your smartwatch!
- Improved IO tweaks, to reduce the overhead and improve battery consumption
Version 3.0:
- Added new super smooth scrolling algorithm, follows perfectly your finger!
- Improved system animations speed and fixed some lags in notification pannel
- Added super RAM Low Meomry Killer algorithm for better extra app management
- Fixed and improved IO tweaks, now makes your watch even faster!
Version v2.1:
- Added Memory RW turbo speed! best memory speed ever for a faster watch!
- Fixed overally some lag issues got with last v2.0 update
Version v2.0:
- Added Misc performance tweaks for overall better watch navigation
- 2x faster scroll speed for faster animations and smoother scrolling
- Renice system at every boot
- New VM tweaks
- Disabed kernel logging to improve performances
- Improved RAM management system for better custom apk experience
- Clean smartwatch junk memory files at every boot
- Faster screen raise to wake up
- Added busybox applet for better tweaks enabling
Version V1.1:
- Improved Dalvik VM tweaks
- Improved UI smootheness
- Added new 3D tweaks
Download and enjoy!
goo.gl/asPtmN
If my work was useful always press thanks!
Very good! Thank you!
is the Rom only with English language or are other translations included?
peppe85 said:
is the Rom only with English language or are other translations included?
Click to expand...
Click to collapse
This is not a ROM it's a mod! somethig you can add to your current ROM so you can install it stratight away without problems!
also V1.1 got released!
great news
goo.gl/rbbRdF
this link take me to a chineese site - very strange..
Thanks, i installed it, let us see
I have the last US rom 2.8.1.0 , but my bootloader is unlocked, can i install your mod????
Code:
mount: Operation not permitted
mkdir failed for /system/AmazBoost/, Read-only file system
adb: error: failed to copy 'logcat_tweaks' to '/system/etc/init.d/': remote Is a directory
logcat_tweaks: 0 files pushed. 0.1 MB/s (1869 bytes in 0.013s)
adb: error: failed to copy 'CSZ_tweaks' to '/system/etc/init.d/': remote Is a directory
CSZ_tweaks: 0 files pushed. 1.1 MB/s (2766 bytes in 0.003s)
adb: error: failed to copy 'EXT4_tweaks' to '/system/etc/init.d/': remote Is a directory
EXT4_tweaks: 0 files pushed. 0.5 MB/s (1414 bytes in 0.003s)
adb: error: failed to copy 'VM_tweaks' to '/system/etc/init.d/': remote Is a directory
VM_tweaks: 0 files pushed. 0.9 MB/s (2372 bytes in 0.003s)
adb: error: failed to copy 'Battery_tweaks' to '/system/etc/init.d/': remote Is a directory
Battery_tweaks: 0 files pushed. 0.8 MB/s (2174 bytes in 0.003s)
adb: error: failed to copy '85kernel_tweaks' to '/system/etc/init.d/': remote Is a directory
85kernel_tweaks: 0 files pushed. 0.9 MB/s (2388 bytes in 0.003s)
adb: error: failed to copy 'IO_tweaks' to '/system/etc/init.d/': remote Is a directory
IO_tweaks: 0 files pushed. 0.9 MB/s (2448 bytes in 0.003s)
adb: error: failed to copy '3D_tweaks' to '/system/etc/init.d/': remote Is a directory
3D_tweaks: 0 files pushed. 0.4 MB/s (2102 bytes in 0.005s)
There is an error during install
Firmware 2.8.1.0, there is no init.d on my watch initially
i think you need root for this
E_g_o_r said:
Code:
mount: Operation not permitted
mkdir failed for /system/AmazBoost/, Read-only file system
adb: error: failed to copy 'logcat_tweaks' to '/system/etc/init.d/': remote Is a directory
logcat_tweaks: 0 files pushed. 0.1 MB/s (1869 bytes in 0.013s)
adb: error: failed to copy 'CSZ_tweaks' to '/system/etc/init.d/': remote Is a directory
CSZ_tweaks: 0 files pushed. 1.1 MB/s (2766 bytes in 0.003s)
adb: error: failed to copy 'EXT4_tweaks' to '/system/etc/init.d/': remote Is a directory
EXT4_tweaks: 0 files pushed. 0.5 MB/s (1414 bytes in 0.003s)
adb: error: failed to copy 'VM_tweaks' to '/system/etc/init.d/': remote Is a directory
VM_tweaks: 0 files pushed. 0.9 MB/s (2372 bytes in 0.003s)
adb: error: failed to copy 'Battery_tweaks' to '/system/etc/init.d/': remote Is a directory
Battery_tweaks: 0 files pushed. 0.8 MB/s (2174 bytes in 0.003s)
adb: error: failed to copy '85kernel_tweaks' to '/system/etc/init.d/': remote Is a directory
85kernel_tweaks: 0 files pushed. 0.9 MB/s (2388 bytes in 0.003s)
adb: error: failed to copy 'IO_tweaks' to '/system/etc/init.d/': remote Is a directory
IO_tweaks: 0 files pushed. 0.9 MB/s (2448 bytes in 0.003s)
adb: error: failed to copy '3D_tweaks' to '/system/etc/init.d/': remote Is a directory
3D_tweaks: 0 files pushed. 0.4 MB/s (2102 bytes in 0.005s)
There is an error during install
Firmware 2.8.1.0, there is no init.d on my watch initially
Click to expand...
Click to collapse
Your system is not rooted! adb root failed actually.....
New version v2.0 released
New Version v2.0 uploaded with ton of improvemets!
Version v2.0:
- Added Misc performance tweaks for overall better watch navigation
- 2x faster scroll speed for faster animations and smoother scrolling
- Renice system at every boot
- New VM tweaks
- Disabed kernel logging to improve performances
- Improved RAM management system for better custom apk experience
- Clean smartwatch junk memory files at every boot
- Faster screen raise to wake up
- Added busybox applet for better tweaks enabling
Thanks for your effort.
I didn't install it till now but have some remarks:
1) AmazBoost_remover.bat has a typo:
adb shell rm -f /system/etc/init.d/Battey_tweaks
should be:
adb shell rm -f /system/etc/init.d/Battery_tweaks
2) Some changes are made in the build.prop. Those changes are permanent I guess. Why do you have them started each time the device boots?
nhedgehog said:
Thanks for your effort.
I didn't install it till now but have some remarks:
1) AmazBoost_remover.bat has a typo:
adb shell rm -f /system/etc/init.d/Battey_tweaks
should be:
adb shell rm -f /system/etc/init.d/Battery_tweaks
2) Some changes are made in the build.prop. Those changes are permanent I guess. Why do you have them started each time the device boots?
Click to expand...
Click to collapse
If I write with echo command directly on the build.prop file in Smartwatch system, to remove the mod you must reflash your rom or download rom. Zip extract build.prop file and replace it inside the watch, a very long and not user friendly process to do. If i use setprop command, instead, those line are activated at every boot and have the same efficiency as the permanent build.prop modifications but it's enough to run my remover.bat to completely remove the mod and clean your ROM from my modifications.
MagicMan3311 said:
i think you need root for this
Click to expand...
Click to collapse
You are right, I havent notice rooted ROM req
Version v2.1 released!
Fixed some lags issues and added super extra memory RW speed!
AmazDev said:
Version v2.1 released!
Fixed some lags issues and added super extra memory RW speed!
Click to expand...
Click to collapse
Thanks for the great work. I'm going to check this out later!
AmazDev said:
Your system is not rooted! adb root failed actually.....
Click to expand...
Click to collapse
Code:
- Waiting for device...
- Waiting for root...
- Installing AmazBoost...
adb: error: failed to copy 'logcat_tweaks' to '/system/etc/init.d/': remote Is a directory
logcat_tweaks: 0 files pushed. 0.6 MB/s (1909 bytes in 0.003s)
adb: error: failed to copy 'CSZ_tweaks' to '/system/etc/init.d/': remote Is a directory
CSZ_tweaks: 0 files pushed. 0.7 MB/s (2337 bytes in 0.003s)
adb: error: failed to copy 'EXT4_tweaks' to '/system/etc/init.d/': remote Is a directory
EXT4_tweaks: 0 files pushed. 0.5 MB/s (1430 bytes in 0.003s)
adb: error: failed to copy 'VM_tweaks' to '/system/etc/init.d/': remote Is a directory
VM_tweaks: 0 files pushed. 0.8 MB/s (3214 bytes in 0.004s)
adb: error: failed to copy 'Battery_tweaks' to '/system/etc/init.d/': remote Is a directory
Battery_tweaks: 0 files pushed. 0.5 MB/s (2122 bytes in 0.004s)
adb: error: failed to copy '85kernel_tweaks' to '/system/etc/init.d/': remote Is a directory
85kernel_tweaks: 0 files pushed. 0.6 MB/s (2444 bytes in 0.004s)
adb: error: failed to copy 'IO_tweaks' to '/system/etc/init.d/': remote Is a directory
IO_tweaks: 0 files pushed. 1.7 MB/s (5265 bytes in 0.003s)
adb: error: failed to copy '3D_tweaks' to '/system/etc/init.d/': remote Is a directory
3D_tweaks: 0 files pushed. 0.7 MB/s (2122 bytes in 0.003s)
adb: error: failed to copy 'Cleaner_tweaks' to '/system/etc/init.d/': remote Is a directory
Cleaner_tweaks: 0 files pushed. 0.8 MB/s (1691 bytes in 0.002s)
adb: error: failed to copy 'Performance_tweaks' to '/system/etc/init.d/': remote Is a directory
Performance_tweaks: 0 files pushed. 0.8 MB/s (1644 bytes in 0.002s)
adb: error: failed to copy 'Renice_tweaks' to '/system/etc/init.d/': remote Is a directory
Renice_tweaks: 0 files pushed. 0.8 MB/s (3203 bytes in 0.004s)
busybox: 1 file pushed. 1.9 MB/s (1320860 bytes in 0.664s)
- Setting permissions...
Unable to chmod /system/etc/init.d/*: No such file or directory
- Rebooting...
AmazBoost installed! Press any key to exit...
With temp root on 2.8.1.0 firmware - no init.d dir. What firmware do u use?
how to root 2.8.1.0 pace ? DO we have instructions for this version?
Huxler said:
how to root 2.8.1.0 pace ? DO we have instructions for this version?
Click to expand...
Click to collapse
https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-firmware-installers-2017-t3725494
Temporary root, steps 10-11. U can exec adb commands, not working usual way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1928 (Chinese) and A1929 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original Chinese Firmware
Click to expand...
Click to collapse
OTA updates
Click to expand...
Click to collapse
@Neur_User for STRATOSfied Rom and other stuff
@Cracklydisc for original script and other stuff
@1immortal for his support
@Jaz, contributors and collaborators in Telegram group.
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues).
4. Wait to the end of the process and don't touch anything.
Installation output
*************************************************************
Stratos 3 CN 4.0.13.0 Stock Firmware Installer by Saratoga
*************************************************************
0. Restarting adb server
***************************
**********************************
1. Connect the watch to the PC
**********************************
**********************************
2. Rebooting to Fastboot mode
**********************************
******************************
3. Checking the connection
******************************
*******************************
4. Booting modded recovery
*******************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
***************************************
5. Waiting for connection in Recovery
***************************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
**********************************
10. Changing language to Chinese
**********************************
****************************************************
Stock Recovery and Bootloader installation process
****************************************************
********************************
11. Rebooting to Fastboot mode
********************************
****************************
12. Booting temporal root
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
*************************
15. Flashing Bootloader
*************************
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
*******************
16. Removing files
*******************
***************
17. Rebooting
***************
************
18. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch. Just run FCT_RST_STOCK.bat or use these commands instead.
Method 1:
Code:
adb reboot wipe
Method 2 (Only if watch is fully booted and you have root):
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Click to expand...
Click to collapse
Latest version
Stock CN/Chinese 4.0.22.0 Firmware Installer with OTA updates (Bugged Ultra Mode strings)
Click to expand...
Click to collapse
Previous versions
Stock CN/Chinese 4.0.19.5 Firmware Installer with OTA updates
Stock CN/Chinese 4.0.13.0 Firmware Installer with OTA updates
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual installation method
Manual installation method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in first post.
On your terminal, go to the path where all the files were unzipped, or if you are running a Windows OS, just run terminal_cmd.bat and you are good to go.
OTA Installation
Download OTA installer from Post #1 and if you are running a Windows PC, run terminal_cmd.bat, or any other command/terminal window on your PC in the root of the unzipped folder.
Copy the update to the watch
Code:
[COLOR="Blue"]adb push update.zip /sdcard
[/COLOR]
And launch the update
Code:
[COLOR="blue"]adb reboot update[/COLOR]
Wait to the end of the update, and when the watch reboots delete the update file
Code:
[COLOR="blue"]adb shell rm /sdcard/update.zip[/COLOR]
Firmware installation
On your terminal, go to the path where all the Firmware files were unzipped.
You can copy and paste all needed commands.
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery_mod.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
5. Wait until you get a triangle with an exclamation mark in your watch
6. Copy the files to the watch (it may take up to a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
7. Start Firmware installation (it may take up to 4 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN[/COLOR]
Stock Recovery and Bootloader installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-CN-adb-root.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
13. Copy stock Recovery and Bootloader files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/
adb push u-boot-with-spl-mbr-gpt.bin /data/media/0/[/COLOR]
Output (or similar)
Code:
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
15. Flash Bootloader
Code:
[COLOR="blue"]adb shell busybox dd if=/data/media/0/u-boot-with-spl-mbr-gpt.bin of=/dev/block/mmcblk0[/COLOR]
Output (or similar)
Code:
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
16 . Delete stock recovery and Bootloader installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img
adb shell rm /data/media/0/u-boot-with-spl-mbr-gpt.bin
[/COLOR]
17. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
18. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Factory Reset
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch
You can factory reset your watch by:
Code:
[COLOR="Blue"]adb reboot wipe[/COLOR]
When it's done, the watch will turn off.
Launch pairing QR code
You can use:
Code:
[COLOR="Blue"]adb shell am start -n com.huami.watch.setupwizard/.InitPairQRActivity[/COLOR]
Reboot into Ultra mode
You can reboot into Ultra mode by:
Code:
[COLOR="blue"]adb reboot mcu[/COLOR]
Mio1
Mio2
Thanks for your job !
Multi language (french) ?
Hi can you share multi language had which languages
Can someone confirm if Chinese Rom has English included by default?
Sent from my VOG-L29 using Tapatalk
tipu2185 said:
Can someone confirm if Chinese Rom has English included by default?
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
Only Chinese. However, you can change language to English using adb commands but you may face some bugs probably.
If you want official English language and others, check Stock/US/International thread for Stratos 3.
where can I find the update.zip?
thanks
Device: Sony Xperia Tablet Z
Model: SGP312
Android: 4.4.4
Problem started from 3 days ago. I had custom rom and had custom recovery: xzdualrecovery
I had some issue so wanted back to the official firmware. But unfortunately, i failed to restore the backup using TWRP.
So i needed to flash official firmware using Flashtool.
Didn't working Lolipop firmware so i flashed kitkat.
But the problem started after flashing firmware, that system is only Read-Only. I cannot able to use Internal Memory and also playstore not working.
So i wanted to again root and install "xzdualrecovery".
But getting error cause of the read-only issue.
Here is the log:
Code:
==============================================
= =
= XZDualRecovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
5. Open an ADB shell
6. Exit
Please choose install action.
[1,2,3,4,5,6]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting device and ROM info
=============================================
Device model is SGP312
Firmware is 10.5.1.A.0.292
Android version is 4.4.4
=============================================
Step2 : Sending the recovery files.
=============================================
10 KB/s (31 bytes in 0.002s)
2219 KB/s (18170 bytes in 0.007s)
163 KB/s (501 bytes in 0.002s)
1788 KB/s (12812 bytes in 0.006s)
2623 KB/s (65965 bytes in 0.024s)
771 KB/s (3159 bytes in 0.003s)
2378 KB/s (29204 bytes in 0.011s)
227 KB/s (699 bytes in 0.002s)
2406 KB/s (34473 bytes in 0.013s)
293 KB/s (1202 bytes in 0.003s)
2826 KB/s (96956 bytes in 0.033s)
3916 KB/s (870760 bytes in 0.217s)
3416 KB/s (3559894 bytes in 1.017s)
3528 KB/s (2426224 bytes in 0.671s)
2803 KB/s (14346 bytes in 0.004s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 870760 Feb 22 2016 [1;32m/data/local/tmp/recovery/busybox[0m
Press any key to continue . . .
mkdir: can't create directory '/storage/sdcard1/XZDualRecovery': Read-only file system
mkdir: can't create directory '/cache/XZDualRecovery': Read-only file system
touch: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
grep: /cache/XZDualRecovery/XZDR.prop: No such file or directory
##########################################################
#
# Installing XZDR version 2.8.26 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
This firmware does not require byeselinux, will not install it.
Creating /system/.XZDualRecovery and subfolders.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Creating the XZDR properties file.
touch: /cache/XZDualRecovery/XZDR.prop: No such file or directory
chmod: /cache/XZDualRecovery/XZDR.prop: No such file or directory
Updating installed version in properties file.
dr.recovery.boot will be set to TWRP (default)
dr.initd.active will be set to false (default)
dr.ramdisk.boot will be set to false (default)
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event5!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event0!
Speeding up CWM backups.
mkdir: can't create directory '/sdcard1/clockworkmod/': Read-only file system
touch: /sdcard1/clockworkmod/.hidenandroidprogress: No such file or directory
Make sure firstboot goes to recovery.
mkdir: can't create directory '/cache/recovery/': Read-only file system
touch: /cache/recovery/boot: No such file or directory
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
Yes had rooting issue but rooted successfully using kernel: SGP312_10.5.A.0.230_kernel.ftf
So i have SuperSU and rooted using flashtool.
I tired by chaning flashfile:
SGP312_10.4.1.B.0.109_US_CA_PR_R1C.ftf
SGP312_10.5.1.A.0.283_HK-SA-SG-MY-AE-KW.ftf
SGP312_10.5.1.A.0.292_VMo UK-IE.ftf
SGP312_10.6.A.0.454_VMo US-CA-PR.ftf
SGP312_10.7.A.0.222_1273-3888_HK-SA-SG-MY-AE-KW.ftf
SGP312_10.7.A.0.222_VMo_US_CA_PR.ftf
Still no luck. Stucking permission issue.
I tired to remount using adb shell but again it's getting read-only issue after the restart.
So i want to know how can i resolve this read-only filesystem issue? I need to use TWRP to restore my backup too.
Please help me, save my tablet.
Update: Fixed.