Database Info

[RECOVERY] [UNOFFICIAL] [Phobos] TWRP 3.0.0-0 for the HP Slate 21

TWRP for the HP Slate 21 (phobos)
Code:
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
TeamWin Recovery project (or TWRP for short) ported for the HP Slate 21 (s100 & k100).
Here are some images:
{
"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"
}
Download
https://www.androidfilehost.com/?fid=24399994186369430
Install/Flashing Instructions:
1. You will need the following things in order to install TWRP on the Slate 21: 1 USB male to USB male connector, a computer with ADB and fastboot installed, common sense.
2. Turn off device and boot into fastboot mode (Volume Down + Power)
3. Connect your device to your computer by plugging one end of the USB cord into the lone USB port on the left-hand side of the device and the other end on any USB port on your computer.
4. Run the command “fastboot oem unlock” (no quotes)
5. Select yes on your Slate 21, after this step you will lose all your data. Vol Up to move Up, Vol Down to move Down, Brightness Up to select.
6. After fastboot has been unlocked, you’ll need to flash TWRP to your recovery. Do do this run the following command:
fastboot flash recovery /path/to/downloaded/TWRP.img
Replace /path/to/downloaded/TWRP.img with where you downloaded TWRP provided by me (Quaesar). You can drag and drop the IMG into Terminal/CMD to do this easily.
7. Use the buttons on the side of the device to select “Recovery”
8. Profit! You now have the latest TWRP on your device!
Cyanogenmod 12.1:
http://forum.xda-developers.com/general/general/rom-cyanogenmod-12-1-hp-slate-21-t3201416
Donations:
You can donate to me for my hard work through PayPal. My donation email is [email protected]. Any and all donations are welcome regardless of amount. Thanks for supporting me!
Direct link: https://www.paypal.me/Quaesar
Credits
Building this was a collaborative effort. The following developers/beta testers helped me provide you with this:
Quaesar (me): Main person, started project, etc etc.
UnjustifiedDev: Device tree, initial setup
SLATE21&MOTOG: Beta testing
Vocoderism: Beta testing
JonasFi: Beta testing
Seanichigo: k100 testing
If you have any comments or questions, reply to this thread and I'll get to you whenever I can
PLEASE HIT THAT THANKS BUTTON!!! IT REALLY SHOWS YOU APPRECIATE MY WORK!!!!!
Peace,
Quaesar

Changelog:
Public Release 1:
- First public release of recovery. Nothing major to see here
Known Issues/Bugs:
- CPU temperature will show up as 0 sometimes (it's usually 40-50*C if you're wondering)

FAQs:
Q: Bruhhhh, hook me up with dem sources
A: Dem sources can be found at teh GitHubs: (Link)
Q: Should I backup my stuff?
A: Do I need to answer that?
Q: What is this fastboot your speak of and how can I get it?
A: This video explains everything nicely: https://www.youtube.com/watch?v=maLWScgXflk
Q: On a scale of one to ten, how cool are you?
A: 11

Version 3 works very well. I also resolves an issue with using the swipe control from the previous version. Thanks Q!

device not found

Desparragosa said:
device not found
Click to expand...
Click to collapse
Check your connection (wire, computer, Slate). Make sure you have the correct fastboot drivers installed. I've seen an issue with the Windows 10 where Windows doesn't want to recognize or flash to the device. If you're comfortable, you may want to try using Ubuntu (I use 14.04). If you want, you can always contact me over Hangouts at [email protected]
Peace,
Quaesar

Quaesar said:
Check your connection (wire, computer, Slate). Make sure you have the correct fastboot drivers installed. I've seen an issue with the Windows 10 where Windows doesn't want to recognize or flash to the device. If you're comfortable, you may want to try using Ubuntu (I use 14.04). If you want, you can always contact me over Hangouts at [email protected]
Peace,
Quaesar
Click to expand...
Click to collapse
Hi. I can't do the unlock. Started with windows 10, and now with windows 8. Get the same message FAILED (command write failed (Unknown error))
don't know what else to try. Can you provide the fastboot drivers you used?
EDIT: Found the problem. Had to disable MTP!

rgomesf said:
Hi. I can't do the unlock. Started with windows 10, and now with windows 8. Get the same message FAILED (command write failed (Unknown error))
don't know what else to try. Can you provide the fastboot drivers you used?
EDIT: Found the problem. Had to disable MTP!
Click to expand...
Click to collapse
Nice! I use Ubuntu anyway so I would know about drivers haha

