Database Develop

Problems with mounting cache

my phone is crazy. can't download anything using play store.
not enough memory. but at close look the phone will not mount cache partitaion.
anybody pls help. all roms the same

Anybody?
I get error code 498 in lgp 990 custom rom.
but in miui rom the android core process is forced closed
Error code 498 is related to cache partation.
but in miui is android core process that is forced closed all the time
There is no cache mounted on the phone.
And it doesnt metter which rom ja choose. it's all the same. some rom says it isn't enough memory.
Help please. i think it's got to do with cwm. it's just wrong. it's v 6.0.1.5 i think. there was never problem with 5.0.0.7
Formating cache will not create cache partation in cwm. please resolve problem

Try command:
mke2fs /dev/mmcblk0p2
from terminal emulator or adb shell and reboot your phone.
Check if your cache is mounted with command:
mount | grep cache
Worked for me.
Sent from my LG-P990 using xda app-developers app

asmerito said:
Try command:
mke2fs /dev/mmcblk0p2
from terminal emulator or adb shell and reboot your phone.
Check if your cache is mounted with command:
mount | grep cache
Worked for me.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
No such file and not working. i cecked cahce with link2sd and it's unreadeble as N/A
I'm not sure where is the problem but i think it got to do with cwm. that program has f my phone.
Even before some roms wouldnt work properly exept muiu or wuiu i dont know what rom is called.
But even now that rom wont work as before after installing djmango i am terible at spelling and knowing names.
but do get good analasys anyway.
i did install long ago new ics upgrade which was no difference in rom and maybe there was the problem (bootloader
) this is just a guess but my money is on cwm
problem solved. Cmw 5.0.2.0 working by downgrade

[Q] can't mount /data

form last some days when I am trying to create backup of my phone (Micromax Canvas A1)
i am getting a same error in all the recoveries
CAN'T MOUNT /DATA
any one pls tell me y is it happening and the solution of this problem....
:good:

USE TWRP AND TRY FORMATTING WITH MAKE EXT4fs AND DON'T USE RM RF AND IF STILL DOESN'T WORK TRY REBOOTING SYSTEM AND TRY TO FORMAT AGAIN STILL GOT ERRORS TRY FLASHING A NEW ROM

tsrajput said:
form last some days when I am trying to create backup of my phone (Micromax Canvas A1)
i am getting a same error in all the recoveries
CAN'T MOUNT /DATA
any one pls tell me y is it happening and the solution of this problem....
:good:
Click to expand...
Click to collapse
flash the stock userdata.img by:
fastboot flash userdata userdata.img
the image file will br ir SP tools flashable rom/firmware.

tsrajput said:
form last some days when I am trying to create backup of my phone (Micromax Canvas A1)
i am getting a same error in all the recoveries
CAN'T MOUNT /DATA
any one pls tell me y is it happening and the solution of this problem....
:good:
Click to expand...
Click to collapse
If you are on 5.1+ then use twrp 2.8.6.0... Thats the latest official build for sprout

Yes, the latest recovery solves the issue of many zips which were not flashing......

Mİ3 Brick or Dead Im very sadly

Guys. I installed mm miui beta. after I want go back miui kk. and I flashed stock partition with cwm. now I cant flash any zip with twrp, cwm or orj miui recovery. I cant flash fastboot rom. I can only flash recovery with fast boot. in twrp menu internal stroge looking 0 mb. SDcard working but recovery cant flash any zip bec. internal stroge looking 0 mb. And I cant flash rom with adb.
mi flash error: 0x80004005:FAILED (remote: partition table doesnt exist ) Im very sad guys. I love my phone pls help me. with out battery cant give me 9008 port. I cant try testpoints.
Sorry for my bad lang. Who can help me?
in my partition table cant see rm 25 and 26
my partition table = i.imgur.com/XxyPuVA.png
I solved my problem with qpst guys. dont need thread thanks. firstly ı removed partition table with adb. after my pc connected with port10. with qpts ı write blocks. and install with mi flash my offical rom

en.miui.com/thread-138246-1-1
use http and html in end and . wherever necessary cant post link

There is a solution to unbrick using miflash here http://en.miui.com/thread-59891-1-1.html

