Can't send fastboot flash commands to Pixel C - Pixel C Q&A, Help & Troubleshooting

fastboot devices shows the Pixel C, but any fastboot flash commands (or fastboot flashall) fail due to unsupported command errors. Any ideas what's going on? I tried reinstalling drivers and rebooting Windows 10. Those didn't help. What's wrong? Is there a fix I can make?
This device used to have a rooted copy of Marshmallow from xceed along with a TWRP installation. But those are gone. The system partition is now blank (probably along with the user and data partitions).

I had a similar issue as the device being not detected. I used Nexus Root Toolkit v2.1.8 to flash TWRP and push supersu so I could flash them.

could the partitions just be unmounted which would show as empty

Mother_Teresa said:
I had a similar issue as the device being not detected. I used Nexus Root Toolkit v2.1.8 to flash TWRP and push supersu so I could flash them.
Click to expand...
Click to collapse
My problem is different from yours. fastboot detects the device and can perform thinks like locking and unlocking. What it can't do is flash. I did try NRT. But it can't flash either as it appears to use the same driver and fastboot that I was using--just buried.

dkryder said:
could the partitions just be unmounted which would show as empty
Click to expand...
Click to collapse
Not sure who you were replying to. But the partitions (except for bootloader and recovery) are empty as they've been wiped. I wiped the system partition myself with TWRP once. Turning on and off the bootloader lock seems to have done the rest. Besides, what would that have to do with the unsupported command I got?

I misread.

Will Pittenger said:
My problem is different from yours. fastboot detects the device and can perform thinks like locking and unlocking. What it can't do is flash. I did try NRT. But it can't flash either as it appears to use the same driver and fastboot that I was using--just buried.
Click to expand...
Click to collapse
If I recall correctly--but it's been a number of months, I had a sort of similar problem with my Pixel C trying to flash a system image after unlocking the bootloader. This thread http://forum.xda-developers.com/pixel-c/help/fastboot-pixel-c-t3328635 was helpful. Selecting some generic Google driver in Win 10 did the trick, but I do not recall which driver.

tbcpn said:
If I recall correctly--but it's been a number of months, I had a sort of similar problem with my Pixel C trying to flash a system image after unlocking the bootloader. This thread http://forum.xda-developers.com/pixel-c/help/fastboot-pixel-c-t3328635 was helpful. Selecting some generic Google driver in Win 10 did the trick, but I do not recall which driver.
Click to expand...
Click to collapse
Their drivers didn't help either.

Well, I'm getting a different error. I moved the USB cable to a different port on the PC. The first port was on a hub as the 3.0 ones built into the computer were in use. I only have one on the PC itself that's on the front. The others I have to crawl under the desk and behind the computer for--and those are in use to. The new error is that it didn't like the raw file size of the img files I tried. Seems i need something that's a multiple of the block size which is 4096.

I finally have Nougat on my device.

Related

[Q] boot loop installing paranoid 4.0 beta, can't fastboot