Hi there
Is there any other way of installing TWRP onto the HP Slate s/k100 21 without using a male to female usb connector?
Like rooting the Slate then flashing using something like the app Flashify? Booting off the SD card?
Thanks in advance

Hey there! I tried to install your recovery on my HP Slate 21, but although the fastboot output looks good to me:
seems I have already unlocked previously:
Code:
$ sudo fastboot oem unlock
...
(bootloader) Bootloader is already unlocked.
OKAY [ 0.025s]
finished. total time: 0.025s
And flashing the recovery also seems like it works fine:
Code:
$ sudo fastboot flash recovery TWRP_3.0.0-0_phobos_Quaesar.img
target reported max download size of 641728512 bytes
sending 'recovery' (9256 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 0.892s
But when I boot into recovery afterwards I get not TWRP but a stock recovery that will not flash your cyanogenmod because it cannot verify it.

Apad121 said:
Hi there
Is there any other way of installing TWRP onto the HP Slate s/k100 21 without using a male to female usb connector?
Like rooting the Slate then flashing using something like the app Flashify? Booting off the SD card?
Thanks in advance
Click to expand...
Click to collapse
If you can get root then yeah it's good. However finding a way to root without a wire to connect to the computer is kinda hard. My suggestion is to skip that and just twist two male usb cables together
@kaefert, try locking and unclocking the bootloader. If that doesn't work wipe the recovery partition then flash it

Quaesar said:
If you can get root then yeah it's good. However finding a way to root without a wire to connect to the computer is kinda hard. My suggestion is to skip that and just twist two male usb cables together
@kaefert, try locking and unclocking the bootloader. If that doesn't work wipe the recovery partition then flash it
Click to expand...
Click to collapse
Thanks but I have already bought the cable and flagged TWRP on. I have also tried out your cm ROM.

I could use some advice. I enabled the USB developer option, when the cable is connected to my booted HP slate the ADB command window on my laptop works. I was able to send command adb reboot bootloader to reboot the Slate into the bootloader but once I get there, the cable disconnects from the Slate so I can't do the fastbook unlock command. Any tips ?

when I run the fastboot flash recovery /path/to/downloaded/TWRP.img command
error appears: can not open '/path/to/downloaded/TWRP.img'

im having issues installing TWRP on Slate21
hi, its been a while since I touched anything android, so its probably no surprise im having problems here! lol, anyhow, ive got a Slate 21 stuck on the 'HP Slate Android' boot screen and wanted to reflash it, so I follow the instructions here, and I get as far as the point where you flash TWRP and I get a problem and it doesn't flash?
this is what it says when I try>>>>>
Target reported Max download size of 641728512 bytes
error: cannot load 'c:\TWRP.img' : No error
obviously ive placed the TWRP.img on the root drive, am I doing something wrong here? have I got the wrong ADB driver? any help will be greatly appreciated. thanks Dee

HP Slate 21-s100
Turn off device and boot into fastboot mode - OK
Connect your device to your computer by plugging USB male to USB male connector - OK
Run the command “fastboot oem unlock” - OK
fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 19.503s]
Finished. Total time: 19.504s
fastboot flash recovery /path/to/downloaded/TWRP.img - OK
Use the buttons on the side of the device to select “Recovery” - OK
Profit! You now have the latest TWRP on your device! - NOPE! :crying: I see the original hp Android System Recovery :crying: WHY?
I was worng, Where am I doing wrong?

I did it the way you say here.
then i wanted to change the software.
i got this error.
I did something wrong.
I am installing twrp but it won't open.
Pressing volume + volume - power keys comes here.
I would be glad if you could help.
Thanks

[Recovery][Snapdragon][R7S/r7sf] Official TWRP for Oppo R7Sf (3.1.1-0)

Team Win Recovery Project 3.1.1-0
This is for the International Oppo R7S, Snapdragon models only! Do not flash on Mediatek R7Sm models!
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://twrp.me/devices/oppor7sf.html
For Official TWRP Changelog see Official TWRP News page:
https://twrp.me/
Old changelog listing:
CHANGELOG for 3.0.2-2:
-Fix subpartition restore bug (ex: EFS)
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords).
This fixes decrypt of full device encryption on devices that support decrypt.
This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese
won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_oppo_r7sf (master)
Thanks! & Contributors!
My wife for her patience love you baby!
Team Win, especially Dees-Troys, MSF, Captain_Throwback
Most of all! Uberlaggydarwin , without you this would not have been possible
As promised I have created a Guide on how to install TWRP permanently on the Oppo R7S. It is attached. See below!
Update: Updated Guide to V3 due to TWRP Update and minor fixes in the Guide.
Counter:
GuideV1.pdf = ~1000 Downloads
GuideV2.pdf = 3700 Downloads
GuideV3.pdf = 2918 Downloads

