[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
I was experimenting how to modify system files on a stock system image without installing superuser and thought I'd share what I found:
What you need:
android platform tools (ADB and related files, FASTBOOT)
custom recovery (I used TWRP). You need to be able to gain adb root access, which is not possible using a 'production' image (to quote google's error message when I tried this) which is why you need to have a custom recovery. WARNING!! If you perform an oem unlock of your device to unlock the bootloader, you will be forced to wipe your device, proceed at your own risk! I am not responsible for what you do with your device.
Administrator access on your pc (if using windows)
In my example I was modifying /system/etc/gps.conf to use local time servers for faster GPS lock. To do this I rebooted into my custom recovery, mounted the system partition (rw) and used:
Code:
adb pull /system/etc/gps.conf
I then edited the file locally to use the desired NTP server with notepad++.
following this I used:
Code:
adb push gps.conf /system/etc/gps.conf
At this point I rebooted and used:
Code:
adb shell
to run the cat command on /system/etc/gps.conf and confirm my updates were now visible in the updated gps.conf file.
Hi friend! Can you help me?
C:\adb>adb push gps.conf /system/etc/gps.conf
failed to copy 'gps.conf' to '/system/etc/gps.conf': Read-only file system
reijr said:
Hi friend! Can you help me?
C:\adb>adb push gps.conf /system/etc/gps.conf
failed to copy 'gps.conf' to '/system/etc/gps.conf': Read-only file system
Click to expand...
Click to collapse
In TWRP mount system
I've used this before to change my build.prop
After updating to the latest build on Nexus 5, this no longer works.
I can pull and push the build.prop boot on reboot the original file returns.
Any ideas ?
IMPORTANT NOTE ABOUT ROOTING:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting.
REQUIREMENTS
1- Unlocked Bootloader (search on google if you dont know how to unlock)
2- Drivers and Adb/Fastboot commands knowledge
--------------------------------------------------------------------------------------------------------------------------------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
Bugs:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the serial number folder seems to change (which means that on /TWRP/BACKUPS/serialnumber/backupsinside/ changes every reboot so you have to go get the backup inside the old serialnumber folder and put on the new serialnumber folder).
Im leaving an unsecured boot image because system does not boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
Steps to Install TWRP and root
1. Download and extrct the files: https : // drive. google . com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip ---
Continuation 6. Step by Step of Step 6 since people seem to have been running into issues with it:
After rebooting to TWRP and having SuperSU.zip in the tablet storage. Go on Install tab and press the supersu file and install/flash it then reboot the device.
I flashed the latest Open Beta 25 yesterday and it took me some time to figure out how to properly root that. I was searching for a compatible TWRP for Android Oreo and I stumbled upon one when I was reading through pages and pages of comments from our community.
So, I am writing the steps here with the necessary files so that everyone can find it in one place.
This is not my work. All credits go to the original developers. I am just consolidating the steps I followed here. If I am violating any rules, please feel free to close this thread.
Credits:
@akhilnarang for Modified TWRP
@Chainfire For SuperSU
Necessary Downloads:
Oreo Compatible TWRP: https://drive.google.com/open?id=0B46mMEeAPSYGd3dBbzJhMWJUVE0
SuperSU Zip: https://drive.google.com/open?id=0B46mMEeAPSYGV1U3c3JSRmF2dWs
Steps to install TWRP and Root:
Note: My phone was encrypted when I tried this.
1. Copy the downloaded SuperSU Zip file to your phone.
2. Copy the TWRP file to the folder where ADB and Fastboot are installed.
3. Turn off your OnePlus 3/3T. Boot your OnePlus 3/3T into Fasboot mode > Press and hold the Volume Up Button + Power Button.
4. Connect your phone to your PC via USB Cable.
5. Open a command window on the folder where ADB and Fastboot are installed. Go to the folder where ADB and Fastboot are installed. Hold down Shift Key > Right Click on the empty space > Choose ‘Open CMD Here’.
6. Execute the below command in the command window to see if your device is properly connected:
Code:
fastboot devices
7. Make sure the TWRP file is in the ADB folder. Execute the below command to install TWRP on your OnePlus 3/3T running Android Oreo:
Code:
fastboot flash recovery TWRP-Oreo-OnePlus-3-3T.img
Do not restart your device upon installation. The procedure is not yet over.
8. Assuming you are now in Fastboot Mode, use the volume buttons and choose ‘Recovery Mode’ and then press the power button to enter TWRP Recovery.
9. Once you are in TWRP > Tap on ‘Install’ > Choose the SuperSU Zip file which you have downloaded from above > Swipe right to flash.
10. Reboot your device.
Let me know if you have any questions/doubts!
Source
If you have other TWRP already installed, any reason not just to install the compatible one by flashing image of compatible one using that?
gmlogan said:
If you have other TWRP already installed, any reason not just to install the compatible one by flashing image of compatible one using that?
Click to expand...
Click to collapse
We should be able to install twrp without connecting to pc if we already have twrp
gmlogan said:
If you have other TWRP already installed, any reason not just to install the compatible one by flashing image of compatible one using that?
Click to expand...
Click to collapse
You could do that. Shouldn't be an issue, I guess. The above steps are just what I followed.
Yes, but isn't Oreo package replacing TWRP with OnePlus recovery?
Sent from my OnePlus3 using XDA Labs
Unn113 said:
Yes, but isn't Oreo package replacing TWRP with OnePlus recovery?
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Install the recovery img in TWRP again after the zip. Reboot to recovery to confirm it didn't overwrite TWRP
liam_davenport said:
Install the recovery img in TWRP again after the zip. Reboot to recovery to confirm it didn't overwrite TWRP
Click to expand...
Click to collapse
No, what he says is that, once you install the Oreo Update Zip from TWRP it will be replaced with TWRP. I guess we could avoid this by immediately flashing the TWRP Zip soon after flashing the Oreo Zip.
dreams.sri said:
No, what he says is that, once you install the Oreo Update Zip from TWRP it will be replaced with TWRP. I guess we could avoid this by immediately flashing the TWRP Zip soon after flashing the Oreo Zip.
Click to expand...
Click to collapse
He means stock Oreo zip. If you flash OnePlus stock rom in TWRP and don't reflash TWRP stock zip replaces it with OnePlus recovery
Got error 7 while trying to install official Oreo beta from TWRP. Maybe a recovery issue not sure. I needed to flash last N beta and update from settings to Oreo beta
Its only possible with oneplus recovery. Trust me.
articblaster7 said:
Its only possible with oneplus recovery. Trust me.
Click to expand...
Click to collapse
OK, but after you have flashed Orea Beat with their recovery will it run OK with Twrp for backups and rooting etc
I dont have time to test right now. But i'm sure to Will vê possible now or in a near future
mauk said:
Got error 7 while trying to install official Oreo beta from TWRP. Maybe a recovery issue not sure. I needed to flash last N beta and update from settings to Oreo beta
Click to expand...
Click to collapse
You could download the Stock Oxygen OS Recovery and fastboot flash the recovery > Go to Stock Recovery > Go to 'Install from ADB' > Connect phone to PC > Sideload the update Zip > Boot into OREO > Reboot to Fastboot > Flash TWRP > Flash SuperSU. Will hardly take 15 mins.
liam_davenport said:
He means stock Oreo zip. If you flash OnePlus stock rom in TWRP and don't reflash TWRP stock zip replaces it with OnePlus recovery
Click to expand...
Click to collapse
True that, agreed!:good:
dreams.sri said:
True that, agreed!:good:
Click to expand...
Click to collapse
so the process is
1) Flash oreo compatible recovery
2) Flash Rom
3) Flash TWRP recovery
4)Flash root
manishdev said:
so the process is
1) Flash oreo compatible recovery
2) Flash Rom
3) Flash TWRP recovery
4)Flash root
Click to expand...
Click to collapse
1. Flash Stock Recovery.
2. Sideload Oreo Zip
3. Flash Oreo Compatible TWRP
4. Flash SuperSU
manishdev said:
so the process is
1) Flash oreo compatible recovery
2) Flash Rom
3) Flash TWRP recovery
4)Flash root
Click to expand...
Click to collapse
Yes. It's ok like you write.
Hi Guys,
I faced below issue while flashing Oreo beta update on oneplus 3 using twrp.
Details:
TWRP: 3.1.1.2
Rooted: Magisk v14.0
Do I need to unroot and uninstall twrp before updating?
TWRP:
OnePlus3Oxygen_16_OTA_035_all_1710131629_83503ca929ca4b82.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsscript aborted: E3004: This package is for "OnePlus 3" devices; this is a "".
E3004: This package is for "OnePlus 3" devices; this is a "".error: 3004
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/sdcard/TWRP/OnePlus3Oxygen_16_OTA_035_all_1710131629_83503ca929ca4b82.zip'
Updating partition details...
Iata backup size is 8093MB, free: 37507MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
SuperSU not Working
dreams.sri said:
I flashed the latest Open Beta 25 yesterday and it took me some time to figure out how to properly root that. I was searching for a compatible TWRP for Android Oreo and I stumbled upon one when I was reading through pages and pages of comments from our community.
So, I am writing the steps here with the necessary files so that everyone can find it in one place.
This is not my work. All credits go to the original developers. I am just consolidating the steps I followed here. If I am violating any rules, please feel free to close this thread.
Credits:
@akhilnarang for Modified TWRP
@Chainfire For SuperSU
Necessary Downloads:
Oreo Compatible TWRP: https://drive.google.com/open?id=0B46mMEeAPSYGd3dBbzJhMWJUVE0
SuperSU Zip: https://drive.google.com/open?id=0B46mMEeAPSYGV1U3c3JSRmF2dWs
Steps to install TWRP and Root:
Note: My phone was encrypted when I tried this.
1. Copy the downloaded SuperSU Zip file to your phone.
2. Copy the TWRP file to the folder where ADB and Fastboot are installed.
3. Turn off your OnePlus 3/3T. Boot your OnePlus 3/3T into Fasboot mode > Press and hold the Volume Up Button + Power Button.
4. Connect your phone to your PC via USB Cable.
5. Open a command window on the folder where ADB and Fastboot are installed. Go to the folder where ADB and Fastboot are installed. Hold down Shift Key > Right Click on the empty space > Choose ‘Open CMD Here’.
6. Execute the below command in the command window to see if your device is properly connected:
Code:
fastboot devices
7. Make sure the TWRP file is in the ADB folder. Execute the below command to install TWRP on your OnePlus 3/3T running Android Oreo:
Code:
fastboot flash recovery TWRP-Oreo-OnePlus-3-3T.img
Do not restart your device upon installation. The procedure is not yet over.
8. Assuming you are now in Fastboot Mode, use the volume buttons and choose ‘Recovery Mode’ and then press the power button to enter TWRP Recovery.
9. Once you are in TWRP > Tap on ‘Install’ > Choose the SuperSU Zip file which you have downloaded from above > Swipe right to flash.
10. Reboot your device.
Let me know if you have any questions/doubts!
Source
Click to expand...
Click to collapse
hello, i followed all the steps but for some reason, my phone is stuck in boot loop. everything is normal untill i see my lockscreen,but as soon as i try to unlock or even press powerbutton , the phone restarts again everytime.
Will the same steps work for magisk?
I don't have the original boot.img. I want to unroot temporarily. But want to re-root afterward.
I was wondering if I can save a modified_boot.img somehow and flash that later once I am done. Is it possible?
devsk said:
I don't have the original boot.img. I want to unroot temporarily. But want to re-root afterward.
I was wondering if I can save a modified_boot.img somehow and flash that later once I am done. Is it possible?
Click to expand...
Click to collapse
What ROM and device are you using?
How did you root it in the first place?
What OS are you running?
Heres my 30 second version of how id do it on my Pixel 2 XL an a/b device....ymmv, depending on device
Download latest platform tools from Google for your OS, if necessary: https://developer.android.com/studio/releases/platform-tools
Next you'll need dd, if you're on Linux, you can skip ahead
For Windows....go to http://gnuwin32.sourceforge.net/packages/coreutils.htm
Download Binaries & Dependencies zips
Extract dd.exe from coreutils-5.3.0-bin.zip /bin to platform tools path
Extract all .dll's from coreutils-5.3.0-dep.zip /bin to platform tools path
Enable USB Debugging & ABD access on device
Boot device to recovery (usually TWRP)
on PC and prompt in platform tools folder:
if you have recovery (usually TWRP) installed:
adb reboot recovery
if you DONT have recovery (usually TWRP) installed, but instead fastboot it via bootloader (as i do on my Pixel 2XL):
adb reboot bootloader
fastboot boot twrp-xxx.img
swipe into twrp
back to PC prompt:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
adb pull /sdcard/boot.img magisk_boot.img
Uninstall magisk
When you need to flash magisk boot image back:
Boot to bootloader..
on PC and prompt in platform tools folder:
adb reboot bootloader
fastboot flash boot magisk_boot.img
fastboot reboot
Note: You can of course use the same first process to backup (and extract) the stock boot.img before rooting ....and the latter to reflash it if needed if rooting goes wrong
Sorry, I should update my profile. My device is OnePlus 8 Pro.
> dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/magisk_boot.img
@73sydney why would this not work from within a rooted device? Its not like some process is holding a read lock on that partition or something else is also writing to it. Its a partition persisted in the NAND, which is not being touched by anything.
The only thing is that there are 2 partitions on the NAND: boot_a and boot_b. I need to know which one is the current one.
And this tells me slot B:
cat /proc/cmdline | tr ' ' '\n' | grep --color slot
androidboot.slot_suffix=_b
For flashing back, I obviously need to be in bootloader because I won't have the root to write to the partition.