hey everyone I'm new to xda.
so forgive me if i went wrong somewhere.
I rooted my canvas a1 (sprout 4) couple of months ago. i then had cyanogen mod on it. between these two months i had 2-3 crashes but i successfully wiped and flashed the same rom again via twrp. recently i wanted to upgrade to resurrection remix so as i wipe the data,system,cache.but none of that happened.log said unable to mount storage. unable to mount data. unable to mount cache.(invalid argument). unable to find crypto footer etc.etc.I tried every i could. accidentally i also erased recovery. and also unfortunately i kept usb debugging off. but i can bout into recovery via fastboot boot command. fastboot flash command not working. can anyone help me?plz need urgent help....
Edit: I've tried using spflashtools but everything went wrong. I used format+download. but it only formatted no download. do i lost everything oem+bootloader+recovery+os. nothing happens whatever i do to my phone. only it is recognized by pc as mediatek device. That's it.
Related
I was having some problems connecting to my mobile network, I couldn't access Google Play Store, I couldn't read Chinese well enough to figure out how to download and install new apps from China's playstore, so I decided to flash a custom OS on my P6 to play around with.
These are the steps I've taken and where it's led me to now -
Installed TWRP on my phone
Installed ADB and Fastboot onto my computer
Turned on Developer Mode and enabled USB debugging
Copied new OS Zip into my memory card
Restarted phone into TWRP recovery
Followed instructions to wipe dalvik, cache, data, and system (I'll try to find the link after this post)
Attempted to install the new OS (Failed due to incompatibility, stupid me)
Tried Sideloading an official Huawei released OS from their website (Failed to recognize my device on adb)
Tried Rebooting my device into Bootloader and attempted to load a Zip to force update my phone (and displayed "e:failed to mount /cache")
Flipped through xda and thought I needed Stock Recovery to load an official OS, so I fastboot flashed it in
Rebooted my phone into Recovery, saw "wipe data/factory reset", so I attempted that (displayed "E:failed to mount /data (invalid argument)
So... I'm stuck here, not sure what to do next because I think I'm just breaking my phone more than I'm trying to make it work... Can anyone help me out here? ._."
faye2thesky said:
I was having some problems connecting to my mobile network, I couldn't access Google Play Store, I couldn't read Chinese well enough to figure out how to download and install new apps from China's playstore, so I decided to flash a custom OS on my P6 to play around with.
These are the steps I've taken and where it's led me to now -
Installed TWRP on my phone
Installed ADB and Fastboot onto my computer
Turned on Developer Mode and enabled USB debugging
Copied new OS Zip into my memory card
Restarted phone into TWRP recovery
Followed instructions to wipe dalvik, cache, data, and system (I'll try to find the link after this post)
Attempted to install the new OS (Failed due to incompatibility, stupid me)
Tried Sideloading an official Huawei released OS from their website (Failed to recognize my device on adb)
Tried Rebooting my device into Bootloader and attempted to load a Zip to force update my phone (and displayed "e:failed to mount /cache")
Flipped through xda and thought I needed Stock Recovery to load an official OS, so I fastboot flashed it in
Rebooted my phone into Recovery, saw "wipe data/factory reset", so I attempted that (displayed "E:failed to mount /data (invalid argument)
So... I'm stuck here, not sure what to do next because I think I'm just breaking my phone more than I'm trying to make it work... Can anyone help me out here? ._."
Click to expand...
Click to collapse
By the steps you've taken i can tell you are on stock recovery at this moment and with no system installed on phone, so i would suggest you downloading an official stock rom (update.app file) and put it in dload folder in a SD card and try to install. Now one thing that you should be aware before attempting this is to make sure you have the same version of OS as the one before, either JB or KK. Good luck.
Hi I'm currently facing a problem. I Connected my phone ( ZE550ML or Z008) via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, I saw a post that said MOFD_UPDATE, on my phone comes up different. I tried flashing the latest 2.19.40.97/8.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
I was on stock MM, on december patch, then I rooted my phone, and after few days normal usage, yesterday I flashed boot animation and boot logo given in different threads in xda, today suddenly it was not properly charging, then I thought restart may fix the problem , but it doest , it is not starting. I have tried everything, but cant able to do anything, even flashing lollipop from sp flash tool is not working. When i flash custom rom cm13 from recovery it shows
* unable to mount /system
* unable to mount /cache
* unable to mount /data
* unable to mount /oem
and nothing is happening, when flashing lollipop from sp flash tool, even custom recovery is not going, it is still there.
pls help me urgently.
I have same problem with my phone.I tried in all ways but not working
try to push rom by ABD sideload may be it can help.
Google How to push rom from ADB side load.....
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Janxr said:
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Click to expand...
Click to collapse
Just simply download and flash the Apollo's stock Fastboot ROM in fastboot mode
I tried flashing with with this: "apollo_global_images_V13.0.5.0.SJDMIXM_20220704.0000.00_12.0_global_3391fe8ef8"
is that the right version for my phone (bought in Germany)? I dont get an error while flashing but i just is not finishing. Its running for an hour now and still nothing happended. Ill update this if it finishes.
Edit: False alarm: After restarting the pc, i can connect again. But I still dont know what to do now.
I stopped the process after 2 hours and it got worse. In the recovery, i get the same issues as before, but my fastboot menu got replaced by onother one (I just see orange text that says fastboot). With that new fastboot menu I can not connect to my computer anymore.
Solved: I will never touch these Xiaomi tools again. platform-tools is just better and works
How did you solve the problem with the phone that cant connect to pc?