Does it mean that bootloader is unlocked ?

lapocompris said:
Does it mean that bootloader is unlocked ?
Click to expand...
Click to collapse
You are able to unlock the bootloader. For me it's just not possible to enter twrp. Everytime gets overwritten by color os recovery.

OK. Just tested it on the R7 Lite. It works well. Also, as expected, it has soft keys and the hard keys dont work.

Could anyone point me to a step by step instruction on how to install twrp recovery. Sorry for the novice question. Sorry without Root as I'm on latest 5.1.1 and cannot root with oppo tools.

smokeyrider said:
Could anyone point me to a step by step instruction on how to install twrp recovery. Sorry for the novice question. Sorry without Root as I'm on latest 5.1.1 and cannot root with oppo tools.
Click to expand...
Click to collapse
Just head over to the twrp page. The is an instruction written down. Don't forget to unlock your bootloader.

Hi I have followed the instructions. I can "adb reboot bootloader" and get oppo bootloader screen. When I enter "fastboot flash recovery twrp.img" My phone just reboots to normal and the CMD prompt just hangs "waiting for device". Any assistance appreciated. I have latest 5.1.1 Color OS and Windows 10 machine. Thanks.

Ravikirancg said:
OK. Just tested it on the R7 Lite. It works well. Also, as expected, it has soft keys and the hard keys dont work.
Click to expand...
Click to collapse
if you have root and could provide me with the output of the partition details I can build a TWRP specific for the R7 Lite. if it has not been done yet.
I will need information output of:
ls -l /dev/block/bootdevice/by-name/
and
cat /proc/partitions
you will need to have root and switch to "su" in the shell before entering the commands.

celoxocis said:
if you have root and could provide me with the output of the partition details I can build a TWRP specific for the R7 Lite. if it has not been done yet.
I will need information output of:
ls -l /dev/block/bootdevice/by-name/
and
cat /proc/partitions
you will need to have root and switch to "su" in the shell before entering the commands.
Click to expand...
Click to collapse
Your alive celoxocis!
Do you have some news on twrp for ps, your cm build etc?

MacLaughlin said:
Your alive celoxocis!
Do you have some news on twrp for ps, your cm build etc?
Click to expand...
Click to collapse
CM is still work in progress. I will be leaving tomorrow for a one week getaway. After that I plan to write a PDF guide for those with PS how to install TWRP as PS fastboot allows for bootloader unlocking.

celoxocis said:
CM is still work in progress. I will be leaving tomorrow for a one week getaway. After that I plan to write a PDF guide for those with PS how to install TWRP as PS fastboot allows for bootloader unlocking.
Click to expand...
Click to collapse
I thought you need to update the twrp version? The only problem was twrp didn't get recognized and gets overwritten by color os recovery.

MacLaughlin said:
I thought you need to update the twrp version? The only problem was twrp didn't get recognized and gets overwritten by color os recovery.
Click to expand...
Click to collapse
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.

celoxocis said:
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
Click to expand...
Click to collapse
But I get a success notification...? Fastboot oem unlock

MacLaughlin said:
But I get a success notification...? Fastboot oem unlock
Click to expand...
Click to collapse
if you do "fastboot OEM unlock" twice. does it show "already unlocked" the second time?

celoxocis said:
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Device already : unlocked!
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.874s
So the bootloader is unlocked. DTB stands for Device Tree Blob and is a mechanism to pass low level hardware information between bootloader and kernel. So I guess it's just not for PS.
---------- Post added at 07:05 PM ---------- Previous post was at 06:44 PM ----------
celoxocis said:
if you do "fastboot OEM unlock" twice. does it show "already unlocked" the second time?
Click to expand...
Click to collapse
Yes!

