Hi Guys! Im from the Philippines. I have Mi3 bought from SG last June 2014. Last Tuesday, the phone suddenly had a problem when I wake up in the morning.
ROM version 23 (stable), Rooted.
Problems below:
Processes/app that stop during standy (Phone On, no apps running)
android.process.acore
settings
com.google.process.gapps
music
google play services
launcher
When opening Camera, error is flagged "can't connect to camera"
Messaging app stops (default messaging app)
When trying to restore factory default (erase all app, data, etc) phone resets but apps/data
are still there.
Can't erase any data in the phone.
Can't put data to phone (example: Picture from pc to phone). When I tried to copy data to
phone, window pop-up saying the device was disconnected or stopped working.
I can read/copy any data from the phone. (example: copy picture from phone to PC)
Tried to go to mi-recovery and tried the ff:
Wipe cache - ok
Wipe used data - failed
Wipe all data - ok - but when the phone restarted, data is still there.
Wipe sd card - ok
I can't flash rom to phone via recovery since I dont have update.zip on my phone.
Again, when the phone restarted, data is still there and the problem is there.
Tried to flash phone via fastboot using MiFlash 2014.05.09, the results are below:
ROM version: cancro_images_KXDCNBF24.0_4.4_cn_1fbb634ef8 and cancro_images_JXDCNBD14.0_4.3_bb5096bfd9
Using flash_all_except_data_storage.bat
- operation completed. but when phone restarted, the problem and data are still there.
Using flash_all.bat
- operation stopped with Unspecified error0x8000405: FAILED (remote: failed to erase partition)
Additional info:
I still can make calls in my phone. FM radio is working. Music player is working.
Question:
What's next? anything I can do to fix this?
Thanks.
beginner_wan said:
Tried to go to mi-recovery and tried the ff:
Wipe cache - ok
Wipe used data - failed
Wipe all data - ok - but when the phone restarted, data is still there.
Wipe sd card - ok
I can't flash rom to phone via recovery since I dont have update.zip on my phone.
Again, when the phone restarted, data is still there and the problem is there.
Tried to flash phone via fastboot using MiFlash 2014.05.09, the results are below:
ROM version: cancro_images_KXDCNBF24.0_4.4_cn_1fbb634ef8 and cancro_images_JXDCNBD14.0_4.3_bb5096bfd9
Using flash_all_except_data_storage.bat
- operation completed. but when phone restarted, the problem and data are still there.
Using flash_all.bat
- operation stopped with Unspecified error0x8000405: FAILED (remote: failed to erase partition)
Additional info:
I still can make calls in my phone. FM radio is working. Music player is working.
Question:
What's next? anything I can do to fix this?
Thanks.
Click to expand...
Click to collapse
Install CWM recovery first then do the below things from recovery,
1) Wipe data/factory reset
2) Wipe cache
3) Wipe dalvik cache
4) Format system 1 and system 2 from mounts and storage menu
5) format data
6) Power off the device and go to fastboot mode
7) Try to install Fastboot rom again with the option 'flash_all_except_data_storage.bat' using mi flash tool
it should works.
Hello sujithar37. Thanks for the response. What CWM recovery should I install? And how can I install it? I tried to install CWM_recovery_r7_cancro_final.zip using RayGlobe tools but when I tried to reboot the phone it boot loop. Am I doing anything wrong? Thanks.
beginner_wan said:
Hello sujithar37. Thanks for the response. What CWM recovery should I install? And how can I install it? I tried to install CWM_recovery_r7_cancro_final.zip using RayGlobe tools but when I tried to reboot the phone it boot loop. Am I doing anything wrong? Thanks.
Click to expand...
Click to collapse
Please do click on thanks button rather than your sentence. That was I liked lot . Please check below the thread for detailed recovery installation .
http://forum.xda-developers.com/showthread.php?t=2830538
Sent from my MI 3W using XDA Free mobile app
I have the same problem.
If I try to flash cancro_images_4.11.14_4.4_cn with flash_all, after about 63 seconds I get this message:
(Unspecified error(0x800004005: FAILED (remote: failed to erase partition)..
I believe it fails on the fastboot %* flash userdata %~dp0images\userdata.img command
I can adb boot a recovery image, but any wipes/cleans/ etc say they work, but do nothing. My clockworkmod log shows:
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I was able to use adb pull and get photos off, but when I try to write an update.zip with adb push update.zip /sdcard/ I get a message saying that I don't have permission to do so.
Is this perhaps a permission issue?
Hi beginner_wan, you have got to fix this error?
how to do it?
description of my dance with tambourines -> http: en.miui.com/forum.php?mod=viewthread&tid=427670
If anyone knows how to check for NAND memory errors, help ...
I've bought a used Moto G 2014 XT1068 with a software bug trusting that i can get it to work again.
It shows the message "Warning Bootloader Unlocked". So i activated AP fastboot mode by holding PowerButton and VolDown. Then I flashed TWRP_2.8.0.1_Titan_v2, TWRP2.7.1.1-titan-motog-2014 and twrp-2.8.6.0-titan via ADB but it none of them is starting when i select the recovery button in fastboot mode. Instead of Teamwin logo it goes to the laying android with red triangle.
Then i tried to boot the recovery.img via ADB with "fastboot boot XXX.img" and then the Teamwin logo arises but it stucked with any TWRP i used.
Then i tried to use CWM_Touch_Titan_v2.img in the same way and it worked (only with ADB command again). So i wanted to wipe all to install a new ROM but then it stucked while it says: Formatting /data...
When i try to install a ROM by choosing the .zip-file form /external_sd it seems to work but a few seconds later the message is:
PhilZ Touch 6
Clockworkmod v6.0.4.7
-- installing: /external_sd/Stock_XT1068_22.21.28-ROM.zip
Finding update package...
Opening update package...
installing update...
>>> XT1068 Stock Lollipop Firmware [22.21.28] <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
E: Error in /external_sd/Stock_XT1068_22.21.28-ROM.zip
(Status 7)
Installation aborted.
E: cannot write to /sdcard/clockworkmod/.last_install_patch
press any key to continue
Click to expand...
Click to collapse
I don't know what to do anymore
nilsxvx said:
I've bought a used Moto G 2014 XT1068 with a software bug trusting that i can get it to work again.
It shows the message "Warning Bootloader Unlocked". So i activated AP fastboot mode by holding PowerButton and VolDown. Then I flashed TWRP_2.8.0.1_Titan_v2, TWRP2.7.1.1-titan-motog-2014 and twrp-2.8.6.0-titan via ADB but it none of them is starting when i select the recovery button in fastboot mode. Instead of Teamwin logo it goes to the laying android with red triangle.
Then i tried to boot the recovery.img via ADB with "fastboot boot XXX.img" and then the Teamwin logo arises but it stucked with any TWRP i used.
Then i tried to use CWM_Touch_Titan_v2.img in the same way and it worked (only with ADB command again). So i wanted to wipe all to install a new ROM but then it stucked while it says: Formatting /data...
When i try to install a ROM by choosing the .zip-file form /external_sd it seems to work but a few seconds later the message is:
I don't know what to do anymore
Click to expand...
Click to collapse
Try flashing using twrp. Some roms don't flash properly with cwm , connect ur phone to ur PC, enter bootloader mode, and open command window(shift + right click) from ur adb folder (place twrp 2.8.6 img in that folder, rename it as twrp ,remove the 2.8.6 n img ) and enter, adb devices (in cmd window) , if it shows connected, enter fastboot flash recovery twrp.img , then unplug and select recovery from bootloader menu. Take backup of rom, n wipe system, data and cache and flash rom, gapps n supersu.
Hope this helps, pm me if u need help.
Sent from my Moto G 2014 using Tapatalk
This is true, i had this same problem ,i rename as twrp , no 2.8.6 .img etc.. twrp flashed.
It worked now. I couldn't start twrp by selecting recovery from bootloader menu but i started twrp with ADB via "fastboot boot twrp". It showed just the teamwin logo first for about 15 minutes but then it started twrp. So i pressed the log button to see why it took so long. There were hundreds of red messages.
The Message is always like: "E: Unable to stat '/data/..."
I tried to wipe my data and cache. Dalvik cache und cache worked fine but when it comes to data there are always the messages "E: Unable to stat '/data/..."
I get the the same messages when i try to install a ROM.
Is it possible that my internal storage is broken? :crying:
The Good:
I can charge the battery, boot to CWM, WebOS Recovery or TPTB_v42 from moboot.
The bad:
If I boot to CM the Android icon shows for a few minutes and then the screen goes blank and stays blank.
In TP Toolbox I can Flash A6 and Mount Media Volume
Repair Android Volumes fails with
"e2fsck unable to set superblock flagts on dev/store/cm-cache"
and "Failed to correct errors on volume cm-cache."
Resize Android Volumes returns: "Help File 'confirm_repair_bad' is missing" and e2fsck -fp detected error on fs on vol cm-cache rc=8"
Complete Data Reset returns: "Failed ERROR LUM config erase check FAILED. Possible read-only failure.
In CWM
I can install zip but it makes no difference to above.
I wiped cache partition and Dalvik - no change to above
I formatted cache - no change to blank screen
I think I need to do the equivalent of an fdisk through novaterm but am at a loss of how to accomplish this. Any help would be greatly appreciated.
hi. i'm having the same issue. TP was working fine until a few weeks ago. i'm trying to just start over but i'm seeing the same "bad" as you. Even after doing a factory reset within android, it just reboots and everything is still there.
Hoping someone can assist.
Carey4782 said:
The Good:
I can charge the battery, boot to CWM, WebOS Recovery or TPTB_v42 from moboot.
The bad:
If I boot to CM the Android icon shows for a few minutes and then the screen goes blank and stays blank.
In TP Toolbox I can Flash A6 and Mount Media Volume
Repair Android Volumes fails with
"e2fsck unable to set superblock flagts on dev/store/cm-cache"
and "Failed to correct errors on volume cm-cache."
Resize Android Volumes returns: "Help File 'confirm_repair_bad' is missing" and e2fsck -fp detected error on fs on vol cm-cache rc=8"
Complete Data Reset returns: "Failed ERROR LUM config erase check FAILED. Possible read-only failure.
In CWM
I can install zip but it makes no difference to above.
I wiped cache partition and Dalvik - no change to above
I formatted cache - no change to blank screen
I think I need to do the equivalent of an fdisk through novaterm but am at a loss of how to accomplish this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Minus Toolbox, I am having this exact same problem. Have either of you figured out how to fix it yet?
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
Make sure to follow this guide precisely, as order matters. At the end, I will post an explanation of why we need to execute these steps. I spent an entire weekend of trial and error on my Huawei Honor Note 10, and now I have figured out the ins and outs so you don't have to. You're welcome
Prerequisites
Huawei Honor Note 10 device, either on stock ROM or rooted (doesn't matter)
MicroSD card (formatted exFAT or FAT, doesn't matter)
Bootloader unlock code for Huawei Honor Note 10 (follows a format like my own HBP38K14DBK2RNB4)
Computer with admin privileges
Before You Flash Anything
Back up, back up, back up! I am not responsible if you lose valuable or sensitive data. Your Huawei Honor Note 10 will factory reset a number of times (probably more) before you can get back up and running again. Either use TWRP to do this, or use HiSuite (not recommended but will work on a locked bootloader).
Remove your SIM card! Your carrier may get charged ridiculous amounts of fees if you have a limited data plan, such as 256MB (Canada has notoriously expensive phone plans, so Canadians beware). When you reboot, expect Huawei's stock ROM to use copious amounts of data on retrieving the latest version of bloatware and spyware.
Ensure you have stock recovery installed. If you don't, download the stock recovery image, place it in your Minimal ADB and Fastboot folder, then boot to download mode by holding the VOLUME DOWN button and simultaneously plug in in your Huawei Honor Note 10 device, then open Minimal ADB and Fastboot on your computer and run this command:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Steps to Install Custom ROM on Huawei Honor Note 10
Download the EMUI 9 stock ROM and place the dload folder on your MicroSD card
Boot to (stock) recovery by holding down the VOLUME UP, VOLUME DOWN, and POWER buttons at the same time. The update should begin immediately. Wait patiently for your phone to reboot
Fill out the bloatware questionnaire by Huawei and download any and all updates under Settings. This will ensure you have the latest boot image. You will reboot at least once.
Once you have completed all the updates, reboot to download mode; press and hold the VOLUME DOWN button while you plug in your Huawei Honor Note 10 device to your computer
On your computer, download and open Minimal ADB and Fastboot
Run the following command:
Code:
fastboot oem unlock <code>
(where code corresponds to a format that looks like this: HBP38K14DBK2RNB4)
Confirm unlocking your bootloader by using the VOLUME keys, selecting yes, and pressing the POWER button. The Huawei Honor Note 10 device will now perform a factory reset
IMPORTANT step. DO NOT let the Huawei Honor Note 10 reboot. DO NOT. Impatiently wait for the low-level factory reset to complete and as soon as it does, enter download mode again by pressing the VOLUME DOWN key and plugging in the device again
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
IMPORTANT: disable_Dm-Verity_ForceEncrypt by installing this zip. If you don't do this, you won't be able to enter TWRP again
Optionally install magisk, titanium backup, and other magisk mods
Reboot system and profit
Update: 2021-04-06
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. This should boot you to stock RECOVERY.
Wipe to factory reset. Confirm by typing "yes" (WARNING: this wipes your device)
Plug in your Huawei Honor Note 10 to your PC with ADB
Boot to DOWNLOAD mode by holding down the VOLUME DOWN button as soon as your Huawei Honor Note 10 reboots
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
Install any custom ROM you wish via selecting a system image (or zip file if you have EMUI 8)
Install magisk, titanium backup, and other magisk mods (note that you will NOT be able to boot to recovery after this; consider this you last chance to install any mods)
Reboot system and profit
Background and Explanation
When you first flash a ROM, even in EMUI 8, your Huawei Honor Note 10 encrypts /system to prevent third parties such as TWRP from mounting it. Hence, you may successfully boot to TWRP, but /system will be mounted as read-only. This is problematic, as it means you can't install any new ROMs (however, you can make a backup, which can be useful for backing up stock, encrypted /system partitions)
Because /system gets encrypted, it means you have to wipe /system completely. Doing a factory reset (low-level) does this, once you unlock your bootloader. However, if you were to let your Huawei Honor Note 10 boot, then the stock ROM would, by default, encrypt /system, forcing you to start this process all over again (as TWRP will, in most cases, not even boot with an encrypted /system). If your TWRP hangs on the TWRP logo, your /system partition is likely encrypted. You need to factory reset, install TWRP again, and then wipe /system, followed by installing the Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip script.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
I hope this guide helps other fellow Huawei Honor Note 10 owners. If you have any questions, please also make sure to include your EMUI version and steps taken so that I can best help you. I hope that I have saved some of you trouble when updating to EMUI 9 and also helped to explain why updating can become so tedious.
Thank you for the instructions! I've got some questions...
ForgottenSolstace said:
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
Click to expand...
Click to collapse
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
null00005 said:
Thank you for the instructions! I've got some questions...
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
Click to expand...
Click to collapse
Yep, so it sounds like you have an encrypted /data.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
(Note: this will erase everything on /data)
Then boot to TWRP again. Check the logs and try again.
ForgottenSolstace said:
Yep, so it sounds like you have an encrypted /system.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
Then boot to TWRP again. Check the logs and try again.
Click to expand...
Click to collapse
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
null00005 said:
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
Click to expand...
Click to collapse
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
ForgottenSolstace said:
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
Click to expand...
Click to collapse
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
null00005 said:
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
Click to expand...
Click to collapse
If you roll back to stock and unlock your bootloader again, then you don't need to do fastboot erase userdata because "factory reset low-level" will perform that once you unlock your bootloader again. So you should be able to flash TWRP, boot fine (only that one time), install whatever ROM you want, flash magisk, and boot (note: on EMUI9, you must reboot to recovery, as boot_ramdisk only exists in EMUI8).
In the past, I have ignored the message "failed to mount '/odm'" and still had success; just pay attention to the status code at the end when you install /system. Don't bother wiping odm, as we really care about mounting /system. Perform a factory reset just to be safe, and feel free to wipe /data, but it won't matter if you already performed a factory-reset (low-level) from unlocking your bootloader again.
Try installing your ROM of choice from TWRP despite this error, flashing magisk, and confirm if that works.
ForgottenSolstace said:
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
Click to expand...
Click to collapse
Hi, how about root with magisk in this rom?!
TheFastGT said:
Hi, how about root with magisk in this rom?!
Click to expand...
Click to collapse
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
jazzzy said:
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
Click to expand...
Click to collapse
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
TheFastGT said:
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
Click to expand...
Click to collapse
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
jazzzy said:
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
Click to expand...
Click to collapse
I've a Honor Note 10 and i haven't TWRP installed, i use stock recovery and Openkirin rom...
How can I unlock my bootloader?
Darj said:
How can I unlock my bootloader?
Click to expand...
Click to collapse
HCU client
TheFastGT said:
HCU client
Click to expand...
Click to collapse
Thanks.. this is the only device I have so I wanted to ask what would happen if I mess it up
TheFastGT said:
HCU client
Click to expand...
Click to collapse
And once I unlock the bootloader using HCU client, do I have to follow the steps above or can I just install a custom recover how you'd do on any phone?
@Darj , did you manage to sort out rooting your Huawei Honor Note 10? I've updated the installation steps to reflect the shortened steps I last took to get Magisk running (downgraded to EMUI8 on my Huawei Honor Note 10 to try to preserve TWRP).
Hopefully, we'll see more ROMS from the OpenKirin project, as the latest security patch is almost a year old on EMUI8.
@ForgottenSolstace not yet. I want to make sure I have all the informations I need before spending money to unlock the bootloader
@Darj , it only costs 15USD to unlock your Huawei Honor Note 10. Why not go ahead and try?
I assure you that the effort is much worth it; Stock ROM is bloated with all kinds of spyware from the Chinese government. When you install AOSP, you can actually secure your phone following the updated instructions which encrypts /data.
Let me know if you have any questions. Happy to help
Hi ...got problem using twrp?