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!
Hello,
I have a big problem with my H815. I've installed H-ROM_V30-PORT-V2.1 but now I have no signal / no service and my IMEI is "unknown".
The steps i did before:
1. Unlocked the bootloader with this tutorial:
https://www.youtube.com/watch?v=O64GfQORCaE&t=450s
2. Installed TWRP (twrp-3.2.0-0-g4.img)
3. Made a full backup with TWRP (efs, boot, system, cache, etc...) and copied the backup at my pc.
Then i wiped the phone.
4. Installed H-ROM
https://forum.xda-developers.com/g4/development/rom-h-rom-v30-port-t3672567
So the system is working well and booting, but I have no signal and my IMEI is "unknown" in the android settings.
I thought this could be not a big problem, because I made a TWRP backup. So I copied the backup-files back from my PC to the phone.
At TWRP I can choose the backup but then nothing will happen.
The screen shows:
Running Recovery Commands
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Thats all. But TWRP does not restore anything.
Can you please help me??? I have no idea what I could do now :crying::crying:
I forgot a very importent step.
At the end I rooted the phone with SuperSU. And that's the step, when my IMEI got lost.
I used UPDATE-SuperSU-v2.76-20160630161323.
Is there a way to root the phone without loosing the imei???
try this: https://forum.xda-developers.com/showpost.php?p=73489308&postcount=2
Hello, I've buyed a Moto z2 play. I unlock the phone, I do a nandroid backup, then I flash Oreo 64 bit, then I reflash stock nougat. At this point, cause I'm an idiot, I make a format, so I loose my backup. I try to flash this and that but nothing. Fortunately I download a persist partition's backup (from another device) from the web and now my 2 IMEI are 0, i can't rewrite they with original IMEI I have (I think), I lost my serial number (?) and I lost my 4g (LTE).
I think it is because I've format a persist partition (perhaps) or other important partition.
I need help if anyone can rewrite a persist file with my original IMEI or if anyone can share this partition backup. I've a xt1710-09 (Italy).
Is it possible to relock bootloader and send phone to lenovo or I can brick the device?
Thanks
http://ilmiodiarioprivato.altervista.org
the folder is still in your system is recommended to find more about the subject, I managed to recover the imei of a moto.g4play do not lose the imei completely
you need a version of TWRP that is compatible with write twrp correctly and take a backup of your phone (this is achieved by formatting the persistent area and loading a stock software with the correct commands you have to verify your imei from fastboot, barcodes section , if it still appears, you can recover it
Thanks for your reply. When I came back home I try to restore the partition (or brick the phone)!
http://ilmiodiarioprivato.altervista.org
Hello,
I was disabling journaling on my device's partitions then after rebooting from the TWRP I found a very slow startup. After that I thought it a bootloop. So I installed the previous ROM which was DevBase, followed by many as Alexis and others they were all giving the same a bootloop or at least what I thought it was.
So I flashed a stock firmware but the true issue started after this the IMEI is invalid and showing as null.
I found an EFS backup inside of .backup/efs/efs_bqckup.img.tar inside of the OTG folder together with recent.img something like that.
I tried to Gunzip to restore on the /sda3 partition didn't work nor direct dd command worked for the .img
How can I restore my EFS or repair the IMEI in a legal way note that I've everything for the phone including it's IMEI.
I was on NLOS 16 and it's running well. the problem starts when I try to connect a public wifi network and phone hang. after force reboot phone stuck at boot animation for a long time. I tried force reboot to recovery doing clear cache, factory reset nothing works. Suddenly notice that my data partition is 0 MB after changing the partition type phone does not boot up. I tried almost every solution that I found. it boots some time but freez on setup wizerd , if i pass the setup wizerd it hang.
list of my worth try
1. followed mega unbrick tutorial, flash success without any issue but stuck at boot animation. sometimes it boots but no IMEI but it shows my network.
2. erasing modemst1 and modemst2 stuck at boot animation.
3. no matter which rom i flash it just stuck at boot animation. some time it shows encryption unsuccessful but after format data result is the same.
4. now it seems I had messed up with my efs AND I DON'T HAVE any backup of my efs partition but fixing it by erasing modemst1&2, erasing persist and reflash persist does not work.
5. restore twrp does not work.
don't know why it stuck at boot animation.it was running well 2 days ago .
is there any other way to fix it??
i have my both imei no and pcba no.
sorry for bad english as i am not so well in english.