When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.
specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s
specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.
I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.
Related
hello,
today i downloaded the Android 5.0 Image from Google and wanted to flash it.
i extraced the tgz file and flashed the boot.img and system.img via fastboot.
so far so good. i reboot the tabelt and it has a bootloop.
so i used the flash-all.bat included in the tgz file but it wont flash it (didnt copied the error message)
so i tried flashing 4.4.4. but when i flash anything it wont work (fastboot flash recovery recovery.img for example)
i tried differend usb ports and with fastboot devices it shows my device.i tried rebooting the laptop and the tablet. no changes
example
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash recovery recovery.img
sending 'recovery' (5682 KB)...
after 20 min of waiting nothing changes.
my setup:
a laptop with windows 8.1
all drivers installt
original nexus 7 usb cable
drivers are working fine. i often flashed something on the n7 and my m7 bevor on this laptop
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash boot boot.img
sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
thats a error message i get when something more happens then "sending 'xxx' (xxx kb)
Code:
FAILED (data transfer failure (Too many links))
finished. total time: 85.114s
now i managed to flash recovery (TWRP)
but i cant do anything there. in the pc its not listet (adb devices) and in the log of TWRP it says
Code:
E:Unable to mount '/data'
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
etsch said:
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
Click to expand...
Click to collapse
i have the same problem how did you format it and did it fix the problem
do you have TWRP ?
you go to wipe-> advanced
there you can choose which repair and format.
ive formated one by one and then it shows the size after formating.
now my tablet booted into android (i think its ugly) but iam afraid going in the recovery
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
Code:
FAILED (remote: Error flashing partition.)
Code:
c:\tools>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.000s
I'm at a loss here, is there anyway I can fix this?
Thanks guys
jAm-0 said:
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
I'm at a loss here, is there anyway I can fix this?
Thanks guys
Click to expand...
Click to collapse
I'm sure you've already tried this but, what about the other USB ports? I had this very same issue and it took me about an hour to get my phone to recognize "fastboot -w" again.
If I recall correctly, I had to power off the PC and phone, then downgraded my Minimal ADB and Fastboot and everything started working again surprisingly, commands were recognized and I could wipe and flash with no issues.
Welcome to the club. There are a few of us now. I had this happen when trying to flash TWRP after installing the 8.1 beta. AFAIK there's nothing you can do. I've tried every combination of USB port, cable and OS. Its either a hardware error or somethings ****ed with the bootloader. Essential isn't claiming any responsibility and its just offering a $200 out of warranty replacement to US customers.
EDIT: FIXED
hi everyone, ive already rooted an essential phone in that past so i was a bit overconfident i guess, i followed all the steps in the main post https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976 but when i went to twrp to install the boot img and magisk zip i got an error that i couldnt mount to system, i realized that i had forgotten to set my mount to system so i rebooted into twrp to re instally but through system mount. it just went into a bootloop, so i decided to return my phone back to stock and redo..... well now i can wipe the device or use a flashall, my phone has no data at all, is still recognized in fastboot but it just wont work. i get errors:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.006s
and:
when trying to use fastboot -w, phone still dosent boot and flashall fails because the phone hasnt been wiped, any help please? im phoneless right now, an yes i have tried different usb cords and ports. thank you so much!
edit: not sure if its working yet but i just wiped everything through twrp so that twrp uninstalled and now the back to stock flashall seems to be working, fingers crossed!
edit 2: it goes through the whole back to stock script with everything in adb but when its done it restarts and keeps doing that. ive stopped it the second it says done as well (after it finished writing all of system b) but when i start my phone it just immediately reboots into recovery or bootloader.....
nominath654 said:
hi everyone, ive already rooted an essential phone in that past so i was a bit overconfident i guess, i followed all the steps in the main post https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976 but when i went to twrp to install the boot img and magisk zip i got an error that i couldnt mount to system, i realized that i had forgotten to set my mount to system so i rebooted into twrp to re instally but through system mount. it just went into a bootloop, so i decided to return my phone back to stock and redo..... well now i can wipe the device or use a flashall, my phone has no data at all, is still recognized in fastboot but it just wont work. i get errors:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.006s
and:
when trying to use fastboot -w, phone still dosent boot and flashall fails because the phone hasnt been wiped, any help please? im phoneless right now, an yes i have tried different usb cords and ports. thank you so much!
edit: not sure if its working yet but i just wiped everything through twrp so that twrp uninstalled and now the back to stock flashall seems to be working, fingers crossed!
edit 2: it goes through the whole back to stock script with everything in adb but when its done it restarts and keeps doing that. ive stopped it the second it says done as well (after it finished writing all of system b) but when i start my phone it just immediately reboots into recovery or bootloader.....
Click to expand...
Click to collapse
"fastboot -w" is the command to wipe all user data.
Why are you trying to wipe things through twrp?
Back to stock and add?
The script is run vis fastboot.
Which ROM are you trying to install?
Get either the latest 8.1 or P Beta from the ROM threads.
Try flashing one of those.
Did you unlock_critical?
tech_head said:
"fastboot -w" is the command to wipe all user data.
Why are you trying to wipe things through twrp?
Back to stock and add?
The script is run vis fastboot.
Which ROM are you trying to install?
Get either the latest 8.1 or P Beta from the ROM threads.
Try flashing one of those.
Did you unlock_critical?
Click to expand...
Click to collapse
hi, i had soft bricked so i tried to wipe everything to flash back to stock, anyway i got it to work, was being stupid. ill update the thread. TY!
I was asked yesterday to install LineageOS on someone's phone. It's been a few years, and I screwed some stuff up and now I need help. I'll go through what I did first and then I'll go through my current problems.
Enabled USB debugging and OEM unlock in the phone's settings.
Used ADB to reboot ot bootloader (adb reboot bootloader)
Verified the device's existence with adb.
Used Motorola's website to unlock the phone's bootloader. Process went fine.
Restarted the phone. Got the message that the bootloader was unlocked.
Went back to developer settings to re-enable USB debugging.
Rebooted to fastboot.
Typed in "fastboot flash boot twrp.img" (the file name was longer, but I'll abbreviate for the sake of brevity).
Wiped data.
Formatted data
Now, this is where the problems started. With the data formatted, I couldn't sideload anything, mounting didn't work, and the TWRP file manager showed literally nothing on the phone. No file system or anything, it looked like. This was done on a Linux computer (which also turned two of my MicroSD cards into read only. Thanks Fedora.
Anyway, I figured I should go back to fastboot to fix things. This was probably a mistake, because now I can't do anything. I can't flash TWRP, I can't boot into it, nothing. For example, when I type in
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I get this:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (27096 KB) OKAY [ 0.802s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I Googled around. Some people said I might need to flash partitions from gpt.bin, but that didn't work either. Every time, I get "invalid partition name xxx."
What can I do?
Thanks you in advance.
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Stimayk said:
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Click to expand...
Click to collapse
Try to flash with original miui ROM.
itmasen1 said:
Try to flash with original miui ROM.
Click to expand...
Click to collapse
I tried but no changes are applied
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Stimayk said:
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Click to expand...
Click to collapse
in principle, there is a solution by going through EDL MODE . you have a chance to restore your phone,
do your research on the net about this method.