Hi
I unlocked the bootloader and installed TWRP as described in the tutorials here. I then also flashed SuperSU. Afterwards I booted into stock Android and it worked. I wanted to do a factory reset so that after reinitializing I could install all my apps automatically. I went into TWRP --> Wipe --> Slide to Wipe. After rebooting it asked me for the pincode to decrypt. Since that didn't work I wiped everything except the SD Card and flashed lineage. Since then, my G6 keeps booting into TWRP. I even tried AquariOS (randomls chosen ROM) and I have the same results. I checked into "backup" in TWRP and the system partition is about 1GB. I then wiped it, and it went down to almost 0 I think. I then reflashed lineage and it was again at almost 1GB. So as it seems it is writing something. I then went into "mount" and system was not selected. I checked it and "mount system partition as read only", rebooted into the system, and it booted into TWRP again, system was unchecked under mount, but the read-only option was still checked. tried the same without the read-only option, same result. So now my G6 keeps mounting into TWRP instead of the ROM.
Any ideas what I can do?
Format data in recovery, don't wipe. It will disable encryption. Flash stock 14a again and see if you can get it to boot
I fixed it, somehow TWRP was messed up. I redownloaded it and reflashed it and then it worked
Related
I flashed the root, then a twrp 3.0.2.0 recovery with odin and than went to recovery to make wipes. Had an issue with formatting cache (it was never ending process, more than 20 minutes) I lost my patience and removec the battery, came to twrp recovery again, enabled -rf fix in settings. Wiped everything and then came to install, chose the ROM and proceeded - then an error jumped, that the system was not mounted.
I tried almost everything, but system wont mount with twrp.
Is my only option to get back to official stock?
Did you try TWRP 2.8.7?
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Controllerboy said:
Hi
I'm having this very weird issue with my phone (A2017G). I unlocked BL, installed TWRP, updated to TWRP 3.0.3-1, formatted data, factory reset, install A2017G_Nougat_Bootloader+ModemFix, factory reset again, install LineageOS and then boot. The device booted fine.
I noticed root wasn't built-in so I flashed SuperSU V2.65. After a reboot, my phone won't let me boot into the system anymore. I get asked for a password. Whatever password I enter, it says "Decryption Unsuccesful. The password is correct, but data is corrupt". When I reboot to TWRP and format data and then factory reset, nothing changes. I keep getting the prompt before system boots. Even re-flashing the bootstack and lineageOS doesn't help. I know flashing anything else will brick my phone, so I refrained from doing that.
What am I doing wrong here?
Note that TWRP reads both my internal storage and my SDcard. However, internal storage contains only the folder "TWRP". When I go up a level, I can see the normal folders like "boot", "cache", "data", "dev" and so on. In the "backup" menu, DATA also shows as "0MB"
File system says "f2fs". Do I repair/change it?
Thanks
Click to expand...
Click to collapse
I would say the answer lies with issues between f2fs and SuperSU
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my SM-P600 using XDA-Developers Legacy app
And you flash the wrong SuperSU, the one needed is either v.2.79 or v.2.79-R3. try booting back to TWRP and clean Flash Lineage again and flash either one of the SuperSu I Mention before.
I have the same after install unofficial lineage 14.1 'decryption unsuccessful'
On TWRP 3.0.3-1 I go in 'wipe', then 'advanced wipe' and select 'Data', press 'Repair or Change File System' and then 'Change File System' to EXT4
That's work fine on my 2017G
For root
download.lineageos.org/extras
The arm64 zip
After install with TWRP go in deployment options and activated it!
Lineage is running with root
Thanks, everyone. That worked. I was quite worried for a while, I really don't want tot RMA the device a second time due tot me messing things up.
Where do I find the options in Twrp for deployment
jdg007 said:
Where do I find the options in Twrp for deployment
Click to expand...
Click to collapse
Twrp have no deployment option, what won't you to do.
joergwrage said:
Ah,
I have/had the same error. Looks like this needs to be changed to ext4.
CU
Joerg
Click to expand...
Click to collapse
Probably it is caused by a known bug in the f2fs implementation in the kernel. Only @Unjustified Dev can solve it. Some people who already was using f2fs with TWRP 3.0.4 and LineageOS 13.1 are not having those issues and they were able to dirty flash the new LOS 14.1.
Updating to TWRP 3.0.3-1 is very recommended. TWRP 3.0.2 has some problems when flashing zips. SuperSU is one of them.
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
crazynitro said:
i Also need help guys :/ my auto rotate isnt working. neither is mu auto brightness :/
Click to expand...
Click to collapse
I have the same
I installed TWRP on my device. It worked nicely and I booted into twrp recovery. I thought of doing a factory reset. So, I selected the format option on TWRP. It showed something like "Formatting Data using make_extfs". I left it there. My brother came and pulled out the battery from the mobile. I booted up the phone thinking the process was over. I was stuck in a bootloop. I then booted into twrp again. I tried to wipe cache, but a error message came up showing something like "Failed to mount /data". I tried recovery option on TWRP. There it is showing, 0 MB internal storage. I think the storage got corrupted. Any solutions to this?
Try wiping your all partitions. All at once
So I was using a certain root app and it told me to enable Magisk Core mode and reboot. I did that, and my phone was in a bootloop. So I wen't to TWRP and flashed stock ROM zip. Rebooted and it was still bootlooping.
So I took a TWRP Backup of all partitions, and then wiped system fully and flashed stock ROM. Still bootlooping. So I did a factory reset and wiped system as well, keeping internal storage. Then I flashed stock ROM zip and rebooted - it fixed it, but was factory reset. So I went back into TWRP and restored the data partition. Unfortunately, I got the TarFork Error 255 when restoring. I saw on google that you need to setup Android first to restore. Rebooted to go into Android but it took me to TWRP, and this time didn't ask for decryption password. I went to internal storage and everything was encrypted. I don't remember exactly what I did next but now I'm in fastboot with no TWRP recovery, and when I do fastboot boot twrp.img I get this error: "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')"
Can anyone help me recovery from this and possibly get my internal storage back, or at least installed apps. I can provide TWRP restore log as well: https://del.dog/ivugupemeq
NateDev said:
So I was using a certain root app and it told me to enable Magisk Core mode and reboot. I did that, and my phone was in a bootloop. So I wen't to TWRP and flashed stock ROM zip. Rebooted and it was still bootlooping.
So I took a TWRP Backup of all partitions, and then wiped system fully and flashed stock ROM. Still bootlooping. So I did a factory reset and wiped system as well, keeping internal storage. Then I flashed stock ROM zip and rebooted - it fixed it, but was factory reset. So I went back into TWRP and restored the data partition. Unfortunately, I got the TarFork Error 255 when restoring. I saw on google that you need to setup Android first to restore. Rebooted to go into Android but it took me to TWRP, and this time didn't ask for decryption password. I went to internal storage and everything was encrypted. I don't remember exactly what I did next but now I'm in fastboot with no TWRP recovery, and when I do fastboot boot twrp.img I get this error: "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')"
Can anyone help me recovery from this and possibly get my internal storage back, or at least installed apps. I can provide TWRP restore log as well: https://del.dog/ivugupemeq
Click to expand...
Click to collapse
Have you tried the MSM Download Tool to restore the device yet? I'm leaning towards that honestly.
---------- Post added at 01:44 AM ---------- Previous post was at 01:42 AM ----------
NateDev said:
So I was using a certain root app and it told me to enable Magisk Core mode and reboot. I did that, and my phone was in a bootloop. So I wen't to TWRP and flashed stock ROM zip. Rebooted and it was still bootlooping.
So I took a TWRP Backup of all partitions, and then wiped system fully and flashed stock ROM. Still bootlooping. So I did a factory reset and wiped system as well, keeping internal storage. Then I flashed stock ROM zip and rebooted - it fixed it, but was factory reset. So I went back into TWRP and restored the data partition. Unfortunately, I got the TarFork Error 255 when restoring. I saw on google that you need to setup Android first to restore. Rebooted to go into Android but it took me to TWRP, and this time didn't ask for decryption password. I went to internal storage and everything was encrypted. I don't remember exactly what I did next but now I'm in fastboot with no TWRP recovery, and when I do fastboot boot twrp.img I get this error: "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')"
Can anyone help me recovery from this and possibly get my internal storage back, or at least installed apps. I can provide TWRP restore log as well: https://del.dog/ivugupemeq
Click to expand...
Click to collapse
(Double post, ignore this)
Got it fixed by flashing full stock ROM in fastboot without wiping, so userdata was recovered, and then restored app data from the TWRP nandroid backup in Titanium backup
NateDev said:
Got it fixed by flashing full stock ROM in fastboot without wiping, so userdata was recovered, and then restored app data from the TWRP nandroid backup in Titanium backup
Click to expand...
Click to collapse
mind sharing exactly how you did that? As i'm in pretty much the same boat
FullyCustom2 said:
mind sharing exactly how you did that? As i'm in pretty much the same boat
Click to expand...
Click to collapse
Damn don't even have this phone anymore lol
I think I used the fastboot ROMs from an xda post but when it asks you to wipe or not I clicked no, and then I booted to Android and apps data can be restored from a nandroid backup in titanium backup, just search to find that feature, instead of restoring the data backup in twrp
This error always happens and stays forever after I reboot into the rom the first time. I turn on OTA updates for the ROM all the time, and currently on crDroid 6.11. Error makes it so I cannot flash other things on top of the rom like ANXCamera.
Tried to repair the /data partition, but it also comes out with an error:
/sbin/e2fsck -fp /dev/block/mmcblk0p66 process ended with ERROR: 1
Unable to repair data. I rebooted to system, then rebooted back to the recovery, and repaired the /data partition again, but this time it was successful. but it did not solve the issue, the "Have you lost something?" prompt stayed there.
Decryption works fine, I have a pattern lock and fingerprint, and when booting into recovery and OrangeFox asking for the pattern to decrypt the drive, it works fine and I can see the files, so I don't think its an encryption issue.
I also flashed Magisk by rebooting to recovery a second time after flashing the rom then flashing Magisk.zip
The only way I worked around this issue before was by wiping system, cache, dalvik and formatting data partition, and reinstalling OrangeFox. but it still comes back after flashing crDroid again and booting into the ROM, I don't have any idea how to fix the error.
Every time you install a new ROM, the internal storage in wiped . Internal storage contains a folder "Fox" which contains OrangeFox addons. When it gets deleted , you get that message in recovery.