Hi everyone,
I have a Nexus 4 and I just managed to get it in a boot loop after trying to install Paranoid Android 4.0 beta (pa_mako-4.0-BETA-20131223.zip).
I saw an update come up in goomanager so I downloaded and tried to install it, but after rebooting and starting the update from recovery mode it failed with the following message:
Code:
...
set_metadata_recursive: some changes failed
E:Error in /sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip
(Status 7)
Error flashing zip '/sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip'
Updating partition details...
After this the phone doesn't boot, it stays with the Google logo for a while, and then automatically reboots and goes to recovery.
I'm not sure what that happened. After researching a bit I found out that I may have had to update the recovery first (I'm using TWRP 2.4.4.0).
Therefore I downloaded the last version and tried to install it, but I've found another problem. When I connect the phone to the computer with a microusb cable, the phone is not recognized at all by the computer. I tried both fastboot (booting the bootloader in the phone) and ADB Sideload from the recovery. I use Ubuntu, and the phone should be listed with the command lsusb, but it's not. It's something similar to the device not coming up in the device manager on Windows. It's not listed when running either adb devices nor fastboot devices. I thought it may be a problem of having disabled USB debugging in the phone, but I read somewhere that fastboot should work nevertheless.
I tried 3 different microusb cables, 3 USB ports, 2 kernel versions in my computer and 2 different computers.
Can anybody give me some hope? :crying: Also ideas on how I may solve the problem would be really helpful.
Thanks a lot.
sepha said:
Hi everyone,
I have a Nexus 4 and I just managed to get it in a boot loop after trying to install Paranoid Android 4.0 beta (pa_mako-4.0-BETA-20131223.zip).
I saw an update come up in goomanager so I downloaded and tried to install it, but after rebooting and starting the update from recovery mode it failed with the following message:
Code:
...
set_metadata_recursive: some changes failed
E:Error in /sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip
(Status 7)
Error flashing zip '/sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip'
Updating partition details...
After this the phone doesn't boot, it stays with the Google logo for a while, and then automatically reboots and goes to recovery.
I'm not sure what that happened. After researching a bit I found out that I may have had to update the recovery first (I'm using TWRP 2.4.4.0).
Therefore I downloaded the last version and tried to install it, but I've found another problem. When I connect the phone to the computer with a microusb cable, the phone is not recognized at all by the computer. I tried both fastboot (booting the bootloader in the phone) and ADB Sideload from the recovery. I use Ubuntu, and the phone should be listed with the command lsusb, but it's not. It's something similar to the device not coming up in the device manager on Windows. It's not listed when running either adb devices nor fastboot devices. I thought it may be a problem of having disabled USB debugging in the phone, but I read somewhere that fastboot should work nevertheless.
I tried 3 different microusb cables, 3 USB ports, 2 kernel versions in my computer and 2 different computers.
Can anybody give me some hope? :crying: Also ideas on how I may solve the problem would be really helpful.
Thanks a lot.
Click to expand...
Click to collapse
From what I gather you can get into recovery mode without issue.
Simply restore a backup or try reflashing the previous version of the ROM
Anu6is said:
From what I gather you can get into recovery mode without issue.
Simply restore a backup or try reflashing the previous version of the ROM
Click to expand...
Click to collapse
Thanks Anu6is for the reply. Yes, recovery mode works, but no backups appear in the "restore" option and I can't find any either if I manually browse the file system at /sdcard. I thought I made one when first installing PA but nothing is there.
Also, no previous versions of the ROM are currently in the file system. I never thought I would need them again so I removed them to free space.
Is there a reason why ADB and fastboot would be inaccessible through USB besides a hardware failure?
Your problem is the antiquated recovery. Update your recovery
Sent from my Nexus 5
sepha said:
Thanks Anu6is for the reply. Yes, recovery mode works, but no backups appear in the "restore" option and I can't find any either if I manually browse the file system at /sdcard. I thought I made one when first installing PA but nothing is there.
Also, no previous versions of the ROM are currently in the file system. I never thought I would need them again so I removed them to free space.
Is there a reason why ADB and fastboot would be inaccessible through USB besides a hardware failure?
Click to expand...
Click to collapse
Boot into fastboot instead of recovery and update your recovery via fastboot
Pirateghost said:
Your problem is the antiquated recovery. Update your recovery
Click to expand...
Click to collapse
Thanks Pirateghost and Anu6is for confirming that the problem is an old recovery. Updating the recovery is what I'm trying to do, but as I commented in my first post I can't use fastboot, since even when I'm in the bootloader the phone is not detected by the computer when plugged.
Any idea how to fix that?
Thanks
sepha said:
Thanks Pirateghost and Anu6is for confirming that the problem is an old recovery. Updating the recovery is what I'm trying to do, but as I commented in my first post I can't use fastboot, since even when I'm in the bootloader the phone is not detected by the computer when plugged.
Any idea how to fix that?
Thanks
Click to expand...
Click to collapse
When in fastboot mode, try the command
fastboot devices
see if you computer returns anything
Anu6is said:
When in fastboot mode, try the command
fastboot devices
see if you computer returns anything
Click to expand...
Click to collapse
As I commented in my first post, adb devices and fastboot devices don't return anything. My phone doesn't even appear in the device manager. I tried different cables, different USB ports and different computers.
sepha said:
As I commented in my first post, adb devices and fastboot devices don't return anything. My phone doesn't even appear in the device manager. I tried different cables, different USB ports and different computers.
Click to expand...
Click to collapse
Yeah, sorry...that was too much to read, just scanned it.
I don't know...That's always my fallback, not sure why it wouldn't show
Sent from my Nexus 4 using Tapatalk
So I'm guessing wiping the phone is a no-no for you. Going through basics here.
So you've made sure that the daemon service is running.. .well friend i hope you get throug
Sent from my ONE TOUCH 4033A using xda app-developers app
D_Dio said:
So I'm guessing wiping the phone is a no-no for you. Going through basics here.
Click to expand...
Click to collapse
I've tried wiping caches and doing a factory reset after doing a backup (of the system already in the boot loop condition) but it didn't change anything.
If you've already got root. Can try recovery tools app to install the new recovery
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
plegdroid said:
If you've already got root. Can try recovery tools app to install the new recovery
Click to expand...
Click to collapse
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
sepha said:
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
Click to expand...
Click to collapse
My much bad. Hope you get it sorted
While iam here thou, have you updated your computers drivers for the n4? Incase that's the reason its not finding your phone.
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
sepha said:
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
Click to expand...
Click to collapse
Try cleaning your USB port on the phone with some alcohol
Sent from my Nexus 5
Pirateghost said:
Try cleaning your USB port on the phone with some alcohol
Click to expand...
Click to collapse
Thanks Pirateghost. I tried but it didn't work. I'm more and more convinced there's something wrong with the hardware. Maybe I dropped it one too many times. It was just a strange coincidence and really bad luck that I realized it didn't work just after the problem installing a new ROM.
Anyways, I ordered a replacement for the PCB that holds the microusb connector. Let's hope that works.
I solved the problem.
I managed to make the phone appear on the computer. There must be something broken in the microusb port in the phone because sometimes when I connect the phone nothing will appear on dmesg (I use Linux), sometimes I get USB errors and after trying a few times I managed to make it work.
I updated the recovery through fastboot and then I was able to successfully install the new ROM from recovery and now everything works alright.
Once the replacement board I ordered arrives I'll try replacing that and see if that fixes the USB connection problems.
Thanks to everybody who helped.

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

