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 ...
Related
Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you
Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.
whenever i go into recovery mode i get an error on the bottom of the screem
BUILD : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No Space left on device)
i cant nand backup or anything
rickyiswhite said:
whenever i go into recovery mode i get an error on the bottom of the screem
BUILD : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No Space left on device)
i cant nand backup or anything
Click to expand...
Click to collapse
There are two possibilities:
1) The log is occupiing really the whole space on cache. In that case try to remove the log file from cache directory
2) Did you mess up with custom partion tables? To me this happened some time ago when I forgot to flash fr_boot_xxx.zip onto a boot.img while having installed custom partitions. In that case you have to clean everything. Eventually you need also to flash recovery again. If you have a recent backup, you can try to do a
fastboot erase system -w
then boot into recovery and see, if everything works for you again. If not you need to flash a new recovery:
fastboot flash recovery recovery.img
After that everything should work again, i.e. you can install your backup or you can install a new ROM.
AndDiSa said:
There are two possibilities:
1) The log is occupiing really the whole space on cache. In that case try to remove the log file from cache directory
2) Did you mess up with custom partion tables? To me this happened some time ago when I forgot to flash fr_boot_xxx.zip onto a boot.img while having installed custom partitions. In that case you have to clean everything. Eventually you need also to flash recovery again. If you have a recent backup, you can try to do a
fastboot erase system -w
then boot into recovery and see, if everything works for you again. If not you need to flash a new recovery:
fastboot flash recovery recovery.img
After that everything should work again, i.e. you can install your backup or you can install a new ROM.
Click to expand...
Click to collapse
hmm ok ill try that... thanks... and sometimes it says cant open cache or something
So i was trying to install Liquid Remix rom on my op3t i wiped everything as the manual and have flashed opengapps magisk and the rom but when rebooted into the rom it asked me for my pin ive entered my pin but it said ur pin is correct but ur data has been corrupt u have to factory reset and automatically boots into twrp and when i try to boot into the system the process over and over again and i factory reset it nothing again says data is corrupt and ive flashed my recovery and try to boot into system nothing boots into fastboot iveand being a dummy i am i delted the system everything heard that u can fix it with adb sideloader but my question is can i flash a custom rom notthe stock rom please help me
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
przemcio510 said:
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
Click to expand...
Click to collapse
i already did that on accidentand deleted everything even the backups
Something similar happen to me. I was in twrp and was performing a full wipe(not factory reset), I installed RR, kernel, and then when I was installing gapps, the phone rebooted, and when I tried anything, it said e: legacy property not found( or something similar) and would not boot to system, would not flash anything, wouldn't boot to bootloader, but I was able to transfer files and use adb so I plugged into the computer and used adb reboot fastboot and booted to bootlaoder, now everything works
tergeltengo said:
i already did that on accidentand deleted everything even the backups
Click to expand...
Click to collapse
Backups are supposed to be stored outside the device you make a backup of, keep that in mind for future
Immortalis said:
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
Click to expand...
Click to collapse
Thank You, saved my phone.
I have rooted my m10g using magics via twrp and also applied the "no-dm-verify" patch but I didn't notice about the "forced data encryption" patcher here so that's reason why I didn't patch it at this point! anyway the data section was mounting without any problems but after I reboot recovery I was getting error In mounting the data section I just ignore it and I was able to boot into system normally but after some days exactly after "insufficient space" I just rebooted for some reasons and after that the device won't boot anymore / stucked at bootloop...!
I was able to see the home screen/touch wiz about 4 seconds and after that it's reboots again and again (In this point I tried to delete unwanted files quickly but there's no luck).
Things I have tried:
- flashed an recovery.img extracted from combination firmware and tried the "lacking storage booting" an option from stock recovery menu the device started in safe mode (It's says something like this: please bacup your stuff and then perform factory reset) but it's still won't boot (bootloop).
- twrp decrypt (I set no password there but I just tried In hope of chance) btw twrp never asked before to decrypt my data or to enter any password.
- I did twrp backup to my ext-sd and decompiled the boot.img to see what can I do (but after magics's patch I can do nothing).
- Pulled full userdata (mmcblk0p26) section also the emmc (mmcblk0) and tried to mount via linux reader windows tool / opening via 7zip but still can't access the userdata section. also tried to open the dumped userdata via hex editor but still can't see anything(looks like encrypted).
Things I want to try next:
- Format the data section after that try to restore the dumped userdata section via dd command.
- Enable usb debug at boot time and try to adb shell stop then pull all important data from the device.
- Inject custom script in stock_recovery.img to copy all internal files to the externel-sdcard (or even delete some huge files that I'm pretty sure of their path).
Notes / just to be clear:
* Flashing the stock kernel will encrypt the userdata section and the bootloop will stop but I'll lose all my data (I know that so I was just switching from the stock recovery to twrp).
* I could just perform a format data from the recovery menu / twrp or just flash the stock firmware to fix the booting problem but first I need to all my files get back.
Looking for any help in things that I want to try next.
Finally after a lot of tries I have solved my problem...!
How?
Short answer: ClassyKitchen
Long answer:
I just started creating my first rom In ClassyKitchen and I just enabled adb and removed dm-vertify via the kitchen and after the rom has prepared I just flashed through TWRP after I reboot the phone wasn't able to boot (stucked at first samsung logo) switched the device to download mode and I flashed system only using odin... after that phone started with setup wizard! and it's was still in safe mode (the backup message was still showing also) anyway I completed the setup wizard then check the home screen and apks I have installed wasn't there...!!! I opened "My Files" and finally I was able to see my files again!
I just copied all my internal sdcard to my external sdcard...!
After the copy ends I tried to exit safe mode to get my installed apks/contacts again so I just rebooted the phone to exit from the safe mode! But after the reboot "custom binary flashed bla bla".
I flashed stock "boot.img" and "recovery.img" using odin But as I said in the first post data encryption was there...!!!
Anyway I flashed full stock firmware after that I unlocked my OEM and flashed TWRP again and I restored the emmc dump using dd after restore completed rebooted the phone and it's back to it's state...!
this time I just flashed the patched boot.img (ClassyKitchen) and after the reboot phone started normally with setup wizard as said above! Connected to wifi unlocked my OEM and I was trying to get out of safe mode I rebooted and rebooted and power off but I wasn't able to disable the safe mode...!!!
I tried to root using magics but it's failed (the boot was patched by bla unsupported something like that) also the data section was still unmount able! In the TWRP
Anyway I just stopped at this point! Because I have reach my point (Getting back my sdcard data).
Notes!:
* All thanks goes to the author of ClassyKitchen.
* TWRP I was using found here.
* Odin I have used found here.
* I was using the same firmware version (PDA) installed in my phone.
* I have unlocked my OEM using this method the first time I have used it's taked from me only 3 days!.
* The idea of taking full encrypted emmc backup was by this post (I was getting some error messages so I just used "dd if=/dev/block/mmcblk0 of=/your_external-sd/mmcblk0.img" In case of "no space left error" format your externel-sdcard to ext4 and try again).
Sorry for my bad English x).
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash​
cant solve this please help
tried edl recovery flashed well but didnt solve problem
i have unlocked the bootloader and flashed many raw firmware didnt solved problem
flashed twrp sucessfully but cant mount storage intenal storage 0mb and cant swipe anything
get this message everytime in recovery
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash​
please help
I have no idea it helps, I had my phone crash on me and me trying my old-and-tried flashing etc. I did not have such BCB message, but it sounds like there is an issue with the partitions or partitioning.
There are nice YouTube videos at least that show how to flash the stock ROM (not giving link here for advertising etc).
it boils down to (FIRST get your data off the phone as you are going to lose this)
- TWRP being bootable
- in TWRP: factory reset, wipe data
- flash stock ROM twice: to partition A and after reboot to TWRP, to partition B. I do not know why this needs to be done, love to learn it by myself.
- flash without wiping a custom recovery if wanted.
- restore your data