Database Users

Root problem I have never had before

Hello!
I flashed a a stock 4 part firmware on my 935F a few weeks before via ODIN. Now I tried to root again to flash a custom rom and for other reasons.
The OEM and USB things needed for root to work are locked in the settings.
I have often rooted my phone, I start ODIN then I choose the TWRP .tar file and after that I directly go to the recovery mode.
First of all while starting the phone with the volume up/power/home button pressed the red text on the top of the screen is missing.
Recovery starts and there is NOTHING in the SD folder. I tried it 5 times now and always the same. The phone tells me that there is no /data folder. There is no folder at all. If I try to restore my handy it doesn't work because the folder(s) is not mounted.
I really don't know what to do. It was never a problem to root the device. I tried to unlock the "AUTO START" option in Odin, too but there is no difference. I tried the TWRP 3.2.0-1 and 3.2.0-2 always the same result.
Has anyone confirmed something like this?
The problem is flashing the stock image again and again takes much time and more serious I don't want to stress my phone to much. Now I am on stock again.
How can flashing a TWRP recovery resulting in deleting anything on the data folder, more precise the complete data folder that there isn't anything to mount or install?
Any help welcome!!
Have a nice day,
lienot

Am I really the only one?
No one ever has faced a problem like me?
Come on, it worked always I am on stock and from today twrp deletes my device or makes it invisible?
Please help!
lienot

Did you flash the dm-verity force encryption disabler?

Yes.
But before I can flash anything the sdcard is completely gone and when I flash files from the external sd card there is nothing real flashable because the internal sd is empty and without /data it doesn't work.
I really do not know. I rooted many times.
Very strange.
If I plug my phone to the computer only the Ext SD Card gets recognized.
Have a nice day,
lienot

TWRP can't see your data partition because it's encrypted and TWRP doesn't support this. You need to format your data partition in TWRP (not wipe), you will lose all your data when you do this.

Thanks, but I know the rooting guides.
The problem is:
Now I am on stock. Not rooted
I flash twrp with odin.
If I let the phone start and put the three finger combination before the twrp starts, but before the twrp is coming the small text on the top ".... is ... enforcing" is missing. Then twrp comes and everything is normal but there is no internal sd, or it is empty.
Exactly the same happens if I click "no reboot" in odin and then go to recovery.
From the very beginning there is no folder. I flashed stock again and again. Always the same happens. I never had such problem before. And I call myself "rooting experienced".
Very strange.
Have a nice day
lienot

Lienot said:
Thanks, but I know the rooting guides.
The problem is:
Now I am on stock. Not rooted
I flash twrp with odin.
If I let the phone start and put the three finger combination before the twrp starts, but before the twrp is coming the small text on the top ".... is ... enforcing" is missing. Then twrp comes and everything is normal but there is no internal sd, or it is empty.
Exactly the same happens if I click "no reboot" in odin and then go to recovery.
From the very beginning there is no folder. I flashed stock again and again. Always the same happens. I never had such problem before. And I call myself "rooting experienced".
Very strange.
Have a nice day
lienot
Click to expand...
Click to collapse
There is no internal SD from TWRP because it's encrypted by default in stock, I explained this in the previous post. TWRP cannot see or mount an encrypted partition. You need to install and boot into TWRP, go to wipe, select Format Data and type the word yes. Reboot recovery and TWRP will then see your internal storage. You can then flash your custom rom. The obvious downside of this is that everything on internal storage will be lost so take what you need off it first.

Thanks.
Sorry I typed a 10 minute answer by phone. It's gone.
Anyway I try I inform
Thanks really much
Bye
lienot
I hate writing with a phone phone

Again
"COULD NOT MOUNT /DATA AND UNABLE TO FIND CRYPTO FOOTER"
"FAILED TO MOUNT /DATA (INVALID ARGUMENT)"
Sh... Nothing works again Stock install again and again and again...
This can not be true!!
Please help me
I went directly into twrp and tried to format only DATA the above text is what has happened...
It's not good... I am getting crazy.
CU
lienot

I AM THE BIGGEST IDIOT ON THIS PLANET!​
I choose DATA but not the data I could choose and type "yes"
Man . I am an idiot - I cannot believe it.
I am just installing and doing anything I have to. If it will work I will tell you. I can't believe the mistake I have done....
Thanks a lot
lienot

I cant believe it! 15 minutes, now I am rooted and back on KING ROM and everything works as good as it should.
Somewhere I have my apps stored on my PC. I will transfer them via Titanium...
Everything can be so easy. But why are there two ways to delete the DATA folder, one with "yes" and one to click.
I just was blind that I did not see it, but it is confusing anyway.
Great, a great way to end this evening.... Now I can watch TV and make my phone as it should be again :good:
Holy s...
I am happy now
CU
lienot