Flash partition first then try I'm even faced the problem
Flash partition first then try I'm even faced the problem after upgrading to mm
Try to flash partition ill post u the link in next reply
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
This guide is for you
What you will need:*
1. USB cable is of decent quality (not the one on which the connection is lost at the slightest movement)*
2. Windows
3. The device defined somehow Device Manager*
4. The latest version of*MiFlash*
5. MIUI firmware developer for fastboot*here
6. Adb and fastboot installer*here
Connect your phone in fastboot mode*
Enter this
Fastboot flash partition gpt_both0.bin
This file is in fastboot rom.*
This will restore stock partitions, then flash all the kitkat rom.
"Fastboot flash partition gpt_both0.bin"

I Brick my device, please help

I brick my device restoring modem.
Please can some owner of MiMix 256Gb make a copy of a partition /dev/block/sde3 and and send to my email ?
Commands:
adb shell
su
dd if=/dev/block/sde3 of=/sdcard/tz.bin
my email [email protected]
Please help!
Solved Thanks! Take the file from fastboot rom

TuSKan said:
I brick my device restoring modem.
Please can some owner of MiMix 256Gb make a copy of a partition /dev/block/sde3 and and send to my email ?
Commands:
adb shell
su
dd if=/dev/block/sde3 of=/sdcard/tz.bin
my email [email protected]
Please help!
Solved Thanks! Take the file from fastboot rom
Click to expand...
Click to collapse
How did you brick it?

SantinoInc said:
How did you brick it?
Click to expand...
Click to collapse
Flashing the modem in the wrong place:
dd if=/sdcard/modemst2 of=/dev/block/sde3 instead of
dd if=/sdcard/modemst2 of=/dev/block/sdf3

Dear users, please be carefull with this kind of commands...
To the author thread: Use xiaomiflash if you can enter to fastboot mode and flash latest DEVELOPER CHINA to revive your MIX.

Failed to mount /persist (invalid argoument)

Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!

Youshouldsmile said:
Hey guys, i have a problem with the K20 Pro, i tried a gps module from magisk but it didn't work properly and now when i try to format data, factory reset this error appears: "Failed to mount /persist" (Invalid argoument). How can i fix this? I Was on EU Android Q Rom. I Can still boot up but things as Pop up camera are buggy
I think if someone with TWRP do a Backup of persist and upload somewhere for me i can back it up from twrp!
Click to expand...
Click to collapse
You can extract the persist.img file from the MIUI Q beta fastboot ROM

i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !

sar78mad said:
i have the same problem
tried doing fastboot erase persist , but no luck ( write protected)
using twrp or fox recovery both giving me the same error ( failed to mount persist, invalid argiument..
any help ?
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
also the problem happened after a module install using magisk.. i really dont know how persist partition got damaged when it is write protected !
Click to expand...
Click to collapse
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.

i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..

sar78mad said:
i've managed to fix the problem with persist partition
i used persist.img form stock 10.3.3 global fastboot rom , and copied it to sdcard. then did the adb shell command with (dd if=/sdcard/perist.img of=/dev/block/"add here persist partition dir")
worked and my device now is working like a charm..
Click to expand...
Click to collapse
Bro could please tell us step by step ? i am getting mad. please

Eng.Raman said:
Fix: Just extract persist.img from your fastboot rom then use LR.Team TWRP to flash it in the persist partition after that when you boot to system open the camera app several times until a message apperars to calibrate, tick on it and you will see a popup message tell calibration successful.
Done.
Click to expand...
Click to collapse
perfect
I read my computer partitions. After finding the number of the block that corresponds to my team, copy the persist of the rom stock to my internal memory in twrp and then flash with your command and add my block.
in my case note 10 pro (sweet)
dd if=/sdcard/persist.img of=/dev/block/sdf7
VERY CAREFUL NOT TO USE THIS COMMAND ON ANOTHER computer. each person must read the exact block that corresponds to your mobile reference.

I guess your problem is more of hardware issue ,but have to test to know.
I come to this conclusion because magisk does not modify partitions nor system files , I would start with a clean fastboot flash of the phone (be careful of the lock checkbox).
Then judge from there , if phone still presents anomalies then my first assumption is true.