Crosspost from r/GooglePixel
I enabled ADB over wifi, I installed this app Remote ADB Shell (com.cgutman.androidremotedebuggern) ran a few commands that resulted in "no command found" and a 'ls' command that read permission denied for all items before realizing it was not what I was looking for.
I don't completely remember if this app was still open or not before the device went to sleep. About 10 minutes later I notice my P3XL rebooting and going into recovery reading the standard message:
Code:
Android Recovery
google/crosshatch/crosshatch
9/PQ1A.181105.017.A1/5081125
user/release-keys
Can't load Android system/ Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
I have tried removing the SIM any other tips? Weird phenomenon.
Can you get to recovery and sideload the latest OTA? That should reflash system and not wipe any data. You mentioned you were doing ADB over wifi, which won't work for that. You will need to plug into a machine to sideload the OTA.
Is your bootloader unlocked? If it is, you could flash the full factory image. Editing the flash-all.bat file and removing the -w near the end will prevent it from wiping user data.
fury683 said:
Can you get to recovery and sideload the latest OTA? That should reflash system and not wipe any data. You mentioned you were doing ADB over wifi, which won't work for that. You will need to plug into a machine to sideload the OTA.
Is your bootloader unlocked? If it is, you could flash the full factory image. Editing the flash-all.bat file and removing the -w near the end will prevent it from wiping user data.
Click to expand...
Click to collapse
I can get into recovery. Originally, I was going to wipe cache but that's no longer an option. I'll try sideloading the latest OTA when I get home.
Bootloader is still locked. I was planning to do it this weekend and I know that will wipe user data but need to back up some app data before.
As long as you still have recovery access you should be golden. Do post your results though, please. Curious about the result.
Mission Failed: sidebooted crosshatch 9.0.0 (PQ1A.181105.017.A1, Nov 2018) successfully and... it still fails to boot.
I get a white google screen with a loading bar, then OS "Powering Down..." message, then back to Android Recovery screen.
Tried to rollback to 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) but failed because "downgrade not allowed"
Time to factory reset.
Same data corrupt issue
Hi,
My Pixel 3 XL has the same issue.
I attached it to power cable on the evening and when I came back next morning, it showed the attached screen...
Even flashing the latest OTA image via Recovery does not help.
Is there any chance to get a backup form the device with stock recovery?
I did not modify anything to the device. It is locked and original FW.
Best Regards
Marcus
if you have unlocked bootloader and have TWRP installed you can adb push and pull
mmmchen said:
Hi,
My Pixel 3 XL has the same issue.
I attached it to power cable on the evening and when I came back next morning, it showed the attached screen...
Even flashing the latest OTA image via Recovery does not help.
Is there any chance to get a backup form the device with stock recovery?
I did not modify anything to the device. It is locked and original FW.
Best Regards
Marcus
Click to expand...
Click to collapse
Use the flashall.bat and remove the -w in the file. Search for how to do this. It's been talked about quite allot
c_86 said:
Use the flashall.bat and remove the -w in the file. Search for how to do this. It's been talked about quite allot
Click to expand...
Click to collapse
Hi.
Unfortunately the flashall does not work since the bootloader is locked
Code:
Sending 'bootloader_a' (8489 KB) OKAY [ 0.309s]
Writing 'bootloader_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
Finished. Total time: 0.907s
rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.055s
Sending 'radio_a' (71148 KB) OKAY [ 2.060s]
Writing 'radio_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
Finished. Total time: 2.296s
rebooting into bootloader OKAY [ 0.050s]
...
...
Sending 'boot_a' (65536 KB) OKAY [ 1.740s]
Writing 'boot_a' FAILED (remote: 'Fastboot command (flash:) is not allowed when locked')
Any other option?
thanks
Marcus
mmmchen said:
Hi.
Unfortunately the flashall does not work since the bootloader is locked
Any other option?
thanks
Marcus
Click to expand...
Click to collapse
Are you able to access bootloader screen? If so I would run the unlock command (which will wipe the device) and they flash all
mmmchen said:
Hi.
Unfortunately the flashall does not work since the bootloader is locked
Any other option?
thanks
Marcus
Click to expand...
Click to collapse
You can update through your recovery. Download the November ota, not the system image. Flash through recovery. There are many guides for flashing OTA. Also make sure ADB tools are up to date. There are directions for flashing through recovery on the Google OTA download page if I'm not mistaken.
Bryanx86 said:
You can update through your recovery. Download the November ota, not the system image. Flash through recovery. There are many guides for flashing OTA. Also make sure ADB tools are up to date. There are directions for flashing through recovery on the Google OTA download page if I'm not mistaken.
Click to expand...
Click to collapse
Hi,
that was the first option I did try in the beginning.
It flashes fine, but after reboot, I run into the same error.
During boot, the device is reachable via ADB for a short time before it shuts down automatically and shows the error.
Is it somehow possible to use ADB to prevent the device from shutting down? Then I could try to backup a bit via ADB...
Best Regards
Marcus
mmmchen said:
Hi,
that was the first option I did try in the beginning.
It flashes fine, but after reboot, I run into the same error.
During boot, the device is reachable via ADB for a short time before it shuts down automatically and shows the error.
Is it somehow possible to use ADB to prevent the device from shutting down? Then I could try to backup a bit via ADB...
Best Regards
Marcus
Click to expand...
Click to collapse
If you had enough time you could toggle "unlock bootloader"in settings. Then in fastboot, unlock your device. This will wipe all data on your phone, but you can then flash stock firmware and maybe fix whatever issues you have.
If just backing up your data is what you want, there are ADB commands to do this. Google ADB commands and they're should be many links to give you a better understanding of it, but it's basically "ADB pull (where you want to pull from on your phone)" without quotes or parentheses.
But to fix your problem of random rebooting, I think you will need to unlock bootloader and flash stock, losing your data
I believe there may also be a way to toggle the setting of bootloader unlock via ADB if your device is on and settings is unreachable, but I am unsure how or even if it can be done on the pixel 3xl.
I would call Google for RMA.
Bumping this a month later because.... IT HAPPENED AGAIN. WTF GOOGLE.
This time just left the phone facing down for 5 minutes: Corrupt.
After this happened last time I just had to format and restore to most recent backup. I did not attempt to enable adb over wifi or use terminal, nothing outside of google use case.
TrevorT97 said:
Bumping this a month later because.... IT HAPPENED AGAIN. WTF GOOGLE.
This time just left the phone facing down for 5 minutes: Corrupt.
After this happened last time I just had to format and restore to most recent backup. I did not attempt to enable adb over wifi or use terminal, nothing outside of google use case.
Click to expand...
Click to collapse
Were you able to get your bootloader unlocked? If so I'd try flashing the factory image with the -w intact. But reading your thread it's sounding more like it's a hardware problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Were you able to get your bootloader unlocked? If so I'd try flashing the factory image with the -w intact. But reading your thread it's sounding more like it's a hardware problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, you cannot unlock the boot loader. Since the boot sector is corrupt the only you see is a powering off dialog on a black background.
I believe the problem is related to the way Pie is handling updates. I believe it is supposed to update in the background seemlessly. Everytime it has happened there has been a backup a couple or hours before.
Related
Bootlooping, adb not recognized, softbricked.
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Not sure what happened with regards to the update freeze, but we're past that point now. Your next attempt failed because the bootloader is locked, and since you now have no way to enable debugging, you may have no choice other than to try to revert to factory.
Before trying it, issue a: 'fastboot devices' command and make sure your device appears if not you may have to fix your drivers, make sure you get the right image for your device.
https://developers.google.com/android/nexus/images
EDIT: Oh crap, you don't have USB debugging enabled. Try the link anyway, fastboot should still work.
I will give it a go
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
rohanjoshi said:
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
Click to expand...
Click to collapse
Do you have a camera on the front and back? And is WiFi only? If yes, it is a FLO and you want this one.
Do you have a camera on the front and back? And has LTE and WiFi? If yes, it is a DEB and you want this one.
Based on your initial post, it looks like you have a FLO.
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
If you wanted the latest you'll want the 4.4.2...aka KitKat, that is what it was trying to update you to before this all happened. If you just want to go back to where you were, use the 4.3, but you will get prompted to update again.
Just keep in mind, runing flash-all as-is wipes everything, BUT, you can open the flash-all script in a text editor and remove the -w and it won't wipe userdata.
...also, if I may suggest, strongly, is if/when this works, and your device is backup, I suggest you unlock the bootloader first (since this wipes all data you might as well do it before you put anything on there), then go in and enable debugging. Now you can root, use adb if something happens again, etc.
rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
hey did u tried doing a factory reset from the stock recovery?
varuntis1993 said:
hey did u tried doing a factory reset from the stock recovery?
Click to expand...
Click to collapse
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
rohanjoshi said:
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
Click to expand...
Click to collapse
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
SOLVED
mdamaged said:
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
Click to expand...
Click to collapse
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
rohanjoshi said:
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
Click to expand...
Click to collapse
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
mdamaged said:
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
Click to expand...
Click to collapse
No, i understood that. I did not have the correct drivers installed and whenever I ran 'fastbook devices' nothing showed up.
I wiped all google drivers and re-installed one of the recommended packages and everything ran smoothly after that.
I was loading up my Nexus 7 (2013) with the Project L rom and ran into a problem. At the end of the install, I got an error that it could not erase the cache. I can boot into Bootloader but nothing else. It won't boot into recovery or launch the system OS. When I try to launch the system OS, I just get that updating animation that sits there for hours. Fastboot does recognize the device though, but when I try to do a fastboot erase of a partition, it just hangs. Anyone know how I can get out of this?
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
ritchea said:
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tried the process again. Whether I am trying to erase a partition, re-format a partition, or flash a partition, I get write errors. It is almost as if the rom is write-protected or something. It will copy partition images to whatever partition the bootloader is using, but just won't write them to the proper partitions.
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Check if your Android SDK is up to date
ritchea said:
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
ADB doesn't find the device any longer, although it did when I started the process. So I am left with using Fastboot. When I try to go into recovery, the screen goes black, then I get the Google logo, and it just sits there. When I try to launch into the system, I get they Andy lying down with the rotating geometric shape in his belly - forever. All that seems to work is the bootloader, and it's not really working. This is the kind of results that I am getting.
Code:
C:\Users\Daniel\Downloads\Nexus 7>fastboot devices
07b8be03 fastboot
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash recovery openrecovery-twrp-2.8.
0.1-flo.img
sending 'recovery' (7878 KB)...
OKAY [ 0.254s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.015s
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash bootloader bootloader-flo-flo-0
4.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.067s
C:\Users\Daniel\Downloads\Nexus 7>
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power]
Although I've found many instances of the write write failure you describe, no definitive answers. It does seem that Wug's Toolkit is worth a try. I read the following on his site. I realize it's about unlocking, but the point is you don't need adb to run commands from fastboot.
"WugFresh Mod Carey Parks • 4 days ago
You don't need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the "Unlock" button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use "Flash Stock + Unroot" with softbrick/bootloop mode to get your device back to normal. Cheers!"
Using the toolkit from fastboot without adb might help. (In fact, I didn't know this.) He further brought up these commands: You could also try to issue the commands (NRT advanced utilities > launch cmd prompt):
fastboot format system
fastboot format data
fastboot format cache
Of course this clears everything. But from this point, you could try the "Flash Stock+Unroot" step on the first page of the toolkit.
Have you tried to flash a totally different set of files (like the official 4.4.4 decompressed and placed into the fastboot folder)?
It is possible that your SD card has become corrupted. I'm pretty sure you can't issue any mount commands without adb so you can't set the card to write.
For the 15-20 minutes it will take to set up the toolkit and use it (it has to download files for your device, too). it may be worth the effort. Also, Wug is very good about helping. If you can provide him with a copy of what's happening (while using the toolkit), he will try to help. He really understands this stuff. If you're a "toolkit snob" (my term for those who deny usefulness of toolkits), then ignore that suggestion. You already understand how to use fastboot (which is why some say don't use toolkits). My personal experience is that the kit has helped me get out of bootloops a few times.
ritchea said:
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen.
Click to expand...
Click to collapse
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
djeaton said:
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
Click to expand...
Click to collapse
Oh, I understand on the Andy. OK. Have a great day.
Kinda weird-- http://forum.xda-developers.com/showthread.php?t=2917463different circumstances but same problem. No one responding there, either.
I don't know why this would work when wug's does not, but some claim it did http://forum.xda-developers.com/showthread.php?t=2381582. You would download, extract, click Dead_Nexus7.bat file and run from fastboot.
WARNINGS AND INFORMATION
This guide should let you take an OTA update after receiving the message “Can not update software: There was an unexpected error and the file system may be corrupted. Please contact HTC support for future assistance.”
UPDATE August 22, 2016: Through the great work of @nkk71 and @Captain_Throwback, I think it is safe to say that this method will work for any user, in any region, with any security status (S-Off/S-On). Thanks guys!
* This is a living document, so please post details of your results using this method (device variant, successful/unsuccessful).
* This will work on devices that are both s-on and s-off
I am not responsible for any damage to your device or loss of data. However, if you follow these instructions, nothing SHOULD be wiped. Keyword: SHOULD.
You're going to be flashing files here using fastboot commands. If you aren't comfortable doing that, then do not proceed. Use an RUU from HTC to return to 100% stock and then take your update.
ORIGINAL METHOD
STAGE 0 - Gather files
If you don't already know your MID, CID, and current firmware/rom versions, use "fastboot getvar all" from download mode to obtain this information.
Download TWRP System Image and Boot Image Backups for your device. These can be found for most devices in the Stock Backups thread here: http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Decompress zip file
Copy the entire folder to your TWRP Backup directory on your external SD card (this is going to be /TWRP/Backups/<DeviceSerialNumber>/)
Download the appropriate file below for your device. These files contain stock recovery and a customized android-info.txt that will restore your ability to download and install an OTA
1.80.206.1: HTC10_PMEUHL_1.80.206.1_StockRecovery_EraseDevInfo.zip
1.30.401.1: HTC10_PMEUHL_1.30.401.1_StockRecovery_EraseDevInfo.zip
1.80.401.1: HTC10_PMEUHL_1.80.401.1_StockRecovery_EraseDevInfo.zip
1.80.401.3: HTC10_PMEUHL_1.80.401.1_StockRecovery_EraseDevInfo.zip
1.90.401.5: HTC10_PMEUHL_1.90.401.5_StockRecovery_EraseDevInfo.zip
1.95.401.3: HTC10_PMEUHL_1.95.401.3_StockRecovery_EraseDevInfo.zip
1.95.401.4: HTC10_PMEUHL_1.95.401.4_StockRecovery_EraseDevInfo.zip
1.80.617.1: HTC10_PMEUL_1.80.617.1_StockRecovery_EraseDevInfo.zip
1.91.617.1: HTC10_PMEUL_1.91.617.1_StockRecovery_EraseDevInfo.zip
1.80.709.1: HTC10_PMEUHL_1.80.709.1_StockRecovery_EraseDevInfo.zip
1.92.709.1: HTC10_PMEUHL_1.92.709.1_StockRecovery_EraseDevInfo.zip
1.96.709.5: HTC10_PMEUHL_1.96.709.5_StockRecovery_EraseDevInfo.zip
1.98.709.5: HTC10_PMEUHL_1.98.709.5_StockRecovery_EraseDevInfo.zip
2.41.709.3: HTC10_PMEUHL_2.41.709.3_StockRecovery_EraseDevInfo.zip
1.53.710.6: HTC10_PMEUHL_1.53.710.6_StockRecovery_EraseDevInfo.zip
1.80.710.1: HTC10_PMEUHL_1.80.710.1_StockRecovery_EraseDevInfo
IF YOU NEED A DIFFERENT FILE, PLEASE POST A LINK TO THE OTA FOR THE VERSION THAT YOU NEED THE FILE FOR and I will create the file for you.
STAGE I - Restore stock System_Image backup in TWRP (Go here for more information and help with TWRP: http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139)
Boot to recovery
If prompted, you can select to keep system read-only
From the TWRP home screen, select Mount
Place (or verify) a check in the box to Mount system as read only
Place a check next to system in the partition list to mount
Back to home screen
Select restore
Select the TWRP System Image Backup folder you copied in Stage 0
Check both System Image and Boot
Swipe to begin the restore
When the restore is complete, reboot to DOWNLOAD mode
Back to home screen
Reboot
Download
STAGE 2 - Flash Fix Zip
Type "fastboot oem rebootRUU" to reboot to RUU mode (if you are s-off you can skip this step and flash directly from download mode with the same commands as below)
Type the appropriate fastboot command: "fastboot flash zip NAMEofZIP.zip"
It will flash the rest of the firmware package, when it's finished, issue "fastboot reboot" to reboot to system
That's all there is to it.
Once back in system, try to download the OTA again.
I hope this helps.
Even after restoring stock system from TWRP, I was unable to OTA.
This method totally worked for me. Thanks for putting this together!
x51 said:
Even after restoring stock system from TWRP, I was unable to OTA.
This method totally worked for me. Thanks for putting this together!
Click to expand...
Click to collapse
Awesome. Glad to hear it worked for you.
This step:
"fastboot flash zip SignedFirmware_1.53.617.5-1.21.617.3.zip"
Click to expand...
Click to collapse
won't it take my recovery to 1.53 version? And my system image is 1.21. How will the OTA work if the recovery does not match the system.
I am sorry if this is a dumb question but I am sort of confused.
My history: I had 1.21 stock on a US unlocked version. I unlocked bootloader, installed TWRP, backed up "System Image" and Boot and installed LeeDroid-1.0.0.
Now, I am trying to go back to stock, except that I don't have 1.21 stock recovery. I have already restored System Image and Boot from my TWRP backup.
Will doing the above work for my setup?
devsk said:
This step:
won't it take my recovery to 1.53 version? And my system image is 1.21. How will the OTA work if the recovery does not match the system.
I am sorry if this is a dumb question but I am sort of confused.
My history: I had 1.21 stock on a US unlocked version. I unlocked bootloader, installed TWRP, backed up "System Image" and Boot and installed LeeDroid-1.0.0.
Now, I am trying to go back to stock, except that I don't have 1.21 stock recovery. I have already restored System Image and Boot from my TWRP backup.
Will doing the above work for my setup?
Click to expand...
Click to collapse
Yes it will work. My setup was exactly as you described. Stock recovery is always included in the firmware packages, but isn't always modified and will usually work anyway on versions that are close.
Did it wipe your data?
devsk said:
Did it wipe your data?
Click to expand...
Click to collapse
No, but if this doesn't work then that would be the next step.
Wow, its taking forever to optimize apps.
devsk said:
Wow, its taking forever to optimize apps.
Click to expand...
Click to collapse
How many? You restored system image first, right?
jollywhitefoot said:
How many? You restored system image first, right?
Click to expand...
Click to collapse
Yes.
It looks like this worked. I am now getting the OTA....keeping fingers crossed about it installing the correctly. Then, onto testing my skype/vonage over data.
devsk said:
Yes.
It looks like this worked. I am now getting the OTA....keeping fingers crossed about it installing the correctly. Then, onto testing my skype/vonage over data.
Click to expand...
Click to collapse
Awesome. Glad to hear that.
Interesting. After OTA, its optimizing 54 apps when it optimized 56 before. OTA ate 2 apps? or 2 apps don't need optimization after OTA?
devsk said:
Interesting. After OTA, its optimizing 54 apps when it optimized 56 before. OTA ate 2 apps? or 2 apps don't need optimization after OTA?
Click to expand...
Click to collapse
Not sure. My guess would be two less apps
Everything under control. Thanks a bunch man!!
I'm running rooted stock, S-ON, I followed this guide, and everything is working fine, but I'm getting no OTAs, meanwhile a friend's phone which followed the exact same guide has been receiving them, so I'm trying to follow this guide, but I'm stuck in this part:
jollywhitefoot said:
-snip-
STAGE 2 - Flash signed firmware package
Type "fastboot oem rebootRUU" to reboot to RUU mode (if you are s-off you can skip this step and flash directly from download mode with the same commands as below)
Type "fastboot flash zip SignedFirmware_1.53.617.5-1.21.617.3.zip"
It will flash aboot and run through some initial checks and you will receive "ERROR 90, reboot and re-flush immediately"
The phone should automatically reboot back to RUU mode on it's own, if you end up back in download mode, just retype "fastboot oem rebootRUU" to return to RUU mode (again, if you are s-off and flashing from download mode, you can skip this, also the phone should boot back to download mode, but on occasion, I've seen it reboot to bootloader, in which case, just select reboot to download mode with the volume keys and power button)
once back in RUU mode (or download mode if s-off), re-issue the command "fastboot flash zip SignedFirmware_1.53.617.5-1.21.617.3.zip"
It will flash the rest of the firmware package, when it's finished, issue "fastboot reboot" to reboot to system
-snip-
Click to expand...
Click to collapse
But when I try to do fastboot oem rebootRUU I get this error:
Code:
>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.142s]
finished. total time: 0.142s
htc_fastboot finished. total time: 0.611s
And my phone doesn't appear in adb devices when in download mode. What am I doing wrong?
FenrirMX said:
I'm running rooted stock, S-ON, I followed this guide, and everything is working fine, but I'm getting no OTAs, meanwhile a friend's phone which followed the exact same guide has been receiving them, so I'm trying to follow this guide, but I'm stuck in this part:
But when I try to do fastboot oem rebootRUU I get this error:
Code:
>fastboot oem rebootruu
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.142s]
finished. total time: 0.142s
htc_fastboot finished. total time: 0.611s
And my phone doesn't appear in adb devices when in download mode. What am I doing wrong?
Click to expand...
Click to collapse
That command is case sensitive. "rebootRUU"
And adb doesn't work in download mode.
jollywhitefoot said:
That command is case sensitive. "rebootRUU"
And adb doesn't work in download mode.
Click to expand...
Click to collapse
Thanks that did it. My last phone was a Sony, this is all very new to me.
FenrirMX said:
Thanks that did it. My last phone was a Sony, this is all very new to me.
Click to expand...
Click to collapse
Glad to hear this. It took me a while to figure that one out with my first HTC, too.
So are you able to download ota now?
jollywhitefoot said:
Glad to hear this. It took me a while to figure that one out with my first HTC, too.
So are you able to download ota now?
Click to expand...
Click to collapse
No, I must have messed something else up along the way, I kept getting the system corrupted message, I just flashed the latest RUU and re-rooted. A pain to lose all my data, but well, at least I get no messages anymore when I look for updates.
FenrirMX said:
No, I must have messed something else up along the way, I kept getting the system corrupted message, I just flashed the latest RUU and re-rooted. A pain to lose all my data, but well, at least I get no messages anymore when I look for updates.
Click to expand...
Click to collapse
Sorry to hear that. Too late now, but I'm curious if it was something you were doing or if this method won't work for everyone. Anyway thanks for trying it.
I have bricked my new Pixel 3 XL after trying to root it.
I used the Magisk guide here and got as far as part 2 step 12, i.e. the last step of the actual process. When the phone rebooted, I got the expected bootloader unlocked warning, then the white loading screen for a long time, then a message saying that the system failed to load with Try Again / Hard Reset (or something to that effect) options. Choosing Try Again just repeated this boot process, choosing Hard Reset wiped the phone and then repeated the process.
I went through this about 10 times, then the phone didn't boot at all. Nothing on-screen, no connection with adb. When I tried a few hours later, I got a low battery warning icon (the phone was about about 80% when I started the process). After letting it charge for a few hours, I again get nothing on-screen. It also doesn't boot into the bootloader.
If it can't be fixed, what's the RMA status for phones that might be rooted and definitely have an unlocked bootloader?
It was a really nice phone for a few hours :crying:
QuboidRC said:
I have bricked my new Pixel 3 XL after trying to root it.
I used the Magisk guide here and got as far as part 2 step 12, i.e. the last step of the actual process. When the phone rebooted, I got the expected bootloader unlocked warning, then the white loading screen for a long time, then a message saying that the system failed to load with Try Again / Hard Reset (or something to that effect) options. Choosing Try Again just repeated this boot process, choosing Hard Reset wiped the phone and then repeated the process.
I went through this about 10 times, then the phone didn't boot at all. Nothing on-screen, no connection with adb. When I tried a few hours later, I got a low battery warning icon (the phone was about about 80% when I started the process). After letting it charge for a few hours, I again get nothing on-screen. It also doesn't boot into the bootloader.
If it can't be fixed, what's the RMA status for phones that might be rooted and definitely have an unlocked bootloader?
It was a really nice phone for a few hours :crying:
Click to expand...
Click to collapse
Google actually tells you how to unlock the bootloader so that's not an issue. Just tell them it died while you were try to do a factory reset which is the truth. You shouldn't have an issue with Google and an RMA.
But, there is another thread on here which had the same issue and the phone was able to be revived. I'll see if I can find it.
Edit, see this https://forum.xda-developers.com/showthread.php?t=3874820
Sent from my [device_name] using XDA-Developers Legacy app
That helps. Using his guide, I eventually got the bootloader to appear with Power + Volume Down. But at step 25, Power + Volume Up doesn't get any response.
QuboidRC said:
That helps. Using his guide, I eventually got the bootloader to appear with Power + Volume Down. But at step 25, Power + Volume Up doesn't get any response.
Click to expand...
Click to collapse
I would download the factory images, put the phone in bootloader and run flash all
You already did a factory reset so chances are you lost anything that was on it.
Edit: Also I'm sure you did already but make sure your adb and fastboot are up to date on your computer
hatdrc said:
I would download the factory images, put the phone in bootloader and run flash all
You already did a factory reset so chances are you lost anything that was on it.
Edit: Also I'm sure you did already but make sure your adb and fastboot are up to date on your computer
Click to expand...
Click to collapse
+1 I don't think the phone is hard bricked, I did this 2 times already when flashing ROMs, sometimes bootloader would not load without trying a few times.
Flash-all will get you running.
Follow the path !
Use the guide the guys have already posted in this thread.
I also bricked my phone the EXACT same way
Here's my one tip. If for some reason the guide to unbricking isn't working, either use a different cable, or a different computer (if possible).
Also when I bricked my phone last, the only thing it would do was boot into fastboot mode (power button + volume down ), so have faith and follow the UN brick guide !
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
Use THIS GUIDE instead when you unbrick it and want to root your new pixel!
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
hatdrc said:
I would download the factory images, put the phone in bootloader and run flash all
You already did a factory reset so chances are you lost anything that was on it.
Edit: Also I'm sure you did already but make sure your adb and fastboot are up to date on your computer
Click to expand...
Click to collapse
But how? Power + Volume Up doesn't do anything so I don't know how to get my phone to connect to my PC.
QuboidRC said:
But how? Power + Volume Up doesn't do anything so I don't know how to get my phone to connect to my PC.
Click to expand...
Click to collapse
You need to do power and volume -.
If you can get to the bootloader screen, that means you're not bricked. Also, there is slot a and b. When you download the factory image, you need to make sure you have it flashed on both slots a and b. You can get to the bootloader screen, correct?
I can get to the bootloader, now that I know how. Also, I had mistakenly thought that Power + Volume Up was needed to connect to my PC; I can use fastboot!
I can now get as far as step 32 in the repair guide I mentioned: running flash-all.bat. Running the batch file just flashes a tiny command prompt window for a fraction of a second, making no change to my device - Command Prompts seem a bit unreliable in Windows 10 (Update: I got command prompt to work, flash-all.bat does exactly the same thing), so I loaded the bat file in a text editor, and ran the commands at the Windows 10 PowerShell. The last command threw some errors:
> .\fastboot.exe -w update .\image-crosshatch-pq1a.181205.006.zip
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 1.516s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.019s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2158 MB) to disk... took 10.499s
archive does not contain 'system.sig'
extracting system_other.img (418 MB) to disk... took 2.157s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (445 MB) to disk... took 1.997s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.1-5034669
Baseband Version.....: g845-00023-180917-B-5014671
Serial Number........: 8ABY0HBQ3
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.361s
Click to expand...
Click to collapse
When I reboot, the phone loads to the bootloader and says "Enter reason: error booting boot.img" the first time. Rebooting, or booting the phone from off, then shows the bootloader immediately with the "Enter reason: no valid slot of boot". Basically, it looks like a phone that works, but has no OS installed.
I don't know how to set what slot is being flashed.
QuboidRC said:
I can get to the bootloader, now that I know how. Also, I had mistakenly thought that Power + Volume Up was needed to connect to my PC; I can use fastboot!
I can now get as far as step 32 in the repair guide I mentioned: running flash-all.bat. Running the batch file just flashes a tiny command prompt window for a fraction of a second, making no change to my device - Command Prompts seem a bit unreliable in Windows 10 (Update: I got command prompt to work, flash-all.bat does exactly the same thing), so I loaded the bat file in a text editor, and ran the commands at the Windows 10 PowerShell. The last command threw some errors:
> .\fastboot.exe -w update .\image-crosshatch-pq1a.181205.006.zip
When I reboot, the phone loads to the bootloader and says "Enter reason: error booting boot.img" the first time. Rebooting, or booting the phone from off, then shows the bootloader immediately with the "Enter reason: no valid slot of boot". Basically, it looks like a phone that works, but has no OS installed.
I don't know how to set what slot is being flashed.
Click to expand...
Click to collapse
Do you have the latest sdk platform tools? I'm pretty sure that's your problem. You need version r28.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do you have the latest sdk platform tools? I'm pretty sure that's your problem. You need version r28.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
That fixed it! I had been using the latest Minimal ADB and Fastboot, not the Android SDK Platform Tools. I'm at new-phone start page ("Hi there" / language choice/ vision settings).
Thank you very much for the help, everyone. You've saved Christmas! :highfive:
QuboidRC said:
That fixed it! I had been using the latest Minimal ADB and Fastboot, not the Android SDK Platform Tools. I'm at new-phone start page ("Hi there" / language choice/ vision settings).
Thank you very much for the help, everyone. You've saved Christmas! :highfive:
Click to expand...
Click to collapse
Glad you got it running. The platform tools changed with pie and a lot of people haven't updated. It's been the root cause of most of the flashing issues.
Sent from my [device_name] using XDA-Developers Legacy app
try using power shell instead of command. i forget what my issue was but power shell gave me better luck, but you have to do the entire path even if your in the directory
I'd recommend you put the sdk tools, fastboot and adb, in a directory. Then set a path to it in environment variables (windows). That way adb and fastboot are available no matter what directory your working in. It saves a lot of coping files and it's not as messy.
Sent from my [device_name] using XDA-Developers Legacy app
I used the ADB and Fastboot from r28 but did not install the SDK. If using command prompt, run it as an Admin (right click, run as Admin). Works flawlessly for me. As far as ADB and Recovery goes the only time it works is when you enable sideload mode. None of the normal ADB commands work.
Sent from my Pixel 3 XL using Tapatalk
I followed every step but still no luck. Just the google logo during startup and it stays there. I will leave it on that screen all night and report back but very doubtful
As to how I got into this mess...I rooted all fine, installed a custom rom and magisk. All great but then I decided to install a custom kernel for some reason which did it for me. I downloaded the EX Kernel Manager and installed the kernel within the app which got me to this mess.
You guys think I am screwed?
Edit: After trying and trying....I am up and running again.
Dodolom said:
I followed every step but still no luck. Just the google logo during startup and it stays there. I will leave it on that screen all night and report back but very doubtful
As to how I got into this mess...I rooted all fine, installed a custom rom and magisk. All great but then I decided to install a custom kernel for some reason which did it for me. I downloaded the EX Kernel Manager and installed the kernel within the app which got me to this mess.
You guys think I am screwed?
Edit: After trying and trying....I am up and running again.
Click to expand...
Click to collapse
I am now in the same shape. How did you get up and running? I have the latest platform tools. I had a custom ROM with TWRP and Magisk all working well. Then I tried a new ROM. Big mistake. I can get to fastboot without any problem. I loaded the stock December and it went without a hitch. Now stuck on Google logo.
Daisymae said:
I am now in the same shape. How did you get up and running? I have the latest platform tools. I had a custom ROM with TWRP and Magisk all working well. Then I tried a new ROM. Big mistake. I can get to fastboot without any problem. I loaded the stock December and it went without a hitch. Now stuck on Google logo.
Click to expand...
Click to collapse
What new rom did you try?
Did you flash the factory image with the flash-all batch file? And if so did you remove the -w?
Can you get into the stock recovery? If so try doing a factory reset on it.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What new rom did you try?
Did you flash the factory image with the flash-all batch file? And if so did you remove the -w?
Can you get into the stock recovery? If so try doing a factory reset on it.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Got it straightened out. Had to run flash-all.sh WITH the -w even though it wiped my phone. The ROM was Havoc ROM. Sure lived up to its name.
Hey guys I have an unlocked google pixel 2 XL running TWRP 3.3.0.0, Resurection Remix V7.0.2. and for root I was using Magisk.
I updated Magisk using the recommended installation method. The installation failed, I don't fully remember the error, but it was something along the lines, "partition not found" . After that the magisk updater recommended that I reboot. I did so but now there is the error message "Your device is corrupt. It can't be trusted and may not work properly. Visit link on another device: g.co/ABH ". You can skip the message by hitting the power button. After that You get the normal unlock warning and then the phone got stuck in the google boot screen.
After that I tried entering the recovery but that also didn't work. The phone got stuck on the TWRP boot screen.
So next I tried to reflash the recovery but I got the following error:
Sending 'recovery' (40960 KB) OKAY [ 0.975s]
Writing 'recovery' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.
schpongo said:
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.
Click to expand...
Click to collapse
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.
Badger50 said:
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.
Click to expand...
Click to collapse
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
If you can get into twrp, which you stated you can't, it might work. However, I would first flash the magisk uninstaller zip if you can get into TWRP. If none of that works, then you'll have to fastboot the factory image without the -w so as to not wipe data. You may also try flashing the stock boot.img to see if it'll boot up as well before having to get too drastic with anything else :good:
schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.
schpongo said:
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.
Click to expand...
Click to collapse
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?
Badger50 said:
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?
Click to expand...
Click to collapse
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?
schpongo said:
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?
Click to expand...
Click to collapse
USB-C to USB-C have been notorious for being rather "finicky" and not necessarily working in all cases. What does is USB-A to USB-C cables/cords -- seem to work in all cases.
I'm unsure as to why your data is not showing; whether it's not decrypting or not reading it... question;did you employ a screenlock/fingerprint lock before while the device was working? Because if you did, and it’s not asking for it to “decrypt”, then something more critical is going on and not being able to read your /data and/or /system
In any case, the main reason I wanted to chime in was to bring up something that you might be aware of already, but I wanted to confirm; when using Linux or macOS, you address the flash-all.sh file, and not attempt to launch the “flash-all.bat”.
However, it’s best if you could start from step 1 and download/re-download the Full Factory image, extract the .zip so it shows the 6 files within. Then, at this point and to make sure to cause no further issues, you should get rid of the flash-all.bat file – therefore only keeping the flash-all.sh and the flash-base.sh. Also, to retain any data, supposedly you would remove the “-w” from flash-all, but that’s how it goes for Windows and the flash-all.bat batch file; I’m unsure how to go about the same for Mac or Linux. After making sure you have the 5 correct files, move them on over to the platform-tools folder that contain the adb & fastboot .exe files – also, this would be a good time to make sure you have the most up-to-date platform-tools because, more often than not, not having the most up to date version is what usually causes most hiccups; latest version is “r29.0.5-darwin”.
And, after all of that, if you are still having issues, if you could post your output logs (if you remove the “exit” from the flash-all.bat file, it would keep the output window, but then again, that’s how to to it in a Windows environment…), it would be most helpful as to figuring out where/how things are going wrong. Usually/most likely it’s either platform-tools aren’t up-to-date or using different cords and/or on a different computer seems to be the resolutions at that point.
Hopefully this ends up being helpful…good luck!
Don't try to install twrp. Fastboot boot it