Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?
Trying flashing marshmellow KDZ and it should reset everything
Let me know how things go
TTib said:
Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?
Click to expand...
Click to collapse
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.
KronicSkillz said:
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.
Click to expand...
Click to collapse
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!
TTib said:
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!
Click to expand...
Click to collapse
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.
KronicSkillz said:
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.
Click to expand...
Click to collapse
I flashed the kdz via LGUP and... now the phone won't boot to anything except TWRP. Have tried restoring two previous nandroid backups, installing CM12 and MM, all install without reporting errors. LGUP detects it as an unknown device, so can't flash kdz again. Might have bricked this one. :crying:
Phew. Okay, solved! I followed the following guide to flash an old version of the stock firmware: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html.
Then, I upgraded, rooted, flash TWRP and finally installed MM again and it seems to be back to normal ("Android is starting" screen as we speak. Fingers crossed!). Thanks to everyone who helped me out with this one!
Hi Community,
today i took my phone out of my desk and it was powered off and won't boot anymore. Just recovery and fastboot mode were working. I was on Lineage OS, TWRP with open bootloader.
Wipe storage in TWRP isn't working, also file manager shows no data on system oder sdcard. I tried also to repair file system in TWRP but file size of data or system seems to be 0MB. (used, free and size, all 0MB)
Wtf happend? Memory broken? Somebody heard something similar?
Kind regards
Manuel
Edit; Tried to flash fastboot rom with myflash but with no sucess. The flashing ends within 1 sec with error in log file: FAILED (remote: failed to write partition)
Hi
Did you try reflash twrp and wipe format data? You can try this modded TWRP
https://androidfilehost.com/?fid=673368273298976196
boarder87 said:
Hi Community,
today i took my phone out of my desk and it was powered off and won't boot anymore. Just recovery and fastboot mode were working. I was on Lineage OS, TWRP with open bootloader.
Wipe storage in TWRP isn't working, also file manager shows no data on system oder sdcard. I tried also to repair file system in TWRP but file size of data or system seems to be 0MB. (used, free and size, all 0MB)
Wtf happend? Memory broken? Somebody heard something similar?
Kind regards
Manuel
Edit; Tried to flash fastboot rom with myflash but with no sucess. The flashing ends within 1 sec with error in log file: FAILED (remote: failed to write partition)
Click to expand...
Click to collapse
Exactly this happened to me. Same scenario as you. Was on Los and only recovery and fastboot were working. Same error with miflash.
Worse though i tried to reflash recovery to the latest version. It failed and now phone doesn't even start. Just red blinking light.
I know this is an old post but did you ever fix it or the only solution is to change the motherboard?
Sent from my MI 9 using Tapatalk
Hi guys,i have a MI CC9e,and i have some problems with the TWRP recovery.
I have already unlocked the Bootloader and also Installed the TWRP.When i Flash the EU Rom the process finish normally and the phone boot also normal,the problem comes when i reboot the phone to recovery mode,i get the error "unable to mount data" (invalid argument) and "unable to mount /data/media/TWRP/"
I have already tried a lot of guides,for example how to convert f2fs DATA Partition format and the Cache to ext4 etc without success...
How can I fix this Problem and install then the weekly updates?i don't want to format my phone everytime i get an update....
SORRY FOR MY BAD ENGLISH
Up
I need your help please
my phone sometimes reboot automatic, the last get bootloop, and then the phone won't work properly.
Error on /system , /data , / cache, /storage (all of them get message "Invalid argument" but on system "No such file or directory"). Can't take picture of it because that's only my phone.
already doing anything from Google, Youtube, and MI forum. But all of them not work for my phone.
I tried to flash from MI flash and get error "remote: failed to write partition"
what I need to try :
1. Send your TWRP, PBRP, OrangeFox, Batik Recovery . Backup all of them and fresh (just like a new from factory reset) so i just only restore that
2. i need your suggestion what should i do
if all of them doesn't work too, well my last thing is buy a new phone
sorry for my bad English
Which model, what was the ROM installed on the phone before and which ROM were you trying to flash?
edizz0 said:
Which model, what was the ROM installed on the phone before and which ROM were you trying to flash?
Click to expand...
Click to collapse
Redmi 5A (RIVA) Installed CUSROM "Syberia OS 3x" trying to flash Stock ROM via MI FLASH but can't, error like the screenshot
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Janxr said:
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Click to expand...
Click to collapse
Just simply download and flash the Apollo's stock Fastboot ROM in fastboot mode
I tried flashing with with this: "apollo_global_images_V13.0.5.0.SJDMIXM_20220704.0000.00_12.0_global_3391fe8ef8"
is that the right version for my phone (bought in Germany)? I dont get an error while flashing but i just is not finishing. Its running for an hour now and still nothing happended. Ill update this if it finishes.
Edit: False alarm: After restarting the pc, i can connect again. But I still dont know what to do now.
I stopped the process after 2 hours and it got worse. In the recovery, i get the same issues as before, but my fastboot menu got replaced by onother one (I just see orange text that says fastboot). With that new fastboot menu I can not connect to my computer anymore.
Solved: I will never touch these Xiaomi tools again. platform-tools is just better and works
How did you solve the problem with the phone that cant connect to pc?