Post bootloop fix problems

Hi there,
I'm hoping someone can help me with a few issues after I've gone through the bootloop fix that was posted a while ago.
I've got the phone up and running (YAY!) but it's really slow. I understand there is a zip file that can be "side loaded" but I'm not sure how that's done. I boot into the recovery mode but it asks for a password. When I cancel and just go to install there are no files that can be found, even though I copied the file into several directories on the phone.
The second thing is that despite being set to US English I don't seem to have assistant anymore. Has this happened to anyone else?
Thanks.

Did you flash the latest performance fix image from xcnathan??
Sent from my Nexus 6P using XDA Labs

mdfarazb2 said:
Did you flash the latest performance fix image from xcnathan??
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I loaded the image on the phone.
Rebooted the phone into recovery mode.
Tried to install it, but I wasn't able to find it in any directory.

madclancrew said:
I loaded the image on the phone.
Rebooted the phone into recovery mode.
Tried to install it, but I wasn't able to find it in any directory.
Click to expand...
Click to collapse
Did you click the "install/flash image" button in the lower right corner?
Sent from my Nexus 6P using XDA Labs

mdfarazb2 said:
Did you click the "install/flash image" button in the lower right corner?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I don't have an install/flash image in the bottom right.
The Install button is located at the top left, there are no files when I go in there, and the directory list seems like it's missing stuff.
There is also Wipe, backup, restore, mount, settings, advanced, and reboot.
on the advanced screen i have copy log, fix contexts, file manager, terminal reload theme and adb sideload.

madclancrew said:
I don't have an install/flash image in the bottom right.
The Install button is located at the top left, there are no files when I go in there, and the directory list seems like it's missing stuff.
There is also Wipe, backup, restore, mount, settings, advanced, and reboot.
on the advanced screen i have copy log, fix contexts, file manager, terminal reload theme and adb sideload.
Click to expand...
Click to collapse
When you browse your internal storage, you see no files/folders? Completely blank? That means you probably need to factory reset your phone once... Wipe everything including the internal storage, and did you get an option at the startup of twrp, the read only settings? And slide to confirm? Did you slide that button?
Sent from my Nexus 6P using XDA Labs

mdfarazb2 said:
When you browse your internal storage, you see no files/folders? Completely blank? That means you probably need to factory reset your phone once... Wipe everything including the internal storage, and did you get an option at the startup of twrp, the read only settings? And slide to confirm? Did you slide that button?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I see some directories, but no files and some directories are missing.
When I boot into recovery mode it asks for a password. I click cancel and then swipe right to keep going.

madclancrew said:
I see some directories, but no files and some directories are missing.
When I boot into recovery mode it asks for a password. I click cancel and then swipe right to keep going.
Click to expand...
Click to collapse
Yup... You're doing right... After going into Install section there's no option in lower right corner named flash zip or flash image? Just Bedside select storage.
Sent from my Nexus 6P using XDA Labs

