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

[Q] Unlocking BL and Rooting XT1068 DUAL SIM

Hello,
I recently bought a moto g 2014 XT1068 Dual Sim, and I've already updated to 5.0.2.
I really wanted to get it rooted, and as I've seen, it is only possible by first unlocking the BL.
I wanted to ask if there is a safe method to to that, since my device is Dual Sim, and I dont know if the methods provided in the forum work
I'm aware that the warranty will probably be voided (I'm from europe and bought it here also), but honestly I just want the root access.
Please just tell me, if possible, if there is any safe method to unlock the BL and after that, to root my Dual SIM.
Thank you for your patience,
maximuns

unlock bootlader install custom recovery and root
http://m.youtube.com/watch?v=BLSTDsFG1xw

Moto G User said:
http://m.youtube.com/watch?v=BLSTDsFG1xw
Click to expand...
Click to collapse
is this working on lollipop 5.0.2?

I´ve got the XT1068 dual sim too and I rooted it with this method:
1) Unlock bootloader on the Motorola homepage following this thread: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
Minimal ADB and Fastboot does the job.Unlocking BL will erase your userdata.
2) Now you have two options:
a) Flash TWRP 2.8.5.0: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149 (I used 2.8.5.0, 2.8.6.0 surely will work too)
b) Or just boot into it, the way I did : http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Command for flashing (TWRP will replace your stock recovery):
Code:
adb reboot bootloader
fastboot [B]flash[/B] openrecovery-twrp-2.8.5.0-titan.img
(You can rename the file for instance in recovery.img, then the command will be fastboot flash recovery.img)
Reboot into TWRP recovery,flash latest superSU (earlier versions will cause bootloops): http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip (it should be placed in internal or external storage) via the Install menu.
Wipe cache and dalvik.
Command for booting into TWRP ( TWRP will not be flashed on your phone, it´s just temporary.As described in the linked thread above the recovery.img-file has to resist in the adb and fastbot folder):
Code:
adb reboot bootloader
fastboot[B] boot[/B] openrecovery-twrp-2.8.5.0-titan.img
Your phone will restart in temporary custom recovery.
Flash the latest superSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip from TWRP (it should be placed in internal or external storage) via the Install menu.
Wipe cache and dalvik,reboot phone and you´re done.

maximuns said:
is this working on lollipop 5.0.2?
Click to expand...
Click to collapse
Wolfcity's method will work with Lollipop 5.0.2.
I took the same way and everything works fine.

Wolfcity said:
I´ve got the XT1068 dual sim too and I rooted it with this method:
1) Unlock bootloader on the Motorola homepage following this thread: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
Minimal ADB and Fastboot does the job.Unlocking BL will erase your userdata.
2) Now you have two options:
a) Flash TWRP 2.8.5.0: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149 (I used 2.8.5.0, 2.8.6.0 surely will work too)
b) Or just boot into it, the way I did : http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Command for flashing (TWRP will replace your stock recovery):
Code:
adb reboot bootloader
fastboot [B]flash[/B] openrecovery-twrp-2.8.5.0-titan.img
(You can rename the file for instance in recovery.img, then the command will be fastboot flash recovery.img)
Reboot into TWRP recovery,flash latest superSU (earlier versions will cause bootloops): http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip (it should be placed in internal or external storage) via the Install menu.
Wipe cache and dalvik.
Command for booting into TWRP ( TWRP will not be flashed on your phone, it´s just temporary.As described in the linked thread above the recovery.img-file has to resist in the adb and fastbot folder):
Code:
adb reboot bootloader
fastboot[B] boot[/B] openrecovery-twrp-2.8.5.0-titan.img
Your phone will restart in temporary custom recovery.
Flash the latest superSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip from TWRP (it should be placed in internal or external storage) via the Install menu.
Wipe cache and dalvik,reboot phone and you´re done.
Click to expand...
Click to collapse
Thank you so much for your reply! I'll think about it, I'm afraid of doing something wrong and get the device boken, since I'd loose the warranty, but when I decide decide to do it ill report to you the result
once again thanks!

