[MOD] [Stratos/Pace][v3.2] AmazBoost™ Speed up your Watch! - Amazfit

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.

Related

[Q] Samsung Galaxy S2 can't root on stock 2.3.6

hi guys,
i have a problem: i have upgrade my SGS 2 with kies at the 2.3.6 stock I9100XWKI1, and after i try to get root permission with Doomlord's procedure , but it's impossible after upgrading. i try also with unroot 2.2 but the same.someone can help me?please
these is the log
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Premere un tasto per continuare . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
22 KB/s (23060 bytes in 1.000s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
1493 KB/s (1075144 bytes in 0.703s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/.lfs: Function not implemented
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 900 bytes
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Premere un tasto per continuare . . .
same problem. DXKL1.
this one worked perfect.
http://forum.xda-developers.com/showthread.php?t=1125414
Alternatively...
...root before upgrading. See here.
Rgds,
dgndg
nope. didnt work for me. my 2.3.3 was rooted but lost root access once it got to 2.3.6. so just use a different rooting method other than the zergrush exploit.

[Q] Pleeeeease Help me ... problem rooting sk17i

Hello ...
I'v recently downgraded my mini pro to .42 to do a root, I am new to this and I found a way using zergrush.
whenever I try rooting I have the following error:
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
721 KB/s (23060 bytes in 0.031s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[+] Found a ... mode
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
731 KB/s (1075144 bytes in 1.435s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 433300 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Any one can help please????
I used the files in this thread:
http://forum.xda-developers.com/showthread.php?t=1695514
and every thing is ok now
Just to be sure, did you enable USB debugging and Unknown sources?
Feanor88 said:
Just to be sure, did you enable USB debugging and Unknown sources?
Click to expand...
Click to collapse
Yes Of course
u might have flushed rooted ftf file to ur fone.dwnld root checker 4m google play.
Sent from my ST15i using xda app-developers app
I had same problems, try rooting with flashtool. Download from here and install. Then klick on the open padlock, right next to the flash. This will root your device. Very great tool, if zergrush/Doomlords didn't work for you!

[Q] DooMLoRD's easy rooting toolkit not working on Samsung Galaxy Y Pro (Galaxy Txt)

Right. Hi. First post.
I wanted to post this in the actual thread, but since I'm not allowed, having not 10 posts, I'll just post this here.
It says the Samsung Galaxy Y Pro (2.3.5) is supported, and in fact I was able to root my phone earlier before I updated it (not sure which version I was at back then, before my last update it was still on 2.3.6 too so I'm guessing that hasn't changed.) using a different exploit. I'll be darned if I can remember which it was, but it did required me to run a .zip file in recovery mode of my phone.
I own this phone (Well it's called a Galaxy Txt here, but it's the same device.) and it's running Gingerbread 2.3.6
Kernel: 2.3.6.35.7
[email protected] #1
Build: GINGERBREAD.CELK2
The tool gave me this output:
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Druk op een toets om door te gaan. . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
643 KB/s (23060 bytes in 0.035s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4467 KB/s (1075144 bytes in 0.235s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 16148 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
I'd like root access again, so I figured I'd post my report anyways.
Thanks.
(By the way, nobody has cyanogen'd it, have they?)

[Q] From cdimage-touch to ubuntu-system to update directly using the phone

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.

Read-only filesystem - Tired everything - SGP312

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.

Categories

Resources