MacLaughlin said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Device already : unlocked!
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.874s
So the bootloader is unlocked. DTB stands for Device Tree Blob and is a mechanism to pass low level hardware information between bootloader and kernel. So I guess it's just not for PS.
---------- Post added at 07:05 PM ---------- Previous post was at 06:44 PM ----------
Yes!
Click to expand...
Click to collapse
I know what DTB stands for I can see that you are on Project Spectrum. The DTB for PS (Marshmallow) is different than that for ColorOS (Lollipop) there fore it is not working. The offical TWRP is based on ColorOS for the mainstream available. Project Spectrum is only available for beta testers. However "fastboot flash recovery TWRP. IMG" should work. To enter TWRP simply hold down volume-down + power button. When I finish CM I will release a TWRP with kernel+DTB based on Android 6.0!

celoxocis said:
I know what DTB stands for I can see that you are on Project Spectrum. The DTB for PS (Marshmallow) is different than that for ColorOS (Lollipop) there fore it is not working. The offical TWRP is based on ColorOS for the mainstream available. Project Spectrum is only available for beta testers. However "fastboot flash recovery TWRP. IMG" should work. To enter TWRP simply hold down volume-down + power button. When I finish CM I will release a TWRP with kernel+DTB based on Android 6.0!
Click to expand...
Click to collapse
Sadly this is not working. I can flash TWRP but if I try to enter TWRP the screen just stays black. At the moment I'm not able to enter recovery, with key buttons. Also Color Os recovery isn't working at the moment.

just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.

celoxocis said:
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
Click to expand...
Click to collapse
I will flash stock recovery again. Maybe later on the new version of ps.

celoxocis said:
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
Click to expand...
Click to collapse
Okay stock recovery isn't working anymore as well. The screen just stays black. Got exactly the same error as when flashing twrp. Now I'm without a working recovery ???? maybe I can extract the recovery img. from spectrum. See if this is working.

[GUIDE] [HOW TO] Return Your Huawei Watch 2 to Stock

Hi, everyone. After reading posts of (and having experienced my own) boot loops and seeing as how there is a guide for the first Huawei watch,
I've decided that there should also be a guide for restoring the Huawei Watch 2 to stock ROM.
Getting Prepared
The bootloader unlocked on the watch. For instructions on how to do so, read janjan's TWRP Recovery guide.
ADB/fastboot and drivers already setup on your computer
ADB debugging enabled on the watch. You can find instructions for this at the same URL link above.
Restoring Via Batch/Shell Executable
The stock image files in janjan's thread are no longer available, so you'll have to go to this Reddit thread for the file.
Under the "Flashing back to stock" section, download the appropriate version for your watch.
Reboot your watch to bootloader either manually or via the ADB command:
Code:
adb reboot bootloader
Unzip the file
For Sawfish Devices:
At the command line, type in the following:
Code:
flash-all.bat (for Windows) or .flash-all.sh (for Linux)
fastboot oem lock
fastboot reboot
For Sawshark Devices: (or if you were having trouble executing the flash-all file successfully. NOTE: There's a missing image
file in the Sawshark stock file, so the flash-all file will not run successfully.)
Go to the folder where you extracted the stock image file and extract the zip file that's there.
Then go to the command line and type in the following:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot oem lock
fastboot reboot
Credits/Thanks
janjan - HUAWEI WATCH 2 (LTE-Sawshark) & (BT-Sawfish)-OWDE.180926.001.A1
- [RECOVERY]+[sawshark(4G)+sawfish(BT)]Unofficial TWRP 3.1.1-0-[29-3-18]
travis82 - [ROM] [KERNEL] [SAWSHARK] Oreo OWDE.180215.017 [DEC/24/2018]
Skin1980 - [GUIDE] [HOWTO] Return to stock for Huawei Watch
davpel - [GUIDE][HOW TO]Boot into Fastboot Mode
CadBuRy.VN - [Rom][NXG46W] Huawei Watch 2 4G L-09S Global Fastboot [Factory Images]

Great guide.
Will try this on my watch.
Thanks.

does not work on leo-dlxx...it will kill the device i restored via twrp another rom
anyone have a stock rom for leo-dlxx?

Timewolf said:
does not work on leo-dlxx...it will kill the device i restored via twrp another rom
anyone have a stock rom for leo-dlxx?
Click to expand...
Click to collapse
I actually have the Leo-DLXX and I wrote this guide mainly for that watch. Do you remember what error messages you received? How does it kill the device?

How prevent upgrade after this? I flash it and all good, but it upgrades to last firmware and I see no solution to stop it

"Invalid sparse file format at header magi" while trying to flash system.img