Wolfcity said:
I´ve got the XT1068 dual sim too and I rooted it with this method:
1) Unlock bootloader on the Motorola homepage following this thread: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
Minimal ADB and Fastboot does the job.Unlocking BL will erase your userdata.
2) Now you have two options:
a) Flash TWRP 2.8.5.0: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-twrp-2-8-2-0-touch-recovery-t2979149 (I used 2.8.5.0, 2.8.6.0 surely will work too)
b) Or just boot into it, the way I did : http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2014-flash-custom-t2955243
Command for flashing (TWRP will replace your stock recovery):
Code:
adb reboot bootloader
fastboot [B]flash[/B] openrecovery-twrp-2.8.5.0-titan.img
(You can rename the file for instance in recovery.img, then the command will be fastboot flash recovery.img)
Reboot into TWRP recovery,flash latest superSU (earlier versions will cause bootloops): http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip (it should be placed in internal or external storage) via the Install menu.
Wipe cache and dalvik.
Command for booting into TWRP ( TWRP will not be flashed on your phone, it´s just temporary.As described in the linked thread above the recovery.img-file has to resist in the adb and fastbot folder):
Code:
adb reboot bootloader
fastboot[B] boot[/B] openrecovery-twrp-2.8.5.0-titan.img
Your phone will restart in temporary custom recovery.
Flash the latest superSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip from TWRP (it should be placed in internal or external storage) via the Install menu.
Wipe cache and dalvik,reboot phone and you´re done.
Click to expand...
Click to collapse
ok i've done it ahah
I just cant boot the recovery.img, it says 'No such file or directory', help???

Did you enter the path and file name correctly?
Check it again.

The recovery file has to be inside the Minimal Adb and Fastboot folder. Paste it there, open the folder, press Shift and do a right click inside the folder. From the menu choose "open a command window here".
Now enter the above adb commands.
Like Lars wrote the path must be correct. If you installed Adb and Fastboot in the root of C: the path should be " C:\Minimal Adb and Fastboot."
Just one thing,if you are annoyed by the bootloader unlocked warning screen just flash (before or after superSU) this logo.bin:https://mega.co.nz/#!cc1AGa6Y!6ctYLqVYWyfhPBU5rF1TX_r9jjF68cP3qcknAWU2DjE
That replaces the warning screen with the stock bootlogo.
Sent from my XT1068 using XDA Free mobile app

Wolfcity said:
The recovery file has to be inside the Minimal Adb and Fastboot folder. Paste it there, open the folder, press Shift and do a right click inside the folder. From the menu choose "open a command window here".
Now enter the above adb commands.
Like Lars wrote the path must be correct. If you installed Adb and Fastboot in the root of C: the path should be " C:\Minimal Adb and Fastboot."
Just one thing,if you are annoyed by the bootloader unlocked warning screen just flash (before or after superSU) this logo.bin:https://mega.co.nz/#!cc1AGa6Y!6ctYLqVYWyfhPBU5rF1TX_r9jjF68cP3qcknAWU2DjE
That replaces the warning screen with the stock bootlogo.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, got it and working flawlessly. Just a question, when I want to flash anything I can repeat the process again (Boot into twrp) with no need to flash it?

Yes you can do it but why don't you want to flash the custom recovery?

If you don´t want to flash roms,kernels etc. all the time,there is no need to flash a custom recovery. You can flash anything like superSU,logo.bin etc. by booting into TWRP, also backup/restore works this way on the Moto G. You can´t do this with a Nexus 7, it won´t boot into TWRP.
Some people want to change as less as possible as long they stay stock.When it comes to custom roms and kernels flashing the custom recovery is the better choice for sure.

Wolfcity said:
The recovery file has to be inside the Minimal Adb and Fastboot folder. Paste it there, open the folder, press Shift and do a right click inside the folder. From the menu choose "open a command window here".
Now enter the above adb commands.
Like Lars wrote the path must be correct. If you installed Adb and Fastboot in the root of C: the path should be " C:\Minimal Adb and Fastboot."
Just one thing,if you are annoyed by the bootloader unlocked warning screen just flash (before or after superSU) this logo.bin:https://mega.co.nz/#!cc1AGa6Y!6ctYLqVYWyfhPBU5rF1TX_r9jjF68cP3qcknAWU2DjE
That replaces the warning screen with the stock bootlogo.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Wolfcity said:
If you don´t want to flash roms,kernels etc. all the time,there is no need to flash a custom recovery. You can flash anything like superSU,logo.bin etc. by booting into TWRP, also backup/restore works this way on the Moto G. You can´t do this with a Nexus 7, it won´t boot into TWRP.
Some people want to change as less as possible as long they stay stock.When it comes to custom roms and kernels flashing the custom recovery is the better choice for sure.
Click to expand...
Click to collapse
Yes but if I flash the twrp will I still receive ota updates?