mdfarazb2 said:
Yup... You're doing right... After going into Install section there's no option in lower right corner named flash zip or flash image? Just Bedside select storage.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I do see that button.
I have the file saved to the root>sdcard>Download folder. (based on the file structure from the app I'm using on the phone.
But when I'm in the recovery mode and I look in the file structure I go to sdcard and there are no subfolders.
My root directory has boot, cache, data, dev, etc, license, oem, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp twres, usb-otg, vendor.
Almost all the folders contain no further sub folders.

madclancrew said:
I do see that button.
I have the file saved to the root>sdcard>Download folder. (based on the file structure from the app I'm using on the phone.
But when I'm in the recovery mode and I look in the file structure I go to sdcard and there are no subfolders.
My root directory has boot, cache, data, dev, etc, license, oem, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp twres, usb-otg, vendor.
Almost all the folders contain no further sub folders.
Click to expand...
Click to collapse
Hello! I have the EXACT same issue in TWRP.
---------- Post added at 04:56 PM ---------- Previous post was at 04:53 PM ----------
under "select storage" it shows (0M) for internal

HEY! fixed it by downloading official TWRP and fastboot flashing it.

stewwmann said:
HEY! fixed it by downloading official TWRP and fastboot flashing it.
Click to expand...
Click to collapse
Where did you get the official TWRP from?

madclancrew said:
Where did you get the official TWRP from?
Click to expand...
Click to collapse
https://twrp.me/Devices/

madclancrew said:
I do see that button.
I have the file saved to the root>sdcard>Download folder. (based on the file structure from the app I'm using on the phone.
But when I'm in the recovery mode and I look in the file structure I go to sdcard and there are no subfolders.
My root directory has boot, cache, data, dev, etc, license, oem, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp twres, usb-otg, vendor.
Almost all the folders contain no further sub folders.
Click to expand...
Click to collapse
Oops your twrp problem then... flash the official one as suggested by stewwmann... and try again if it still doesnt work do a complete wipe including internal storage and then flash that image again via otg or fastboot pushing your file...

mdfarazb2 said:
Oops your twrp problem then... flash the official one as suggested by stewwmann... and try again if it still doesnt work do a complete wipe including internal storage and then flash that image again via otg or fastboot pushing your file...
Click to expand...
Click to collapse
Ok. I'm obviously screwing this all up.
I downloaded the file, and then went to the boot screen. I entered: ./fastboot flash recovery twrp-3.1.1-0-angerl.img that worked fine. Then I rebooted the bootloader. Then tried to go into recovery and it attempted to load, paused, rebooted and then went to normal bootup. So you're suggesting at this point that I wipe the phone and reinstall the entire 7.1.1 as well as the twrp recovery, and the bootloop fix. Then I should be able to download and install the zip file that will help with the speed issue.

madclancrew said:
Ok. I'm obviously screwing this all up.
I downloaded the file, and then went to the boot screen. I entered: ./fastboot flash recovery twrp-3.1.1-0-angerl.img that worked fine. Then I rebooted the bootloader. Then tried to go into recovery and it attempted to load, paused, rebooted and then went to normal bootup. So you're suggesting at this point that I wipe the phone and reinstall the entire 7.1.1 as well as the twrp recovery, and the bootloop fix. Then I should be able to download and install the zip file that will help with the speed issue.
Click to expand...
Click to collapse
What!? After flashing the recovery you weren't able to boot into the recovery? Something is wrong I think.. maybe you entered wrong command while flashing... As you said that worked fine so did you see something like "completed in xx.xx seconds" ? After flashing the recovery? You you have, it should be working fine..

mdfarazb2 said:
What!? After flashing the recovery you weren't able to boot into the recovery? Something is wrong I think.. maybe you entered wrong command while flashing... As you said that worked fine so did you see something like "completed in xx.xx seconds" ? After flashing the recovery? You you have, it should be working fine..
Click to expand...
Click to collapse
Yeah...it didn't work. I'm going to probably have to start from scratch I think. Though this is the third or fourth time I've had to do this.

madclancrew said:
Yeah...it didn't work. I'm going to probably have to start from scratch I think. Though this is the third or fourth time I've had to do this.
Click to expand...
Click to collapse
Before you start over,try renaming the official TWRP to just that(TWRP) That's what their website suggests. From their site:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

stewwmann said:
Before you start over,try renaming the official TWRP to just that(TWRP) That's what their website suggests. From their site:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Ok. After a few more installs it finally booted into the twrp recovery. But it still can't see anything within the directories. I'm on Install Zip, and there are no files and no sub directories within root or SDcard. Image source is internal.

madclancrew said:
Ok. I'm obviously screwing this all up.
I downloaded the file, and then went to the boot screen. I entered: ./fastboot flash recovery twrp-3.1.1-0-angerl.img that worked fine. Then I rebooted the bootloader. Then tried to go into recovery and it attempted to load, paused, rebooted and then went to normal bootup. So you're suggesting at this point that I wipe the phone and reinstall the entire 7.1.1 as well as the twrp recovery, and the bootloop fix. Then I should be able to download and install the zip file that will help with the speed issue.
Click to expand...
Click to collapse
Ok. So I am going to have to wipe the phone and install again. I just want to make sure I'm doing this right.
I will restart the phone into bootloader, then reinstall the entire OS from the start. (PATH="$PATH:/user.../ ./flash-all.sh)
That will reinstall the OS from the file I downloaded from Google.
From there I will then reinstall TWRP recovery and their fix. Then, once I've booted up the phone I will load the zip file onto it, and it should become visible in the file directory in the recovery mode.
Am I right in this?
Thanks for your help.

Accidentally wiped system

So I was going to install xXx NoLimits rom and I went to wipe my storage as to not cause and errors or mess ups. I went to select cache and dalvik/art in advanced wipe and accidentally hit system and swiped to format. Now I'm here in twrp with nothing but the root directory.
I have already tried adb sideload to get OOS back on it. It completed but nothing shows up under sdcard or in any of the root folders. I also tried adb push to the sdcard and it spits out and error. I looked back at some old forum posts and they said to install the sdcard fix in twrp but how am I supposed to get in on the phone if sideload or push don't work?
EDIT: I do have backups of OOS but have no way to get them on the phone.

I can get stuff on the phone now with push and sideload but when I sideloaded the OOS zip and tried installing it, TWRP says its corrupt! Its goes up to about 40% in powershell but the bar on TWRP says 100% and it stops the sideload command from completing. after it "finishes" powershell says "Total xfer: 1.00x"

You still can get into TWRP correct? Then once in TWRP connect your phone to your PC. Take the full zip, not the OTA and drag it into the phone and flash the full OTA. You shouldn't have to worry about sideloading with ADB. I've done this plenty of times, and one by accident as well.

Eric214 said:
You still can get into TWRP correct? Then once in TWRP connect your phone to your PC. Take the full zip, not the OTA and drag it into the phone and flash the full OTA. You shouldn't have to worry about sideloading with ADB. I've done this plenty of times, and one by accident as well.
Click to expand...
Click to collapse
It's okay I figured it out. The problem was is that I completely formatted the system partition and couldn't directly access it from my computer. My solution was to ADB push the full zip file and wait for it to finish. Then I could flash it in TWRP. This whole thing could have been made a whole lot simpler if the Team Win devs would put out 3.1.1-2 and just use the OTG capability of the unofficial one.

Wiping system is no big deal. Just flash the rom zip file and you'll be good.

PwnedBySumo said:
It's okay I figured it out. The problem was is that I completely formatted the system partition and couldn't directly access it from my computer. My solution was to ADB push the full zip file and wait for it to finish. Then I could flash it in TWRP. This whole thing could have been made a whole lot simpler if the Team Win devs would put out 3.1.1-2 and just use the OTG capability of the unofficial one.
Click to expand...
Click to collapse
Or if OnePlus added sd card reader into phone...
This is a valid argument for it...

I had your own problem, I solved buying an OTG cable and then I flashed the rom.zip from TWRP.

Stuck in recovery with no image to flash

First of all, I read this thread, but no luck.
Situation:
* I unlocked bootloader, installed TWRP 3.1.1-1 and flashed Freedom OS, succeding.
* Then I decided to try the Oreo open beta, but had a problem (error 7 flashing it), so I wanted to get back to Freedom OS
* After flashing Freedom OS again (with success) I rebooted but I was stuck at boot logo.
* I decided to flash again OOS 4.5.14, but I misclicked something and I found my self in TWRP with no ROM to flash on SDcard (I think I have checked also internal storage while wiping).
* PANIC!
So, 3 questions:
1) given that I want to stay encrypted (if still possible at this point) should I decrypt data or not at TWRP boot?
2) if I chose decrypt with the unlock code (read that I did) I have to go with decrypt or formatting is enough to keep crypt?
3) MORE IMPORTANT: how do I get a ROM to flash into the phone. Reeboting in TWRP sometimes I see the internal storage, but when I drop a firmware in it I get the transfer windows stuck at 0% and it disappear after a few seconds.
Thanks in advance to who will help me!

this might help - https://forum.xda-developers.com/showthread.php?t=2318497

chris4500uk said:
this might help - https://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
Thanks for the suggestion and... it's a beginning.
The problem is that if I sideload a small file like Magisk upload is ok, even if (obviously) it can't install.
When it comes to Oxygen OS I get I cannot read file error.
I doubleclicked the file and it opens in PC, so it isn't corrupted.

I'd be tempted to try another USB cable and maybe another computer if you have one. Failing that, if it's a problem with TWRP your last resort may be a complete low level flash. A good guide is here - https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Edit: I should say be careful if you do have connectivity problems, as flashing using unbrick tools while your connection is bad would not be a good idea at all since it could make things even worse (maybe even hard brick)

I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.

Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.

Zocker1304 said:
Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.
Click to expand...
Click to collapse
No; i couldn't. But I solved simply by using "Format data".
SOLVED

UncleDan said:
I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.
Click to expand...
Click to collapse
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.

jhs39 said:
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.
Click to expand...
Click to collapse
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]

UncleDan said:
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]
Click to expand...
Click to collapse
There are two with download links included in the instructions thread for flashing Oreo. I recommend the Blu Spark TWRP over the Chinese TWRP. It will be updated more often.

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.

Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.

v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?

Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img

v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.

You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.

Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk

v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.

SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.

Do I need to suck it up and redo the whole phone again........ :/