Hey guys,
I own a Redmi Note 4g. I updated my device and now when it boots up it shows the message 'unfortunately com.phone.android has stopped'. I installed TWRP recovery and wiped every partition but it is unable to mount /data partition , system partition and storage partition. What should I do to get my device working?
Please reply fast I'm in a hell lot of trouble..........
Related
HELLo guys i need a help ,this is my first time to do custom rom so im really noob about this
here the story on my redmi note 3 g ,i am using miui 5 and i hve just rooted it then go with twrp v2.8.7 the i wiped the cache ,system ,dalvic,data the start install this rom from suraj lad Resurrection remix then it done but when i am start to reboot it stuck in progress , then i change my twrp to 2.8.5 then start again ,it still failed stuck in the mi logo Here is the log when i am install flash:
detected filesystem ext4 for /dev/block/mmcb1k0p5
mount : failed to mount /dev/block/mmcb1k0p5 at /system : device or resource busy
symlink: some symlinks failed
"E : Error executing updater binary in zip ' /sdcard/RR V2 final for redmi_note3g_suraj.zip"
error flashing zip '/sdcard/rrv2 final for redmi_note3g_suraj.zip
updating partition details ..
... done
Try reboot to system, and flash again..
I'm having issues booting into my innjoo device.
It all started one morning, I woke up and saw some errors on my screen like (android.process has stopped working) I switched off the phone and turned it back on, but it got stuck on the innjoo logo and never booting up.
I decided to boot into recovery, where I encountered a list errors saying
(E: failed to mount /cache - invalid argument)
(E: cant mount /cache/recovery/log)
(E: cant open /cache/recovery/log)
And some other similar errors.
Choosing the wipe cache partition and the factory format option resulted in the same error. Which led me to believe my internal memory may be corrupted somehow (the data partition perhaps).
Is there a fix for this? And does anyone know of a way to correctly partition an Sdcard so it can be bootable and recognised by the device?
my Samsung galaxy s7 edge(SM-G935FD) is having this problem . in previous Android versions like Marshmallow it worked very well. But at the end of the Nougat updates, this problem started, suddenly the phone freeze and reboots itself, when it freezes there are multicoloured lines in the display(photo). and heats like hell.
and after the last oreo update killed my phone. its rebooting in a loop, sometimes phone works but for a short time.
I tried to factory data reset. there is this error message E: failed to find /misc partition cant reset or wipe cache.
tried to flash but flashing with ODIN, but it did not fix the issue. cant flash with Re-partition checked
tried TWRP recovery and couldn't wipe files or repair file system, Error message "Unable to Mount /data"
tried to change the file system couldn't do it gives this Error E: recv error on uevent
now after flashing with odin and it stuck on the boot logo
so this is my sad story pls help me guys :crying::crying::crying:
I decided to install a custom ROM in my device and what I did was wiped all partitions except 'Micro SD Card' and 'USB OTG', after that I formated data and it wiped all files in my device. Then I tried to flash the custom ROM but I was unable to flash it and an error message pops up - "failed to mount '/cache' (no such device)." I again tried wiping the partitions and all the partitions gets wiped easily exept the cache partition and the same error message pops up. Also whenever I try to restart into recovery, everytime it shows a message "No OS Installed! Are you sure you wish to reboot?"
So please help me out with this problem I can't flash anything at all
engtika said:
I decided to install a custom ROM in my device and what I did was wiped all partitions except 'Micro SD Card' and 'USB OTG', after that I formated data and it wiped all files in my device. Then I tried to flash the custom ROM but I was unable to flash it and an error message pops up - "failed to mount '/cache' (no such device)." I again tried wiping the partitions and all the partitions gets wiped easily exept the cache partition and the same error message pops up. Also whenever I try to restart into recovery, everytime it shows a message "No OS Installed! Are you sure you wish to reboot?"
So please help me out with this problem I can't flash anything at all
Click to expand...
Click to collapse
TWRP version? Have you tried to flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
to prevent the device from encrypting itself?
Wolfcity said:
TWRP version? Have you tried to flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
to prevent the device from encrypting itself?
Click to expand...
Click to collapse
I'm using TWRP v3.2.3-1 and I've flashed that zip but still the cache partition doesn't gets mount.
anyone have idea, im also experiencing the same issue. I was trying to root, and it wasnt taking it on my Moto G5 Plus, so i wiped everything except the same stuff, and then after that, any time it tries to mount the cache it fails. It wont mount at all, refuses to check the box. This is my log when i try to wipe the cache only now.
Failed to mount '/cache' (No such device)
Updating partition details...
Failed to mount '/cache' (No such device)
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/cache' (No such device)
E:Unable to wipe '/cache' -- unknown file system 'auto'
Unable to wipe /cache.
Updating partition details...
Failed to mount '/cache' (No such device)
Nevermind, I got it solved,, must have been caught trying to get to the OS, and looping cause there was not OS, and messing things up. Had to make sure i was holding the buttons to go to boot loader every time, but got it working.
Hello,
im new to this Forum. I try my best to give all the information i have.
What happened?
I tried to install the project /e/ os on my axon 7 mini. First I unlocked my phone with tuliptool in edl mode. I found the twrp recovery-image for my device in this guide (https://www.getdroidtips.com/root-twrp-zte-axon-7-mini-magisk/#Download-Files) flashed it with tuliptool to the recovery partition and it worked. But it broke my stock android rom. I only can boot intro twrp - i cant boot android (only shows zte android title screen). Then i installed the unofficial /e/ port for my device with twrp and it worked. Then i thought i could unroot my phone with tuliptool (i dont know why atm i thougt it will be a good idea) so i ran tupliptool lock unlock and my device was locked again. Now i only can access twrp so i undo the locking. After wiping the data partition with twrp, /e/ startet again. Then i thought that wiping the data partition would solve the issiue with not loading /e/ while locked, therefore i gave it an other try. Locking my phone again, wiping partition with twrp and... nothing. So i gave up and wanted to use my phone again so i unlocked it again.
Whats the problem?
Now I only can access twrp, but it wont show the menu. It just autostarts a script and there are no buttons. The script failes after ~10 seconds and the device crashes (error message below). It trys to boot up but fails, so it loads into recovery -> starts twrp -> runs this script -> crashes and so on. Now i cant do anything. It reboots all the time.
What can I do?
As said, twrp starts but with no menu. I have access to edl mode so i rewrote the recovery partition. This does not change anything. I can access my device with adb while it loads twrp. I have a time window about 10-15 seconds until it reboots. Fastboot does not work. (Not available or locked on Axon 7 mini?) If i try "adb reboot bootloader" my phone just reboots into android (well it did before flashing, now its stuck in the loop.) From searching this forum i think i should reformat the partitions, but i dont know how because i dont have access to the twrp menu. If you need more informations like a dump or something, tell me how to do it.
The Error:
As i dont know how i could dump it from my phone to my PC, i had to manual type the Error here...
$Begin
Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Unable to mount storage
Successfully decrypted with default password.
Updating partition details...
...done
Unable to mount storage
Unable to mount '/data' (Invalid argument)
Full SELinux support is present.
wipe_data_via_recovery
Unable to mount /data/media/TWRP/.twrps
Running Recovery Commands
Failed to mount '/data' (Invalid argument)
Formatting Cache using make_ext4fs...
Done processing script file
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
$end
This runs fast until "Done processing script file". There it waits for ~3 Seconds. Then the last two lines show up and it crashes immediately.
Ok i found a solution - it worked for me but i dont know why. Its not intuitive but hey, its a workaround.
The problem was twrp couldnt startup anymore because the data partition was currupted (not confirmed, but i guess it was currupted). If you follow any guide, they tell you to go to wipe data inside of twrp and wipe (and reformat) the partition. This wont work in this case, because the corrupted partition causes twrp to crash. Its the script in the post above.
To fix this i used adb while twrp was starting up
Code:
adb shell recovery --wipe_data
This alone wouldnt solve the issue, but it will buy some time. After twrp loads again, you will see the main menu of twrp for a couple of seconds. The time you have on the menu is very limited (5 seconds max) before the script that will crash twrp starts executing. In this time window i managed to set twrp to write mode and initiated the wipe of /data. If you get this far, both scrips (wipe data and open recovery script) will execute, the screen will switch between both of them very fast. After a few seconds it will crash again, but the wipe data script could reformat the data partition properly. After this twrp will work like normal.
I don't know if this problem is specific to my device or model. I dont know if this is recreatable. Im glad i fixed it after five long days, im not willing to sacrifice my device again. I dont know if this is a twrp bug or what happened exactly. If anyone had a clue or needs more informations i will provide them. At least I found a workaround.