Yes but you need the stock recovery to install them.

Lars124 said:
Yes but you need the stock recovery to install them.
Click to expand...
Click to collapse
And can I go back to stock recovery after flash twrp?

Yes, you can flash it the same way like twrp.

Lars124 said:
Yes, you can flash it the same way like twrp.
Click to expand...
Click to collapse
you have a link for that? or the comand line?

You can get it from here:
https://www.dropbox.com/s/dedqx3cyk0yx12f/recovery.img?dl=0
command is:
fastboot flash recovery recovery.img

TWRP 3.0.2 for Acer Predator 8 ported by Ruben.

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.

Error fastboot when i flash the recovery

Hello
I try to install a custom recovery on my tf701 (android 4.3, USB debug ON)
here are the previous steps i did :
1/ i have unlock the bootloader using ASUS tools : OK
2/ i have root the TF701 : OK
for this, I installed Minimal ADB and Fastboot
I copy the files found here
and I lauch the command : adb reboot bootloader
then : fastboot boot zImage_dtb ramfs.img.gz
the root is ok
-------------------------------------------------------------------
3/ i try to install recovery
i download the file here : droidbasement.com/asus/tf701t/recovery/
i put the file in the folder of Minimal ADB and Fastboot
and i launch the commande : adb reboot bootloader
then, when the fasboot usb mode is ready on the device : fastboot flash recovery recovery.img
first time :
target reported max download size of 64382
sending 'recovery' (6652 KB)...
FAILED (data write failure (Unknown error)
finished. total time: 5.050s
second time :
target didn't report max-download-size
sending 'recovery' (6652 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.010s
Can you help me please ? I add that, when the device is ON in a normal mode (not fastboot) and connected to the PC with USB, the adb driver interface are ok :
"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
E1OKCY174091 device
"
i have tried to plug on other usb port ... it's the same ...
i have tried to reboot my computer : ... it's the same ...
i have tried to download another version of adp/fasboot (platform-tools_r28.0.2-windows.zip) : it's the same
without this installation, I can't install a custom rom ..
Many thanks in advance !

There are only two working recoveries for the TF701, one CWM without touch interface which I don't quite trust and a pretty good TWRP with touch here https://www.google.com/amp/s/forum....-kang-twrp-tf700t-2-8-x-xarea51-t3121989/amp/
The one you have there is probably the stock recovery...
The Kang TWRP is a little buggy though. You may come to a point where TWRP tells you it cannot mount /system or any other partition for that matter. All you have to do is convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.
Good luck!
Sent from my Pixel 2 using Tapatalk

Hello berndblb
Many thanks for your help
The recovery I try to install is Recovery v6.0.4.6 CWM 11.
Which one is the easier to install for a beginner ?
Because what you said previously seems difficult for me ("convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.")
Can you explain me how to do ?
Recovery v6.0.4.6 CWM 11 or Kang TWRP : can i install then the Rom "
ROM][N 7.1.2] [ KatKiss - Nougatella #037 ] for asus tf701
?
Many thanks in advance

They are equally easy to install since you just flash both of them in fastboot
But if you are asking which is easier to use, then it is the Kang TWRP. CWM does not have the drivers for the touch interface and you have to navigate everything with the vol buttons. More importantly I do not trust the "format data" function in CWM and that is crucial to install a custom rom. The issue with the corrupt file system in the Kang TWRP is a minor nuisance and you fix it right in TWRP. If you get the "cannot mount....." error, you just go to Wipe > Advanced > Change or repair file system, check the System partition and convert it to ext3 (or ext2 - does not matter). Swipe the button and when it is done (less than a minute) you repeat the step and change it back to ext4. After that everything should be good. If you want to read more about this issue search the Katkiss thread for "cannot mount"
Actually, there is another custom recovery out there which I have not tried and cannot vouch for. But maybe you go for that one, it does not seem to have the same issue and is based on a later version of TWRP: https://forum.xda-developers.com/tr...lopment/recovery-twrp-3-2-1-x-tf701t-t3720912
Read the thread, it seems to work fine. The Kang TWRP is 2.8, that one is based on 3.2.1 - both are fine to flash a Katkiss rom.
You do know that you have to fully format /data before you can flash a custom rom, right? You do that in your custom recovery (in TWRP: Wipe>Format Data, swipe the button). TWRP does a secure erase which wipes and trims every block. That's why this formatting takes around 60 minutes. Do not interrupt it!! CWM does not have this functionality, another reason I prefer TWRP..

hello berndblb and all helpers !
i have installed the Kang TWRP: it's ok
then I copy the custom rom KatKit for TF701 on /sdcard
i do a full wipe : error : "cannot mount..." : so I convert to ext2 and then I convert to ext4 the partition System and data
then i do a full wipe
my problem ... i'm sure you find it : i have erased all my data on /sdcard. No kitkat.zip yet !! :crying::crying::crying:
how to copy the rom on my tablet ?
for your information, when I am in TWRP, i can do "adb devices" on my computer :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
15C4110C61C00000009FB01C0 recovery
But push commande is failed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push KatKiss.zip /sdcard/
adb: error: failed to copy 'KatKiss.zip' to '/sdcard/KatKiss.zip': no response:
Connection reset by peer
i put kitkat.zip on a USB Key and I plug it on my docks : it seems not be recognized ...
i 'm really lost
please help !!

Put the Rom on a microSD, mate. You can navigate in TWRP to the card and flash from there
Sent from my Pixel 2 using Tapatalk

Hello !!
I have nevers seen the microsd port ! I discover it 2 days ago !
Just before your answer, a 'adb push' was successfull ! I don't know why, and the next 'adb push' for gapps ans supersu were unsuccessful...it's strange !
But all IS ok now !
I have just a last 2 questions :
1/ next Time, where Can i copy the rom (.Zip) , somewhere it will not be deleted ?
2/my tablet is not rooted now ... Is the way to root depends on the Rom ?
If I follow the steps i did when my tf701 has the rom stock, IS still good ? (https://forum.xda-developers.com/showthread.php?t=2516215)
Thanks for your help !

1) the safest place is a microSD. You can flash the Rom straight from there. But as long as you do not format your data partition - and you only need to to that if you install a different rom - you can keep it on internal storage. In most cases you only need to wipe /data, not format, and that leaves /data /media where your files live, untouched.
2) First the question is: Do you need root? You should only root your rom for a good reason. If you are not sure if you need root - you don't.
Cyber threats are multiplying. You're safer if the tablet is not rooted.
That said: you can root by just flashing the zip in recovery.
BTW, if you did not flash gapps yet, you always should flash it together with the rom, not separate. To install gapps now flash the rom, then gapps, then root (if needed), reboot
Sent from my Pixel 2 using Tapatalk

Not allowed to flash recovery anymore?

I am trying to flash the LineageOS recovery for LineageOS 18. I have previously already installed LineageOS 17 on my phone with no issues like 2 or 3 weeks ago. However, I am now trying to update to LineageOS 18 and I am now not allowed to flash the new recovery to my phone. Nothing has changed since I was last able to flash a recovery to my phone except I just changed my battery out today (since the old one was faulty), but I doubt that would interfere with the software or firmware, right? I have verified my phone is unlocked, I have verified my ADB and Pixel drivers are all up to date, and I have tried flashing on two computers, Linux and Windows. An additional thing to note that may or may not give you a clue as to what is going on is that I am able to boot into a TWRP img, but it no longer prompts me for a decryption password, and when I go to mount > decrypt and enter my pin, it says the password is incorrect.
You guys got any clue how I can fix this?
EDIT:
Here is my terminal output:
Code:
[[email protected] ~]$ sudo fastboot flash recovery /home/chris/Downloads/lineage-18.1-20210409-microG-coral-recovery.img
[sudo] password for user:
Sending 'recovery' (65536 KB) OKAY [ 1.710s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
I have to use sudo because it doesnt detect my device when I dont use sudo for some dumbass reason...

Deleted

cray12399 said:
I am trying to flash the LineageOS recovery for LineageOS 18. I have previously already installed LineageOS 17 on my phone with no issues like 2 or 3 weeks ago. However, I am now trying to update to LineageOS 18 and I am now not allowed to flash the new recovery to my phone. Nothing has changed since I was last able to flash a recovery to my phone except I just changed my battery out today (since the old one was faulty), but I doubt that would interfere with the software or firmware, right? I have verified my phone is unlocked, I have verified my ADB and Pixel drivers are all up to date, and I have tried flashing on two computers, Linux and Windows. An additional thing to note that may or may not give you a clue as to what is going on is that I am able to boot into a TWRP img, but it no longer prompts me for a decryption password, and when I go to mount > decrypt and enter my pin, it says the password is incorrect.
You guys got any clue how I can fix this?
EDIT:
Here is my terminal output:
Code:
[[email protected] ~]$ sudo fastboot flash recovery /home/chris/Downloads/lineage-18.1-20210409-microG-coral-recovery.img
[sudo] password for user:
Sending 'recovery' (65536 KB) OKAY [ 1.710s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
I have to use sudo because it doesnt detect my device when I dont use sudo for some dumbass reason...
Click to expand...
Click to collapse
There is no "recovery" partition anymore, it is in the boot.img. The "recovery" is a virtual partition that doesnt exist as its own partition. Review the steps in LOS 18.1 and it points out to flash the boot.img, then reboot to recovery once you have flashed boot.img and rebooted
Reboot to bootloader
Flash the provided boot.img to both slots (fastboot flash --slot all boot boot.img)
Reboot into recovery and factory reset for initial install
Sideload the latest build of Lineage OS (adb sideload lineage.zip)
I will also note that you seem to be using the MicroG (no GAPPs) version so I dont know if the steps are different than official LOS, but I dont think so. I would follow the dev steps to the T and not try older methods (I did the same thing I am warning against), I used my old and trusty, time tested steps, that always worked in previous devices, but do not anymore on Pixels.
It sounds like whatever happened broke your decryption of /data (but its a guess without knowing more). You might be stuck and need to format /data, or you can try to sideload the update and see if it works. Without enough info, I am guessing so provide more info and we can try to help better.
Also to note, if you use the boot.img / sideload method, you do not need TWRP, nor to mount anything. Its all done from the "native recovery" provided by LOS but you might have screwed up the/data decryption, IDK.
If this were me, and in your shoes, I would restore a FULL FACTORY image (not an OTA) with the -W left intact on BOTH slots so it rewrites my partition layout and undoes whatever funkiness' happened. You would lose everything, but it would get you back into working shape.
If you do not want to start over (and I dont disagree, it sucks), then follow the TWRP forum for coral (PX4):
TWRP Coral [Official]
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B] Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP...
forum.xda-developers.com

GROOVYJOSHCLARK said:
There is no "recovery" partition anymore, it is in the boot.img. The "recovery" is a virtual partition that doesnt exist as its own partition. Review the steps in LOS 18.1 and it points out to flash the boot.img, then reboot to recovery once you have flashed boot.img and rebooted
Reboot to bootloader
Flash the provided boot.img to both slots (fastboot flash --slot all boot boot.img)
Reboot into recovery and factory reset for initial install
Sideload the latest build of Lineage OS (adb sideload lineage.zip)
I will also note that you seem to be using the MicroG (no GAPPs) version so I dont know if the steps are different than official LOS, but I dont think so. I would follow the dev steps to the T and not try older methods (I did the same thing I am warning against), I used my old and trusty, time tested steps, that always worked in previous devices, but do not anymore on Pixels.
It sounds like whatever happened broke your decryption of /data (but its a guess without knowing more). You might be stuck and need to format /data, or you can try to sideload the update and see if it works. Without enough info, I am guessing so provide more info and we can try to help better.
Also to note, if you use the boot.img / sideload method, you do not need TWRP, nor to mount anything. Its all done from the "native recovery" provided by LOS but you might have screwed up the/data decryption, IDK.
If this were me, and in your shoes, I would restore a FULL FACTORY image (not an OTA) with the -W left intact on BOTH slots so it rewrites my partition layout and undoes whatever funkiness' happened. You would lose everything, but it would get you back into working shape.
If you do not want to start over (and I dont disagree, it sucks), then follow the TWRP forum for coral (PX4):
TWRP Coral [Official]
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B] Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP...
forum.xda-developers.com
Click to expand...
Click to collapse
Where are you getting the boot.img for lineage? I don't see one anywhere. All I've seen is recovery.img as me the rom zip.
Thanks in advance Josh.

flash713 said:
Where are you getting the boot.img for lineage? I don't see one anywhere. All I've seen is recovery.img as me the rom zip.
Thanks in advance Josh.
Click to expand...
Click to collapse
If using the official, it's provided in the download section. If not, and it's unofficial, then usually the devs of that ROM provide it. If that's not being done by the devs of the version you are using, then you need to use python and dumper script. It uses python and script (dumper) to pull out the boot.img from the payload.bin (within the zip).
Just keep in mind that I do not use the MicroG version so it's possible the steps vary but I doubt it. What I stated above is usually the method for custom, LOS, even official firmware versions to pull out the boot.img.
Send me the link to download what you're using to try and reproduce it so I can advise better (ROM/recovery/ETC).