Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL.." (see attached screenshot). On the phone itself I see the following:
E: Can't read /dev/block/misc
(I/O error)
E: Failed to get BOX sync msg from MISC
Fastboot Reason: Reboot to bootloader
fastboot: max download size: 100Mb
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E: re-partition failed: Device or resource busy
Fastboot command failed
I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please?
Thanks,
UPDATE
Without any further tinkering on my part the phone is no longer able to boot up. It's now alternating between the "intel inside" logo and motorola logo. Also feels pretty warm. I'm kind of giving up on the device and have ordered a new phone already. If anyone has a quick fix to revive it then feel free to let me know else will use it as a nice paperweight. Thanks.
Related
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. The OS version is Android 4.1.2 Jelly bean. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL..". On the phone itself I see the following:
E: Can't read /dev/block/misc
(Bad file number)
E: Failed to get BOS sync msg from MISC
Fastboot Reason: Flash Failure
fastboot: max download size: 100Mb
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E: re-partition failed: Device or resource busy
Fastboot command failed
Fastboot menu disabled
I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please?
Thanks,
U copy/pasted another forum post , ah well it works.
It is indeed that your phones memory is corrupted.
I maybe have a solution, but first i need to know what firmware u are using.
Hazou
Hey Guys,
Recently I had just done a nandroid backup as well as following it up with a Titanium Backup. After the Titanium Backup was finished, I had been getting a core.gapps failure or something of the like so I decided to restart. After restarting, it was just stuck in a continuous bootloop.
I can still get into TWRP. First things that pop up when it starts up is:
Code:
E: Could not mount /data and unable to find crypto footer.
Unable to mount /system, /data, /cache, /firmware, storage
Unable to mount /data/media during GUI startup.
And it just repeats that. I tried to sideload, but it just throws up the same errors as it tries to mount and unmount those partitions.
I tried to reflash the boot.img in fastboot, but no matter what I try to do in fastboot, it always end in failure saying:
FAILED (remote failure)
Fastboot methods were the only fixes I could find for my problem, but it seems like I need to fix something else before I can even do that. Please help.
Sounds to me like something is messed up with encryption. Did you decrypt?
I know you will lose your data but typically pushing the fastboot files (all of them) fixes things like this
Sent from my iPad using Tapatalk
altimax98 said:
Sounds to me like something is messed up with encryption. Did you decrypt?
I know you will lose your data but typically pushing the fastboot files (all of them) fixes things like this
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
It was already decrpyted. I tried to fastboot oem unlock again in case, but it just threw out an error saying that the device was already unencrypted. I tried flashing both encrypted and unencrypted boot.img, but they all gave the FAILED (remote failure).
So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists.
After I select the zip file in the recovery mode,the installation starts. After that, it says:
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip
(Status 7)
Installation aborted.
Have you checked whether your bootloader is locked or not (because of that damned MIUI MM)? Try sending through fastboot:
Code:
fastboot oem device-info
If the "Device unlocked" comes out as false, then unlock it first by sending through fastboot:
Code:
fastboot oem unlock
It'll wipe all the content of your phone though...
shivam0909 said:
So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists.
After I select the zip file in the recovery mode,the installation starts. After that, it says:
Patching system image unconditionally...
blkdiscard failed: Invalid argument
E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Extend your partition first, you'll be fine then. There is manual tutorial in Mi3 General sub forum.
I'm not the most knowledgeable about these sorts of things and I had tried to flash AOSP onto my phone (my mistake). It is now bricked in the most unique way and I've been stuck on multiple unbricking threads due to one or two issues.
A couple things to mention:
1.
For the explanation in this thread, https://forum.xda-developers.com/realme-x2-pro/help/bricked-realme-x2-pro-twrp-fastboot-t4038999, I had followed natedogg20050's explanation up until the point of checking the system is folder is empty. I'm not sure on how to do that. Regardless I have typed "rm -r system" and "mv system_root system" into the terminal. There are no returning messages, and not sure if it is meant to return anything.
I then proceeded to attempt to flash stock fastboot images with the issue of system.img and vendor.img saying "Invalid sparse file format at header magic" without a "Finished" message at the end.
Rebooting results in the phone saying "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." error, and flashing vbmeta results in "fastboot: unknown option -- disable-verity".
2.
I had attempted to format data through twrp, with an error message returning with "Failed to mount '/data' (Device or resource busy)" and "Unable to mount storage". Similarly, attempting to flash the ozip results in "Patching firmware images...
mount: Failed to mount/dev/block/bootdevice/by-name/
userdate at /data: Device or resourse busy
script succeeded: result was [/data]
Updating partition details...
...done".
I have tried repairing the file system through twrp and it failed.
Trying to change file system to EXT2 results in "Unable to mount storage".
If anyone know the solution please help me. I'm at my wit's end here and exhausted nearly all the treads. Right now the best case scenario is that I missed a solution buried somewhere in there.
thread closed at the OP request
I'm in need of assistance in getting my Pixel 5a back up and running. I was running GrapheneOS with a locked bootloader so I'm limited on what I can do to fix it. Last week I got an OTA update and after that I started getting random boot loops, but then after about 10 restarts my phone would work, it got to the point where it would boot to the login screen but then restart as soon as I try and login. I tried to do a factory reset and get the following error:
"ERROR: recovery: [libfs_mgr]Unable to enable ext4 verity on /dev/block/by-name/metadata because /system/bin/tune2fs is missing - Formatting /data... - Formatting /metadata... - Wiping Ttan M... - ERROR: libnos_datagram: can't send spi message: Try again (I get this line 25 times)
I have tried to sideload the latest OTA update from GrapheneOS, after that I got it to boot to the start screen (like setting up the phone for the first time) I can sometimes get a few screens into it before it restarts and starts boot looping again.
It seems to me that my file system is corrupt or I'm missing the file it says in the error above "tune2fs", how can I check my filesystem or fix the missing/corrupt file?
I have posted this on GrapheneOS's forum and have gotten little to no help and I have always received excellent help here with my older phones.
Any help/advice is greatly appreciated, as of right now I have a useless device.
Thanks