Database Develop

[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system

[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system
Prerequisit :
Be sure to have latest adb (1.0.32) and fastboot version. Download it from here
Link to know how to enter into fastboot
Under Fastboot
Download boot from here
Code:
- fastboot flash boot bootll.img
Download TWRP recovery from here
Code:
- fastboot flash recovery twrp.img
Go to Recovery and format all twice with TWRP recovery
Flashing back stock recovery :
Download stock recovery from here
Code:
- fastboot flash recovery recoverll.img
Back to stock recovery, format twice
Regenereting system step :
Download rooted AW 5.01 system directory from here
Code:
- fastboot flash system system.img
Go back to stock recovery, Choose apply update from ADB (adb sideload)
Download AW 5.01 update from here
Code:
- adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
Reboot system now. Choose langage, etc.
Nota : At this time, if you don't need root and Chainfire SU (witch is useless at this time) you can go just for flashing TWRP by :
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
And that's it.
Or following steps : Rooting back Watch and custom TWRP Recovery support
Download stock rooted AW 5.01 system directory from here
Code:
- adb reboot bootloader
- fastboot flash system system.img
Reboot Watch, autorize adb debug on the watch
Download Chainfire SU 2.40 from here or BETA-SuperSU-v2.42.zip
Note : You can remove Superuser.apk from the zip file into \common recovery which it is not compatible with AW 5.01
Pushing SU to the watch
Code:
- adb push supersu.zip /sdcard/su.zip
Back to Fastmod and flashing TWRP advanced recovery
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
Restart watch and go to TWRP recovery, install/flash su.zip from sdcard, reboot
Et Voilà !

Nice write up, I'm not sure doing the adb sideload does anything though. The system image is already patched, it was a backup from my device just rooted. Currently I have busybox working on the device and and working on init.d support so any changes we want to make will survive after reboot.
Sent from my A0001 using XDA Free mobile app

It'ill be nice :good:

HELP
I've done everything to try to get back to AW 5.01 but when I get to the adb sidelload part it says "error: device not found".
It's seem that windows 8 is not detecting my watch. Anyone have any insight on this would be great thanks!
Jay
edit...
Never Mind Got it to Work!

How did you get it to work?

I managed it, too. Turns out I had to reinstall drivers while in sideload mode. You can do it in device manager, select from computer, from list and find ADB composite device.

Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?

hornedfiend said:
Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?
Click to expand...
Click to collapse
simply flash this in twrp > https://hostr.co/3yMSrXUUMD8B and it will remove for you and you will get root also

Bricked during Downgrade, and manage to unbricked

In the way to downgrade from 4.0.2 to 3.5 I have soft bricked , here is steps
1) I have taken Nandroid backup with Modem and EFS.
2)Wipe all , Format data.
3)Put OS 3.5 zip and SU on phone.
4)Flashed 3.5, but during flashing it got stuked on patching system unconditionaly, canceled and returned to TWRP.
5)Again wipe all.
6)Now unable to mount system, mtp not working.
7)Tried Unbricked tool, didn't got any luck.
8) So I have no OS nothing on it, only TWRP.
9)Tried adb sideload, didn't work.
10)Finally Manage to adb push full os and su.
11)Flashed using TWRP with su, got flashed this time but /data failed error.
12)Booted but it says encryption unsuccessful, your device got damage, Reset Phone.
13)Tried Reset, but didn't work only same screen again.
14)Again format data using TWRP, and finally device got booted.
15)Now device is Decrypted, working fine.

Can't flash my recovery to TWRP on LineageOS

Hello dear fellows,
since 2 days i try to fix a problem with my unlocked and rooted Sony Xperia Z C6603. Still not finding any solution via internet, i take my last chance and post it here.
I unlocked and rooted my C6603 2 days ago and installed via fastboot the actual Lineage Custom ROM lineage-14.1-20171027-nightly-yuga-signed.zip.
Everything worked fine.
Bootloader -> fastboot flash boot boot.img (from lineage-14.1-20171027-nightly-yuga-signed.zip) :good:
Restart into Android Recovery :good:
Install via ADB sideload lineage-14.1-20171027-nightly-yuga-signed.zip :good:
Install via ADB sideload LineageOS 14.1 ARM32 SU (for full root access) :good:
Boot into Lineage, activate dev options and enabled Android-Debugging + Root-Access -> Apps and ADB :good:
Now my problem:
The so called "Android Recovery" is rly bad, so i try to override this recovery with TWRP 3.0.2.0 (yuga) but everytime i get the following error:
Code:
fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10656 KB)...
OKAY [ 0.351s]
writing 'recovery'...
[B]FAILED (remote: Command not allowed)[/B]
finished. total time: 0.370s
Where is my fffffff problem^^ Yes my phone is unlocked and yes, it is rooted (checked it also via root app).
I cant install gapps (dont work with ADB sideload) and and i want a proper recovery for backups and stuff...
So, what is wrong with me? Maybe someone of you have a good idea and can help me, i would rly appreciate it!
Sry for my not so proper english, hope u understand my problem anyway
Phone information:
Sony Xperia Z C6603
Android 7.1.2
LineageOS 14.1-20171020-NIGHTLY-yuga
LineageOS API-Level Guava (7)
Kernel-Version 3.4.113-yuga-gd710842
Build-Number lineage-yuga-userbug 7.2.1 NJH47F f281cb28f4

