Hello everyone heres a guide on how i formated my le pro 3 720 64gb from ext4. please know that this will delete all of your data will be delete i strongly recommand doing a twrp or tatanium backup before hand! allso if this somehow ****s up i will not be hold responsible. i am simply showing you all how i did this to get my result. now with all the formalitys in place lets talk about what exactly the steps are after you backed up everything you want to keep download your feverite rom. the one i am ussing is turbos aokp destroyer ver2, download it unto your pc, allso make sure you have twro custom recovery that support the f2fs.
here is the one i ussed. https://drive.google.com/file/d/0B9ZMWt4u_wSDVkp3UlMxS1liMUE/view
after you have made sure your twrp support it and you backed up everything you need. boot into twrp, wipe/advanced wipe/check data/repair or change file system/chenge file system/ f2fs do the same for data and for cache. then connect you phone via the usb cable to a pc with minimal adb put the rom you decided to install on your le pro 3 into the minimal adb folder and call it something easy like Kitty. i do this all the time xD
then open a cammend windows as admin and type the fallowing code.
adb push push kitty.zip /sdcard
this will start your rom being moved from the pc unto your sdcard on your phone. and i allso belive its the safest way to do it dont qote me on that tho.
then you just install your kitty rom and you should be good to go. NOTE in my case with the destroyer 2 aokp from my good freind turbo i dont think the /system supports f2fs as it reformats it into the ext4 on installation, but data and cache will reamain f2fs at all times. and it does seem quite abit faster regardless. thanks everyone for reading and im sorry if this is done in a extreme noob fashion i hope you all will be able to understand whats going on and all. peace out and be sure to let me know how it turns out for you
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
venezolano69 said:
Do you think it is good than format everything to install a Rom with the twrp in a normal way connecting a USB otg?
Click to expand...
Click to collapse
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
DrTorretz1 said:
It might work. I've never used a otg in TWRP before but if it works I can't see why not.
Click to expand...
Click to collapse
OK thanx for the guide
venezolano69 said:
OK thanx for the guide
Click to expand...
Click to collapse
Your welcome hope it helps!
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
FYI, at the very least you can format your cache partition to F2FS without losing any data.
slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
villarleg said:
Thanks for the tutorial! one tip, system partition its not recommended to format to f2fs, because system its a "readonly" partition and ext4 is fastest than f2fs in read, you only need to change /data and /cache to f2fs to improve the performance of the device!
Click to expand...
Click to collapse
Wow thanks village! I'm happy you enjoyed the guide also thanks for letting me know about the system I will put it up there!
venezolano69 said:
I tried to format cache it didn't work I'm on 23s destroyer with the same twrp navigator v6
Click to expand...
Click to collapse
Does it come up with a error or something? I'm not sure mine did it fine
slgooding said:
FYI, at the very least you can format your cache partition to F2FS without losing any data.
Click to expand...
Click to collapse
Yeah I suppose so. It works really well regardless
DrTorretz1 said:
Does it come up with a error or something? I'm not sure mine did it fine
Click to expand...
Click to collapse
Something like "not possible to mount"
venezolano69 said:
Something like "not possible to mount"
Click to expand...
Click to collapse
That sounds really strange. I'm sorry I can't assist further. Data should be the most important one annyways
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Enamak said:
Whenever i try to format data or cache to F2FS i get Failed to mount errors to both cache and data. But i still could flash the rom, tho i was getting a lot of lag sometimes and i thought it could be because of that. I guess this shouldnt happen, any idea?
EDIT: Fixed by updating twrp to 3.1.0.0
---------- Post added at 09:03 PM ---------- Previous post was at 08:26 PM ----------
Now i have other problem, im stuck at recovery without rom on sdcard, and i cant seem to use adb, it says my device is unauthorized when i type adb devices
Click to expand...
Click to collapse
Do you have an otg?
venezolano69 said:
Do you have an otg?
Click to expand...
Click to collapse
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Enamak said:
I flashed the ROM thro sideload, all fixed now i also thought about otg but i didnt have one and didnt really want to get onde x)
Thanks anyway
Click to expand...
Click to collapse
Otg is very good stuff, when you wipe everything you put Rom insidie the otg and you can flash everything you want
I have another problem.. I formated /cache /data (no problems, errors). After that I flashed "TURBO2012's China / US EUI 23s V8" (no problems, errors).
But DiskInfo from the playstore is showing me ext4 in /cache and /data ?
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
cherryduck said:
Does this work with LineageOS 13? Did this and flashed the ROM but it's been stuck on the boot screen for a while.
Click to expand...
Click to collapse
Same here. I tried it a few days ago with the latest Lineage nightly and started formatting all partitions with F2FS with the same outcome: stuck on bootscreen.
Gradually I returned my partitions to ext4 and only after I returned everything to 'normal' I got past the boot screen. Not even "cache" worked with F2FS.
Related
Hi,
I tried to install CM10 on my Motorola Defy+ (MB526), which was successful to some extent.
When I tried to install the latest gapps through CWM, it froze at the starting applications part.
I force restarted it, seeing that there was no change for a while.
When I restarted the phone, it kept on rebooting, with limited functionality, so I downgraded to CM9.
An error message pops up which says with Encryption Unsuccessful. A reset button was available, but didn't help.
I then re-upgraded to CM10, but the phone has limited functionality.
After researching the problem, I realised that the /data partition is not mounted as it is probably corrupted.
Is there any fix to this problem? Will flashing a sbf recreate the /data partition?
Please advise as the phone is basically useless without /data (no apps and constant reboots)
Thanks,
neiljain
neiljain said:
Hi,
I tried to install CM10 on my Motorola Defy+ (MB526), which was successful to some extent.
When I tried to install the latest gapps through CWM, it froze at the starting applications part.
I force restarted it, seeing that there was no change for a while.
When I restarted the phone, it kept on rebooting, with limited functionality, so I downgraded to CM9.
An error message pops up which says with Encryption Unsuccessful. A reset button was available, but didn't help.
I then re-upgraded to CM10, but the phone has limited functionality.
After researching the problem, I realised that the /data partition is not mounted as it is probably corrupted.
Is there any fix to this problem? Will flashing a sbf recreate the /data partition?
Please advise as the phone is basically useless without /data (no apps and constant reboots)
Thanks,
neiljain
Click to expand...
Click to collapse
Hi Buddy,
I went through the same process last evening, earlier i was on 2nd boot then it was very slow hence I decided to move to CM9 for better UI and good battery life. but while doing so my phone also got encrypted.
I did following and installed CM9 yestrday night.
Removed SD card, read it through computer (CArd reader) and put CM9 in one folder along with GAPPS.
Charged my battery till green light pops up.
Entered the SD card again and then started the phone in Custome Recovery.
Full data Wipe
Dalvik Cache wipe
Install CM9 and Gapps.
again clear Cache and dalvik and reboot.
It should work, let me know if it doesnt work post that as well.
Regards,
Amit Sharma
Plz hit thanks button if this work
[email protected] said:
Removed SD card, read it through computer (CArd reader) and put CM9 in one folder along with GAPPS.
Charged my battery till green light pops up.
Entered the SD card again and then started the phone in Custome Recovery.
Full data Wipe
Dalvik Cache wipe
Install CM9 and Gapps.
again clear Cache and dalvik and reboot.
Click to expand...
Click to collapse
Hi,
If the /data partition is corrupted (which I believe it is), will this still work?
Also, did you get any "Can't mount /cache/recovery/command" errors in CWM at anytime.
Thanks,
neiljain
[email protected] said:
Hi Buddy,
I went through the same process last evening, earlier i was on 2nd boot then it was very slow hence I decided to move to CM9 for better UI and good battery life. but while doing so my phone also got encrypted.
I did following and installed CM9 yestrday night.
Removed SD card, read it through computer (CArd reader) and put CM9 in one folder along with GAPPS.
Charged my battery till green light pops up.
Entered the SD card again and then started the phone in Custome Recovery.
Full data Wipe
Dalvik Cache wipe
Install CM9 and Gapps.
again clear Cache and dalvik and reboot.
It should work, let me know if it doesnt work post that as well.
Regards,
Amit Sharma
Plz hit thanks button if this work
Click to expand...
Click to collapse
Hi,
I tried the above procedure, yet there was no success.
Please advise any alternative methods.
Thanks for your quick reply though.
Regards,
neiljain
neiljain said:
Hi,
I tried the above procedure, yet there was no success.
Please advise any alternative methods.
Thanks for your quick reply though.
Regards,
neiljain
Click to expand...
Click to collapse
remove SD card, log into Stable recovery mode. wipe data / factory reset and try rebooting.
if problem still persist, read your phone through RSD and flash CM7.2 file. let me know if you need link for the same.
It will work.
Regards,
Amit Sharma
This will format your data partition, be warned!
neiljain said:
Hi,
I tried to install CM10 on my Motorola Defy+ (MB526), which was successful to some extent.
When I tried to install the latest gapps through CWM, it froze at the starting applications part.
I force restarted it, seeing that there was no change for a while.
When I restarted the phone, it kept on rebooting, with limited functionality, so I downgraded to CM9.
An error message pops up which says with Encryption Unsuccessful. A reset button was available, but didn't help.
I then re-upgraded to CM10, but the phone has limited functionality.
After researching the problem, I realised that the /data partition is not mounted as it is probably corrupted.
Is there any fix to this problem? Will flashing a sbf recreate the /data partition?
Please advise as the phone is basically useless without /data (no apps and constant reboots)
Thanks,
neiljain
Click to expand...
Click to collapse
Boot to recovery and turn on adb (in Advanced). Open a shell on the phone through adb from a PC. Try to find out if data is mounted, and if so what filesystem type it uses:
Code:
$ adb shell
~ # mount|grep /data
/dev/block/mmcblk1p25 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,nobh,data=writeback 0 0
If /data is corrupted it will not be mounted. On my phone /data and /cache are formatted ext4, which is only supported in the latest CM10. If yours happens to be formatted ext4 as well and you want to go back to CM9 you'll have to reformat both to ext3. If /data is corrupted you can also reformat the filesystem as you don't seem to have data worth keeping on it anyway (seeing that you talk about doing a full SBF flash to 'recreate the /data partition'). This can be done manually or - if you have not nuked the scripts installed by CM10 - using one of the scripts made for that purpose. Those scripts live in /system/bootmenu/script:
Code:
~ # ls /system/bootmenu/script/|grep format
format_ext3.sh
format_ext4.sh
If you have access to these scripts you can just run format_ext3.sh to reformat /cache and /data in ext3:
THIS WILL FORMAT YOUR DATA PARTITION - ALL DATA WILL BE LOST!
Code:
~ # /system/bootmenu/script/format_ext3.sh
If you don't have access to them you can achieve the same effect using the following commands:
THIS WILL FORMAT YOUR DATA PARTITION - ALL DATA WILL BE LOST!
Code:
PART_CACHE=/dev/block/mmcblk1p24
PART_DATA=/dev/block/mmcblk1p25
umount /data
umount /cache
# if you want to check the filesystems you can run these commands...
#/system/bin/e2fsck -y $PART_DATA
#/system/bin/e2fsck -y $PART_CACHE
# to format the filesystems to ext3 use these commands
/system/bin/mke2fs -j $PART_DATA
/system/bin/mke2fs -j $PART_CACHE
mount -t ext3 -o nosuid,nodev,noatime,nodiratime,barrier=1 $PART_CACHE /cache
Once you have formatted /data and /cache you should be able to install CM9 - no need for any SBF flashing unless your phone is really messed up (as in 'deleted the stock kernel' or something like that).
THIS WILL FORMAT YOUR DATA PARTITION - ALL DATA WILL BE LOST! Or did I say that already?
No matter. THIS WILL FORMAT YOUR DATA PARTITION - ALL DATA WILL BE LOST! Just to be clear...
YetAnotherForumUser said:
Boot to recovery and turn on adb (in Advanced). Open a shell on the phone through adb from a PC.
Click to expand...
Click to collapse
Hi,
Highly appreciate your efforts.
I am new to Android, so could you please explain what "adb" is.
Thanks,
neiljain
SBF flash and data wipe in stock recovery should work too...
The other method is a bit more nondestructive, but probably harder for you
Sent from my MB526 using xda premium
thekguy said:
SBF flash and data wipe in stock recovery should work too...
Click to expand...
Click to collapse
Hi,
Could you please advise an SBF suitable for this.
I have a Defy+ that is locked to Telstra (Australia).
Thanks,
neiljain
Hi Everyone,
I will be taking the following steps to fix my Defy+.
I would like to reinstall CM9 (ICS) by quarx2k
Please advise if anything needs to be changed.
CWM
/data is corrupted, so no point in trying to wipe data and cache.
SBF
Flash DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf
Rooting
Flash firmware.sbf
2ndinit
Install SndInitDefy_2.3.apk
CWM
Wipe data and cache and Dalvik cache in recovery.
Install from zip CM9-NIGHTLY-120716-Defy+.zip
Install from zip gapps-ics-20120317-signed.zip
Install from zip Baseband_change(EP93_U_00.59.01).zip
Install from zip ICS_Defy_softunlock_v1.3(EPU_U_00.59.01).zip
Wipe cache and Dalvik cache
Reboot.
Thanks,
neiljain
Hi,
I tried flashing DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.
The flash was successful, but the phone looping the boot animations, not actually loading Android.
I have also lost access to CWM and recovery.
Please help.
Thanks,
neiljain
[email protected] said:
remove SD card, log into Stable recovery mode. wipe data / factory reset and try rebooting.
if problem still persist, read your phone through RSD and flash CM7.2 file. let me know if you need link for the same.
It will work.
Regards,
Amit Sharma
Click to expand...
Click to collapse
Hi Amit,
Could you please send me the link to the CM7.2 SBF.
Highly appreciate your efforts.
Thanks,
neiljain
neiljain said:
Hi Amit,
Could you please send me the link to the CM7.2 SBF.
Highly appreciate your efforts.
Thanks,
neiljain
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1820282 its working, step by step guide, just flash the first SBF file through RSD lite and it should start. charge your battery first please.
All the best.
neiljain said:
Hi,
Could you please advise an SBF suitable for this.
I have a Defy+ that is locked to Telstra (Australia).
Thanks,
neiljain
Click to expand...
Click to collapse
adb is the Android Debug Bridge, a program running on both the phone as well as your PC which makes it possible to access your phone (through either a command line shell or some GUI-thing layered on top of it).
Are you also new to Linux and/or computers in general? In that case you're probably better off flashing the phone as detailed, even though that takes way more time and does involve more risks. If you feel comfortable running commands from a command line I'd advice you to install the ADK (Android Development Kit) on your PC, get adb working and run the commands as I explained. That way you regain access to your phone without all the hassle and risks involved in flashing all the way from SBF. Both methods work, so the end result should be the same.
I'm intentionally not going into excruciating detail on the task of installing and running adb as I don't think you should use your phone as a guinea pig to start experimenting with adb - for that use the emulator which comes with the ADK.
Success
Hi Everyone,
Thanks for your very helpful suggestions.
I was able to recover my phone after flashing the SBFs
Just to be on the safe side, I will stick with CM9.
I will also post the instructions on XDA for other people who have the same problem.
Once again, thanks everyone,
neiljain
neiljain said:
Hi Everyone,
Thanks for your very helpful suggestions.
I was able to recover my phone after flashing the SBFs
Just to be on the safe side, I will stick with CM9.
I will also post the instructions on XDA for other people who have the same problem.
Once again, thanks everyone,
neiljain
Click to expand...
Click to collapse
Thanks Buddy, I too stick to CM9, which is giving best battery 2 days and awesome UI. will move to CM 10 once we have stable version.
Njoy your Defy.
how were u able to flash any file... neither the bootmenu nor the recovery is working... please revert back.
Im using a levovo a6000 android phone after rooting my phone i tried to install a custom rom
then when i checked my internal memory it was showing a 0mb of internal memory
the errors are as follows
1. E : unable to mount /data/media/TWRP/ .twrps when trying to read setting file.
2. E: Unable to mount '/data'
3. E: unable to mount '/storage'
Even on wiping dalvik cache and cache
i have rooted my phone using amd command prompt help me ee
nikhil7870 said:
Im using a levovo a6000 android phone after latest offical android update given by lenovo came my phone booted ok
then when i checked my internal memory it was showing a 0mb of internal memory
the errors are as follows
1. E : unable to mount /data/media/TWRP/ .twrps when trying to read setting file.
2. E: Unable to mount '/data'
3. E: unable to mount '/storage'
Even on wiping dalvik cache and cache
i have rooted my phone using amd command prompt help me ee
Click to expand...
Click to collapse
How did you managed to install the ota update on rooted device....!??
oops sorry its my friend mistake
sasukay said:
How did you managed to install the ota update on rooted device....!??
Click to expand...
Click to collapse
i had flashed a custom rom through TWRP please help me to figure it out
nikhil7870 said:
i had flashed a custom rom through TWRP please help me to figure it out
Click to expand...
Click to collapse
Boot into twrp and wipe cache, dalvik, data and system. Then flash the custom rom
sasukay said:
Boot into twrp and wipe cache, dalvik, data and system. Then flash the custom rom
Click to expand...
Click to collapse
while wiping data, cache , dalvik cache ,system, cache , data
its give a error wipe complete failed
and another error is
E: UNABLE TO MOUNT '/DATA'
E: UNABLE TO MOUNT STORAGE
Can xda developer fix my problem i think that xda is best and i always follow them but now i cannot get any help from you please help me
nikhil7870 said:
Can xda developer fix my problem i think that xda is best and i always follow them but now i cannot get any help from you please help me
Click to expand...
Click to collapse
Flash cwm any try wiping and then flash new rom from
http://forum.xda-developers.com/showpost.php?p=66472910&postcount=4
sasukay said:
Flash cwm any try wiping and then flash new rom from
http://forum.xda-developers.com/showpost.php?p=66472910&postcount=4
Click to expand...
Click to collapse
I think ur system partions is corupted
amithchinu said:
I think ur system partions is corupted
Click to expand...
Click to collapse
if it is corrupted then how to fix it and can u tell me how to do repartition
Go here http://forum.xda-developers.com/showthread.php?t=2683787 u will get solution
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
If it does not work goto service center
amithchinu said:
Go here http://forum.xda-developers.com/showthread.php?t=2683787 u will get solution
If it does not work goto service center
Click to expand...
Click to collapse
You might not know this, but every device has its own different system partitions. The thread you were referring to is for Asus Transformer Pad. Following that might make the problem worse.
But this is ASus phone it works on lenovo a6000
sasukay said:
You might not know this, but every device has its own different system partitions. The thread you were referring to is for Asus Transformer Pad. Following that might make the problem worse.
Click to expand...
Click to collapse
No bro it has sameproblem unable to mount data and cache there is solution to solve
amithchinu said:
No bro it has sameproblem unable to mount data and cache there is solution to solve
Click to expand...
Click to collapse
In that tutorial mmcblk0p8 is being formatted because that memory location has the /data directory on Asus Transformer. But, in our device the /data can be in any other partition, and doing that might brick the device permanently
Delete the recovery log from twrp folder and flash another twrp from flashtool or rash..what version are you using? If it is indeed a corrupted partition, you can reflash your phone using qfill
Try using the Fix Permissions in TWRP recovery...
It may help.
:fingers-crossed:
@nikhil7870 do you solve this problems?
nikhil7870 said:
Im using a levovo a6000 android phone after rooting my phone i tried to install a custom rom
then when i checked my internal memory it was showing a 0mb of internal memory
the errors are as follows
1. E : unable to mount /data/media/TWRP/ .twrps when trying to read setting file.
2. E: Unable to mount '/data'
3. E: unable to mount '/storage'
Even on wiping dalvik cache and cache
i have rooted my phone using amd command prompt help me ee
Click to expand...
Click to collapse
Best way is install the latest twrp I.e 3.0.2 and do the format everything instead of advanced wipe. Your problem will be solved. I too faced the same problem and I did what I have advised you. It worked.
cyberwarrior_a said:
Best way is install the latest twrp I.e 3.0.2 and do the format everything instead of advanced wipe. Your problem will be solved. I too faced the same problem and I did what I have advised you. It worked.
Click to expand...
Click to collapse
Is the problem resolved??
I have solution
Bro don't take so much tension , thats not hardware problem its only your Recovery's reading cache error . you can simply fix this by flashing old version of recovery and from that old recovery again wipe what you want to remove but man don't touch your mount section column , after wiping data and anything else simply flash new twrp.img then simply reboot recovery . wollllaaa you got your partion cache back now again you can simply flash you favorite roms. I hope you understand what you have to do now . But please follow these steps carefully :good: .
Remember don't flash KitKat recovery over lolipop recovery otherwise you got bootloop. Old recovery means suppose if you have now twrp v 3.1 just simply flash v2.8 then after wiping things you want , then simply flash twrp v 3.1 .
If you still have any doubt you can contact me via WhatsApp - +91 9205097520 (indian no. ) or simply reply me on xda or simply mail me at - [email protected] . And at last don't forget to tell me about your device problem .
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Gaby_64 said:
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Click to expand...
Click to collapse
Does TWRP print anything about "successfully decrypting /data with default password" in the console when it starts?
Go WIPE > ADVANCED WIPE > check the box next to "Data" > REPAIR OR CHANGE FILE SYSTEM. What does it say the file system of /data is?
Edit: Did you format /data before or after the issue happened? Never mind, you have to have formated /data afterwords if you were trying different ROMs.
ext4
i dont see the console
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
troy5890 said:
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
Click to expand...
Click to collapse
i tried as both f2fs(performance is worth it) and ext4
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Doc Ames said:
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Click to expand...
Click to collapse
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
troy5890 said:
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
Click to expand...
Click to collapse
May I ask, why are you using that version of TWRP?
Choose an username... said:
May I ask, why are you using that version of TWRP?
Click to expand...
Click to collapse
It's the only version that will boot up successfully when flashed through fastboot.
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
It's the only version that will boot up successfully when flashed through fastboot.
Click to expand...
Click to collapse
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Choose an username... said:
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Click to expand...
Click to collapse
I tried but it ended up not flashing successfully
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
I tried but it ended up not flashing successfully
Click to expand...
Click to collapse
all hail axon7tool then :v
Choose an username... said:
all hail axon7tool then :v
Click to expand...
Click to collapse
Looks like I'll give that a try, thank you
Sent from my ZTE A2017U using XDA-Developers Legacy app
This error comes when a file system is corrupted. i have faced this error and fixed it by using the following method.
in twrp
select wipe
select the partition that is corrupted
tap on repair file system
select ext4
all done
Hope it helps this method also works for yunique(jalebi) yuphoria(lettuce)
thanks
Nothing is working
I tried all things i can found out on xda, yureka fourm and YouTube. I watched all videos related to this issue but failed.
Phone can't write any thing. I tried anand bhatia hard brick software for format every thing but results r obvious.
Plzz help us......!!!
Rmoraj said:
I tried all things i can found out on xda, yureka fourm and YouTube. I watched all videos related to this issue but failed.
Phone can't write any thing. I tried anand bhatia hard brick software for format every thing but results r obvious.
Plzz help us......!!!
Click to expand...
Click to collapse
Tried in fastboot mode??
AmalRam said:
Tried in fastboot mode??
Click to expand...
Click to collapse
Yes i did but no use storage not mounted so unable to write ant think
You are seeing 'storage not mounted in twrp' know..?
Rmoraj said:
Yes i did but no use storage not mounted so unable to write ant think
Click to expand...
Click to collapse
You are seeing 'storage not mounted in twrp' know..? What's the error in the commad prompt using fastboot??
Does this method removes or wipes the current OS? I have Lineage OS installed and as on installing the OTA update through TWRP. there is this error which states unable to mount storage. I really don't wanna format wipe my data. Any help would be appreciated. thanks
Have anyone wipe everything before proceeding new installation.?
I had this Mount issue few minutes back and luckily i found this thread..And yeah repairing the mounts did worked out for me.
Thanks to Hitler_72485.
And yes! It will format everything.
I fell into this when i was doing normal wipe of partitions to install new rom, strangely it got struck while doing format..So i removed the battery and came up with those mounting issues. which ever partition i tried to wipe, mounting those failed afterwards. Then i tried this repairing thing with EXT4 FS. now everything is fine.
I did faced problems while repairing few but i did a normal repair swipe and then selected EXT4 swipe. (Don't know exactly what i did)
Hope No one will have this problem again. unless its a diff. case..!!
See ya.!!
Hello!
I tried to do a clean install of MIUI Global (10.3.11, which came with the phone). I didn't install any other ROM before in this device. Wiped eveything (data, system, dalvik etc.), then flashed the ROM and Magisk.
Now, when I connect the phone via USB I cannot access my files. It only shows "internal shared storage" on Windows, and it's all empty. When I try to transfer a file it shows nothing, the file just don't go. While in recovery I can access the storage and transfer files.
*I did activate USB depuration in developer mode.
*I did change de USB mode to "transfer files"
*I reinstalled the ROM several times.
Maybe it's something to do with the format type of the storage?
I'd try to do a ROM fastboot but I cannot find the fastboot version of MIUI Global for MI 9T.
Please, help
Did you format data? I think you forgot this part, format data then you can wipe it if you want.(formatting will delete everything from your internal storage ofc)
Ohk Let Me Help You .
Have You Advance Swipe the internal storage..then rebooted to twrp Before flashing the ROM !!
GedeonTaylor said:
Did you format data? I think you forgot this part, format data then you can wipe it if you want.(formatting will delete everything from your internal storage ofc)
Click to expand...
Click to collapse
Thanks for the reply! Yes, I did.
It seems like the "/storage/emulated/0/........." is broken. I cannot do nothing on this folder. I tried to create a file/folder in it with Solid Explorer and it says that the directory wasn't found.
Any idea?
Dev_Kahl said:
Ohk Let Me Help You .
Have You Advance Swipe the internal storage..then rebooted to twrp Before flashing the ROM !!
Click to expand...
Click to collapse
I already tried this. I'll try once more to format data, wipe, reboot to TWRP and flash the ROM.
velkz said:
I already tried this. I'll try once more to format data, wipe, reboot to TWRP and flash the ROM.
Click to expand...
Click to collapse
Ohk seems like a complicated one ...Can You Flash The FASTBOOT ROM if I give you the link of the correct ROM for you device !! ( this is all I can help )
Dev_Kahl said:
Ohk seems like a complicated one ...Can You Flash The FASTBOOT ROM if I give you the link of the correct ROM for you device !! ( this is all I can help )
Click to expand...
Click to collapse
Yes, please! I didn't find any fastboot ROM for mi 9t.
GedeonTaylor said:
Did you format data? I think you forgot this part, format data then you can wipe it if you want.(formatting will delete everything from your internal storage ofc)
Click to expand...
Click to collapse
Noticed that when I try to wipe data after formatting it an error appears on TWRP: "error opening '/data/media' (No such file or directory". Is it normal?
Seems like the ROM isn't properly creating the directory, that's why I can't access it.
velkz said:
Yes, please! I didn't find any fastboot ROM for mi 9t.
Click to expand...
Click to collapse
http://c.mi.com/oc/miuidownload/detail?guide=2
Here You Go
Dev_Kahl said:
http://c.mi.com/oc/miuidownload/detail?guide=2
Here You Go
Click to expand...
Click to collapse
Thank you! Gonna try it and update here
Edit: FOUND THE FIX! All I had to do was fix the SELinux contexts on TWRP. Now everything is normal. Thank you both for trying to help
velkz said:
Thank you! Gonna try it and update here
Edit: FOUND THE FIX! All I had to do was fix the SELinux contexts on TWRP. Now everything is normal. Thank you both for trying to help
Click to expand...
Click to collapse
Velkz
How do you did that?
mauriciocardoso said:
Velkz
How do you did that?
Click to expand...
Click to collapse
Boot into TWRP -> Advanced -> Fix Contexts