Thanks!!! You saved my Smartwach because it was bricked and I couldn't find orginal stock firmware

not work with sawshark leo-dll only stuck in logo

Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5

square_eyes said:
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
Click to expand...
Click to collapse
Well, I haven't ever seen sth like you're trying to do, but can you point me to the source of the rom you're trying to flash?

square_eyes said:
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
Click to expand...
Click to collapse
And the second question: Do you own sawfish (WiFi) or Sawshark (LTE) watch?
(I'm going to sleep soon but I'll take a look on this tomorrow)

Lord Sithek said:
And the second question: Do you own sawfish (WiFi) or Sawshark (LTE) watch?
(I'm going to sleep soon but I'll take a look on this tomorrow)
Click to expand...
Click to collapse
sawfish sorry! Will update post. ROM is in the link but I'll have to ask the dev for the source.

Lord Sithek said:
square_eyes said:
sawfish sorry! Will update post. ROM is in the link but I'll have to ask the dev for the source.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Can you share the link or the site where it was posted?.I just wanted to take a look Anyway, maybe you could try the approach from the instructions for sawshark from the opening post here. I mean extract zip and flash images separately in fastboot mode.
Also make sure you have the correct rom version for wifi variant

Lord Sithek said:
Can you share the link or the site where it was posted?.I just wanted to take a look Anyway, maybe you could try the approach from the instructions for sawshark from the opening post here. I mean extract zip and flash images separately in fastboot mode.
Also make sure you have the correct rom version for wifi variant
Click to expand...
Click to collapse
I ended up getting it working. See here for how I rolled back the Wear OS version... https://github.com/NightscoutFoundation/xDrip/issues/749#issuecomment-850037862
Below is the link from above with the files (not source sorry - I'm not sure where that's kept). If you know how to make the demigod patch compatible with the latest official firmware/or even an unofficial ROM, that would be awesome.
See Huawei Watch 2 Care Pack .zip on...
Patching Android Wear devices for use with the G5
Nightscout version of xDrip+. Contribute to NightscoutFoundation/xDrip development by creating an account on GitHub.
github.com
the zip has two patches, and instructions.

square_eyes said:
I ended up getting it working. See here for how I rolled back the Wear OS version... https://github.com/NightscoutFoundation/xDrip/issues/749#issuecomment-850037862
Below is the link from above with the files (not source sorry - I'm not sure where that's kept). If you know how to make the demigod patch compatible with the latest official firmware/or even an unofficial ROM, that would be awesome.
See Huawei Watch 2 Care Pack .zip on...
Patching Android Wear devices for use with the G5
Nightscout version of xDrip+. Contribute to NightscoutFoundation/xDrip development by creating an account on GitHub.
github.com
the zip has two patches, and instructions.
Click to expand...
Click to collapse
Great, glad it worked for you. Unfortunatelly, Im not that skillfull to help you with latest firmware...

[Guide][GSI][13] GSI Install Guide for ROG Phone zs600kl