Thanx for all the help^^
I figured it out what to do:
1. fastboot flash boot twrp(actualversion).zip NOT fastboot flash recovery twrp(actualversion).zip
2. reboot into TWRP recovery mode
3. check if u can mount your data folder
3.1 if not, go to wipe -> advanced wipe -> change file system to ext4
4. install via ADB the actual LineageOS (or put the actual LineageOS file on your Sony/SD)
4. install LineageOS 14.1 SU via ADB (or put the actual LineageOS 14.1 SU file on your Sony/SD) -> https://www.lineageosroms.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/
6. install Open gapps -> http://opengapps.org/
7. reboot and configure LineageOS
7.1 check your developer options -> Debugging + root access for ADB and apps
8. download TWRP apk via PlayStore
8.1 give TWRP apk root access and download the actual TWRP file for yuga
9. flash this TWRP recovery via app
10. DONE
Everything works fine (for now )
Topic can be closed!

Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.

nurps said:
Same problem here, filesystem is ext4, TWRP app says it flashed but after a reboot its not there.
Always have to go via "fastboot flash boot twrp.img" and on the next reboot after flashing lineage its gone again.
After some research I found it it belongs into the fota partition, but I dont seem to have one.
Click to expand...
Click to collapse
Did you manage to solve the issue? I have the exact problem. The TWRP says it flashed but recovery is still stock android.

I have C6602. Someone on reddit gave me the solution; (do note that I had to run
Code:
adb root
for
Code:
su
to work.
You have a Xperia device which deals with recovery kind of weird. Recovery is stored with the kernel, not in a standalone recovery partition. Because of this you need to flash it to a FOTAKernel partition and use a kernel that supports FOTAKernel (the LineageOS one does).
To flash TWRP, first move the recovery image to your device with the adb command
Code:
adb push twrp-3.0.2-0-yuga.img /sdcard
. Then run
Code:
adb shell
to get access to the shell. Then run
Code:
su
and accept any prompts to gain root access. Then to actually flash, run
Code:
dd if=/sdcard/twrp-3.0.2-0-yuga.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse

sideload connection failed when installing magisk from adb

Hi
I am trying to install magisk 16.7 on my doogee s60 Lite android 7.0 phone. Sticking to v16 in hope google pay works.
I have unlocked bootloader in dev options, restarted into phone's native recovery mode, selected apply update from sd card, selected magisk zip file but after verification install aborted.
So I chose update from adb, which got me into bootloader, prompt now send the package
connected phone to windows 7 machine with drivers installed
adb devices
-> started successfully
typed adb sideload magisk-v16.7.zip/
and here is the response:
->sideload connection failed: no devices found
How to fix that?

You either fastboot flash the boot image that you first patch through the Magisk Manager, or you flash the Magisk zip in a custom recovery. Using the stock recovery or adb sideload won't work.

moto G7 plus bootloop

Hi,
I have a moto G7 plus on a bootloop after installing magisk 20.3.
It’s a XT1965-6 with a RETEU 29.98-111-9 ROM, after a clean boot I’ve installed TWRP (using twrp-installer-build-version-lake.zip) and boot into the system.
I then installed Magisk-v20.3.zip, but after the reboot the system keep bootlooping.
I can get it out with “Magisk-uninstaller-20200110.zip”
I’ve tried to get the log cat using “Logcat boot script” from https://www.didgeridoohan.com/magisk/MagiskHideHelp but I get no logfile.
I’ve made a new logcat.txt file and copied the code into it.
Used "adb push logcat.txt /data/adb/post-fs-data.d"
Then in twrp used the file manager to get to the file and “chmod 755”
Reboot the system, let it boot for 3 times and got back to TWRP.
I see no bootlog.log in /sdcard (or /data/media/0)
I even changed the sleep from 30 to 1, but still no log file.
How can I get the log?