Only flashed vendor image to one slot; may have screwed my phone

Flashed vendor image while updating PureNexus but forgot to do it for both slots. Rebooted into system but it kept throwing "System has crashed" dialogs.
Rebooted into recovery to find TWRP gone. Went into Stock Recovery and did a Full Wipe in an attempt to fix things (I was traveling without a laptop and didn't have many options.
I can now get back into the OS, but receive a vendor mismatch error and have lost functionalities like wireless data.
I'm back with my computer but it's no longer seeing the phone (or vice versa) when I plug in. As such I can't sideload.
I also can't load through Stock Recovery because I had encrypted my phone and it can't install off SD.
At this point I just wanna go back to square one but with neither the ability to sideload nor recovery-load, I'm not sure what I can do to try to fix things.
Am I screwed? Is there a potential solution I'm overlooking? Any insight would be greatly appreciated.
Thanks!
Boot into recovery and run the flashall bat file for the full age and remove the-w to save data.
TonikJDK said:
Boot into recovery and run the flashall bat file for the full age and remove the-w to save data.
Click to expand...
Click to collapse
He no longer has TWRP. His device reverted back to stock recovery. He also can't flash a custom recovery due to his computer not recognizing the device.
I've never experienced this issue on any of my devices. These dual slots really make tinkering much more risky from all the crazy issues I've been reading on XDA.
Can you get into fastboot? If you use the "fastboot devices" command in the cmd menu where your fastboot file is located, does it show your device's serial number (I assume probably not, but it should be attempted)?
Pain-N-Panic said:
Can you get into fastboot? If you use the "fastboot devices" command in the cmd menu where your fastboot file is located, does it show your device's serial number (I assume probably not, but it should be attempted)?
Click to expand...
Click to collapse
That is where I was going, and flash the factory image. The computer not seeing the phone is a computer or cable issue he should be able to overcome.
TonikJDK said:
That is where I was going, and flash the factory image. The computer not seeing the phone is a computer or cable issue he should be able to overcome.
Click to expand...
Click to collapse
Or maybe a driver issue? If you can't get the device to be recognized via fastboot, I would try driver troubleshooting.
Pain-N-Panic said:
Or maybe a driver issue? If you can't get the device to be recognized via fastboot, I would try driver troubleshooting.
Click to expand...
Click to collapse
Yep, in stock recovery there is nothing that can cause this other than drivers, cable or computer.
Well, I suppose a bad usb port on the phone could too.
Mismatched Vendor images (so long as they are from the same version (oreo/nougat/etc)) Should not cause any of these problems.
In your specific situation, i wouldnt even bother trying any recovery process through any recovery, stock or twrp.
The best thing for you to do is back up your data, boot your phone into the bootloader, and flash a factory image.
That's the thing, 'fastboot devices' doesn't list anything (nor does 'adb devices' when I'm in system). I never had this problem before and could always see my phone via fb/adb in the past. Nothing has changed on my laptop side (same drivers, same cable, same everything). The only thing that's changed is whatever happened to the phone itself.
Is there no way to undo the nuke the phone so that it undoes the encryption? That's what I thought stock recovery full wipe would do, but the fact that I still can't mount/access the SD card must mean that it's still encrypted.
BTW as far as the vendor image goes, I flashed the NJH47D one, though I must have NOF26W in the other slot because that's what shows up under "Vendor version" in Settings/About Phone.
Troubleshooting update:
• it's not the port, because the phone can see/use a usb-c thumb drive
• it's not the drivers or cable, because I'm able to see my old Nexus 5X when I plug it in
• also, the Pixel charges when it's plugged into the computer, it just doesn't do anything else
The more I poke around, the more hopeless this situation seems. I have no idea how to get around it.
Hello OP,
Understand the urgency your want to your phone fixed but we can only allow one thread for the same content.
Here I close this one and users who are willing to help can go to this thread below:
https://forum.xda-developers.com/general/help/lost-twrp-adb-fastboot-phone-to-sideload-t3694745/
Regards
Jerry

Can't use fastboot. target didn't report max download size

Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
joedajoester said:
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Click to expand...
Click to collapse
Try a different USB port.
Ensure you have USB drivers installed first.
TonikJDK said:
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
Click to expand...
Click to collapse
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
michaelbsheldon said:
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
Click to expand...
Click to collapse
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
joedajoester said:
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
Click to expand...
Click to collapse
Just curious, but when your in the OS, and open a command prompt on the platform-tools folder and type...adb devices...do you see your device ID?? Same thing for when your in bootloader mode and type...fastboot devices...??? ?
did you fix this? im in the same boat, on p beta tried to flash factory image back to 8.1 and getting "target didn't report max download size".
Im using platform tools
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
This is likely not your issue, but if your computer has less than 4 gigs of RAM, or you are trying to flash a file larger than your available RAM you will get this message.
This (i.e. rebooting PC) worked
DanteXXL said:
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
Click to expand...
Click to collapse
This indeed worked when I rebooted my pc.

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5

Categories

Resources