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
Related
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.
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.
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Ankeroth said:
Hello everyone. My problem is bootloop. I searched this forum before I post my own problem. Im trying to solve bootloop problem for 2 days. So I learned couple things. I had no idea what was fastboot and adp before.
Let me tell you what caused bootloop. I was using 6.0.1 firmware and my phone started working slowly. So I thought maybe new update fix that. I updated my phone and it was still slow. Then I looked that up on the internet. Some people said wipe your cache that might fix slow working zenfone. I put my phone on recovery mode and wiped cache and it caused bootloop. I started to search for my new problem. Found one with cmd command flashall. It turned my phone firmware to 1.17.40.1234 from 21.40.1220.2179. And then I downloaded raw ze550kl rom for my current firmware which is 1.17.40.1234. Extracted recovery.img boot.img and system.img
and used following commands :
fastboot devices
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system.img
fastboot commands worked with no problem and then I switched to recovery mode again and used this command:
adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip.If I tried to use raw rom as i mentioned before ,cmd says *cannot read. So I used this firmware from asus website.
last command causes this error on pc
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip
loading: 'ZE550KL_WW_1.17.40.1234-20180205T165447Z-001.zip'adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
Total xfer: 0.00x
and on my phone this error shows up
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Bootloop problem still exists so I tried to use different method which was flashtools. I got "Run flash image script failured" error. I tried to fix it but no luck.
Lastly I tried to apply update from sdcard but my phone cant read on sdcard for some reason and that sdcard is being used my little brother(it works).
What can I do to revive my phone ? Please help me.
Click to expand...
Click to collapse
First download latest official build and don't do any edit or repack of zip .. Copy that ROM in the SD card make sure SD card works or format SD card into fat32 file system and copy ROM in it .. Go to phone recovery .. Hit update from SD card choose the zip wait till it flash if u still fail comment here .. I will give u alternatives
hi, i recently installed twrp for my dora and attempting to repair phone from dead boot (maybe)
when i was trying to install custom rom , log says
failed to mount '/idd' invalid argument
failed to mount '/oem' invalid argument
failed to mount '/qns' invalid argument
and the "backup" part it says
Cache (0mb)
Diag (0mb)
OEM (0mb)
Qnovo (0mb)
tried to push manually via fastboot but failed
looking for flashable zip stock rom for this AU SOV33 is pretty hard to find since this phone wont go into flashmode
any solutions on this case?
if someone kindly shares some backup stock rom via twrp i would be so thankful
thanks
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