{
"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"
}
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Introduction​ROG Phone 1 is no longer receiving any update since android 9 and no custom rom were made, which is sad since s845 is still a well performed CPU even now. However, by the help of Project Treble, we're able to install the latest android 12 (and so on) on this device.
The guide requires some basic knowledges of using SDK Platform Tools and recovery. But feel free to ask if you don't understand anything.
Hardware support​
ComponentCommentCameraWorksSpeaker / MicWorksBluetoothWorks** (Bluetooth in call, all Bluetooth codec supported by the hardware) *(No A2DP)
(Update: All bluetooth functions was now fixed on A13 and above)WiFiWorksSIM / Mobile Data / VoiceWorksVoLTEUnknownFingerprintWorks (see "workarounds and recommendations" to enable fingerprint wakeup)NFCWorksOffline ChargingBroken90Hz Refresh RateWorksAuto-brightnessWorks (May depend on the Rom)Proximity sensorWorksVibrationBrokenRGB backlight on the logoWorks* (Basic functions with an app on google play) *(Will need to set the light again whenever restart the phone)HDR content playbackBroken (Have some wired lines on the screen)
Steps to install​We have 2 ways to install, either through Fastboot or with TWRP. For data safety, I do not recommend break the force encryption whatsoever.
Make sure to Unlock Bootloader before proceeding any further!
A. Install through fastboot:
1. Extract vbmeta.img from the offical rom you're running.​
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".​3. Flash the gsi you choose in fastboot. Do "fastboot flash system (system image name.img)" .​4. Reboot to offical recovery and do a factory reset.​5. You are good to go!​
If you wish to use Magisk (I recommend Lygisk over Magisk since these gsi are force encryped), patch the boot image extract from the offical rom and flash it through Fastboot.
You can also boot to TWRP without flash it onto the device and use adb sideload to install zips, not recommend if you don't know what I'm talking about!
B. Install through TWRP:
1. Extract vbmeta.img from the offical rom you're running.​
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".​3. Flash the TWRP(attached) in fastboot. Do "fastboot flash boot twrp-3.4.0-0-Z01Q-16.0410.2003.24.img" .​4. Reboot to TWRP. Do "fastboot oem reboot-recovery".​5. Format data, cache and system parition in recovery.​6. Flash the gsi you choose in recovery. (flash the "image" into "system partition").​7. Flash any modification zips now.​8. (Optional) Flash "disforsenc_daisy__zero.zip"(attached) in TWRP to disable force encryption.​
It is not recommend to do this step if you really care about your data safety. If someone get your phone, they will be able to access all the files.
9. You are good to go!​
You can still use adb sideload to install zips(and lots of other functions) without disable force encryption. So it's really not recommend to disable it.
Workarounds and Recommendations​
To fix Bluetooth not opening or other Bluetooth related issue, refer to this guide I made. You will need Magisk to enable Aptx. This should NOT be needed anymore, since A13 builds have fix this.
Recommend to use this Gcam. It can utilize all the camera moudules and it's stable.
If you have any problem with mobile network/phone call, try to install and enable the ims apk in "phh/IMS features".
Most builds based on phh's build(which were listed on the wiki page) have a working safetynet, and the Universal Safetynet Fix will work with Magisk installed.
However some of them are still broken. So make sure the safety net is working without Magisk, then install Magisk.
RGB backlight of the ROG logo in the back can be control with this app found in google play. It's not made for this device, but basic functions will work.
My personal recommendation of gsi is crDroid maintain by Nazim. It have working safetynet and lots of customizable features I like. (Especially it can get rid of the search bar and at a glance which I HATE A LOT)
If you do want to enable fingerprint sensor while screen is off, set these two props using adb.
Code:
persist.asus.fp.wakeup=true
If you do want to use bottom usb port rather than the one on the side, set this prop. Also, to go back to the bottom one, set it to a600000.dwc3 .
Code:
persist.vendor.usb.controller.default=a800000.dwc3
If you do want to use double tab to wake, enable related settings in the GSI you use (also settings in "phh treble settings") if needed, and set this prop.
Code:
persist.asus.dclick=1
Credits​Rocky7842​xspx for testing the device with me​Numerous people and threads on the forum for some workaround or inspiration
And all the other devs for creating these wonderful modules/ROMs​

reserved

whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??

Dj.GriM said:
whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??
Click to expand...
Click to collapse
arm64 versions are all fine.

I got a rog phone 1 for a little more than a year now or so, its nice to see that we can at least have a update even if its not oficial. Im getting tyred of the same look of the UI and the aod, my god the stock ones are horrible but if i use another app for the aod it just drains the battery so fk quick. I will give a try to the pixel experience gsi

Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!

Dj.GriM said:
Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!
Click to expand...
Click to collapse
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob

Dj.GriM said:
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob
Click to expand...
Click to collapse
First of all, since the system partition on this phone is designed for android 8/9, it didn't leave much spare space. So a lot of highly modified gsi is too big for the phone. If you wish to flash them, you'll need to follow along this guide to resize partitions (tested and work).
As for the lygisk (magisk) part, take the boot image of the stock ROM you were running (the exact same version is recommended), and use the app to patch the boot.img.
Or if you have installed TWRP, simply flash the zip file through TWRP. If it's encrypted, flash it through adb sideload and it'll be fine too.

does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.

edzraaa said:
does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.
Click to expand...
Click to collapse
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.

Rocky7842 said:
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.
Click to expand...
Click to collapse
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it

edzraaa said:
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it
Click to expand...
Click to collapse
There are crDroid 9 A13 builds maintain by Nazim.
I'd recommend you to try different ROMs and versions to see which one serve you the best.

i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?

