Database Info

Can't get my new tf700t to root or install recovery.

Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?

benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....

LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.

benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?

benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891

benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.

That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?

benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!

Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.

I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you

I have almost the same problem as if the fastboot not install anything despite not display errors

great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.

do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom

Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!

ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors

angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.

ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

Need Valid Backup File

Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>

N101BL said:
Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
Click to expand...
Click to collapse
A 504 error is a network error and has nothing to do with your phone or it's backup. http://pcsupport.about.com/od/findbyerrormessage/a/504error.htm You should research these error's or post a question before doing things that end up making the situation worse. At this point you need to restore your backup and don't do anything till you read the tutorials on how to install TWRP (which has it's own built in way to root the device) or read a supersu tutorial on how to root the device after twrp is up and running correctly THEN if you have issues ask your question in the proper thread...you say you are "booting" twrp...booting twrp means it's not installed and you are running the fastboot boot command. If you meant "booting INTO twrp" by using the vol up key while the phone is booting then you should clarify. You should also be verifying your supersu zip file has the proper size/md5sum. If your backup is not valid (or you didn't bother to make one) then go to the stock image thread and download the most recent image for your model and flash that via twrp.

Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
famewolf said:
go to the stock image thread and download the most recent image for your model and flash that via twrp.
Click to expand...
Click to collapse

N101BL said:
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
Click to expand...
Click to collapse
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".

Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
famewolf said:
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Click to expand...
Click to collapse

N101BL said:
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
Click to expand...
Click to collapse
While your thought is appreciated we currently have all the versions of stock that we need for the 6045i. The next time start by flashing twrp (not just booting it) following the tutorial in the twrp thread step by step...after twrp is installed boot into it and make a full backup for your OWN use before trying to root. I can't emphasize this enough...follow the tutorials..don't just jump out and start running whatevr. Your system was fine when you had the 504 network error...it was also STILL fine when you restored your backup and "continued to get the 504 error". It was after that you went off on a tangent somewhere. If you cause Alcatel enough grief they can check your returns for the presence of modifications such as attempting to root and opt to void your warranty especially after multiple returns.

Stuck in a bootloop, please help

Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]​
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.

Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?

next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.

NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?

You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....

Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.

Google Pixel - No apply update from ADB in recovery and other strange things

Hello everyone,
The starting situation is the Google Pixel of my mother was stuck on android 8.0. While showing there was an update available, the update would always fail to install after the reboot in the process. I found advice to factory reset the phone and then update, but this didn't help.
So my first thought was, if the update won't install the normal way I will do it manually. Google OTA installation guide says, get file (latest), reboot to recovery, plug in to USB, choose apply update by adb.
At this point the guide loses me, because the recovery screen I get to only lists reboot, reboot bootloader, simlock tool and device info tool (see picture). The device info will only tell "failed to update device info". The simlock tool just says "failed to enable simlock". Further while on this screen the phone isn't visible as an ADB device any more.
Next thing to try cause this didn't work was getting the image file (latest) from Google and flashing it through fastboot flash all, which led to a boot loop and the phone not starting at all. So I went and flashed back to the android 8 that was on it before and the phone booted again, but I'm still not any step further.
Next idea was maybe the recovery is broken somehow, so I went to install TWRP. Following the instructions I copied the latest version zip onto the phone and booted the img through fastboot. So far everything is fine, but when I install the zip I will get several errors about "can't mount /persist". And the installation won't work.
At this point I am out of ideas, so maybe someone here can tell me if and how this can be fixed? I wasn't able to find any information on this issue, aside from some xiaomi phones can show similar errors with the /persist partition and TWRP.
Any help would be welcome.