edzraaa said:
i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?
Click to expand...
Click to collapse
Welp, i think i F'd it up . Do i need to do the vbmeta.img everytime? And im not sure what to do now. Changing back to partition A stuck on ROG loading. Since i f'd up i might play around and see what i can do.
UPDATE: I got it to work finally. Flashed EVERYTHING back to "WW-16.0420.2009.39" payload.bin incase you got an error and get stucked (bootloop, wont boot). THEN follow the steps above WITH NO MISTAKES!

I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore

Yusop said:
I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore
Click to expand...
Click to collapse
That is the only way AFAIK. Try to contact Asus for help.

xT2213-1 (Austin) Moto G 5G 2022, S1SAS32.47-59-3

Any custom roms like lineage for this device? This is not kiev.

Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months

Fytdyh said:
Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months
Click to expand...
Click to collapse
I tried using a stock firmware and patched magisk but when I booted up the phone I got this

gr3uh said:
I tried using a stock firmware and patched magisk but when I booted up the phone I got this
Click to expand...
Click to collapse
{
"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"
}

You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.

Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked. .
Click to expand...
Click to collapse
I think I used the wrong firmware possibly

Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.
Click to expand...
Click to collapse
Makes no sense since I was perfectly able to unlock the bootloader using Motorola's official guide.

I recommend posting your questions here :
https://forum.xda-developers.com/t/...noob-friendly.2257421/page-2453#post-87357675
Do say what you did, what you flashed. Everyone can help you faster if you are concise and say what did you flash or did to that device. Whenever you try something, write it down.

mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it

Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!

3×5 said:
Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!
Click to expand...
Click to collapse
I've been told there will never be any progress on custom roms and firmware for this device since it is mediatek and mediatek is locked down their binaries making it hard for people to make custom rom. That being said you can try porting your own twrp or flashing a GSI.

KParsons0697 said:
mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it
Click to expand...
Click to collapse
My phone I bought it from a carrier and it was locked until payed off, paid it and waited a few days and it worked. Rooting this device was easy, just wish rom development would come sometime. I hear android 13 should be coming to this device around the beginning of Q2 of 2023

@gr3uh, thanks for the reply. I could try a GSI, but really my goal is to have an open-as-possible, de-Googled phone. I don't even really care about MicroG, or any of this. Even with no services at all, I can use Google Maps in a browser.
I assume if I install the stock firmware from lolinet, it'll have all the Google Play services. Will the phone also be rooter at that point? Or do I have to also root the phone, and then manually remove all the play services?
The big picture question is this: what's the simplest route to me De-Googling this phone?
Bonus question: why is the stock firmware hosted on a site called 'lolinet'? Maybe I don't want to know...

Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.

I should also point out that when I boot into fastbootd on the phone, it says 'Secure boot - yes' even though I flashed that empty vbmeta image and got:
Code:
target reported max download size of 268435456 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.000s]
writing 'vbmeta_b'...
OKAY [ 0.073s]
finished. total time: 0.074s

3×5 said:
Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.
Click to expand...
Click to collapse
There should be a batch file in the zip you can use to flash the dynamic partition covers everything just edit it to fit your need. And run as betch

Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)

3×5 said:
Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)
Click to expand...
Click to collapse
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.

radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Thanks for the clarification. Unfortunately, my image is just an img.xz file. There's no .bat script and no zip.
I ran fastboot getvar current-slot and it says 'current-slot: b'. Then I ran fastboot flash system_b imagefile.img.xz and I got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165282916 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
OKAY [ 9.401s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
finished. total time: 14.558s
So basically the same problem as before. I tried running 'fastboot delete-logical-partition product_b' and got:
Code:
fastboot: usage: unknown command delete-logical-partition
I could try 'fastboot flash super imagefile.img.xz' but I don't know if I'm supposed to delete super first, and I don't want to make things worse. So any advice would be appreciated.

radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Alright, I was able to flash the GSI ROM, but it didn't work. My phone thinks the OS is corrupted. I think my only choice now is to go back to my stock ROM. I tried to flash the super partition but running
Code:
./fastboot flash super ../super.img_sparsechunk.0
and it did this through sparsechunk 26. Then I rebooted and I still have no OS.
Now this stock ROM does not have a .bat file, but it does have flashfile.xml. Is there any way I can use this to automate the flashing process? At this point, I'm thinking I'm going to have to flash every partition.
Related question: In the flashfile, it specifies partitions as logo_a, vbmeta_system_a, etc. But when I run '
fastboot getvar current-slot' it says my current slot is 'b'. So should I replace every instance of _a with _b?