Develop Bugs

[Q] Help me pleaseee...uncryption unsuccessful

When i flashed the rom it says mount: failed to mount /dev/block/mmcblk0p28 at /data failed; no such volume
i dont know it then i flashed gapps and format /system and /data and reboot
Then it says uncryption unsuccesful

yup, that makes two of us. tried installing lollipop and phone went funky, not sure how to fix it. tried google but nothing helpful, hopefully somebody can help us on this.

Both of you have the right recovery?

Any fix??

Yes
Sent from my SM-G900F using XDA Forums Pro.

1-Install stock rom using ODIN and use OPS file , don't forget to wipe data after installation completes
2-Install CWM right version for your phone using ODIN
3-Install any ROM you want
hit thanks if it helped , if not please explain in more details your problem

Ok, for the Encryption unsuccessfull problem, this is what I did to get my Galaxy W to work.
In addition to format /system, /data etc, I had to format /storage/sdcard0 as EXT4. This gets past the Encryption unsuccessful problem, and I can flash the ROM CM12 and get it running.
But, I'm running into a weird problem that no one else seems to have come across. I can flash gapps 5.1.x, apparently without any failure messages on the flash window, and boot up.
Once the boot up is completed, I cannot see any of the Google apps icons at all !!?
I followed the same flashing process when installing CM 11 and 4.4 gapps, and this works fine. With CM 12, 5.1 gapps, I don't get any Google apps.
Anyone else came across this?
PS: After looking in the right place, many (all?) have the gapps problem in the cm-12.1-20150912-UNOFFICIAL-ancora thread. But I've also tried the RR rom with OTA updates. RR works - OTA just sits there with a blank page.

Nightly 14.1 lineageOS Rom For Crackling

https://download.lineageos.org/crackling
The First One!

Do we need su for arm or su for arm64?

Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64

What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs

kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite

M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs

AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.

Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?

Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"

Can this be installed over the top of cm13.0 nightly?

Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.

M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.

Wifi
Installed tonite smoothly however no wifi - anyone else with this?

Same here, just reported a bug to the bugtracker.

Make a clean install three days ago, all works fine

pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-

Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.

M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.

I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.

ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English

Unable to Mount Data in TWRP

I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!

You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs

Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Thanks for the response Unn113. Do I simply need to format and start from scratch?

trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2

Jackson.Armstrong.Blow said:
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Click to expand...
Click to collapse
Thanks!

trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Click to expand...
Click to collapse
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.

the Doctor said:
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
Click to expand...
Click to collapse
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Sent from my OnePlus5T using XDA Labs

Either blu_spark or ibe recovery work. They also work with lockscreen security setup, no problems over here.

Unn113 said:
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Click to expand...
Click to collapse
How do you figure? I've successfully backed up my previous ROM and flashed another one using that TWRP, my device is encrypted properly, I've reset lockscreen security, and my device passes SafetyNet.

Had the same issue. Flashing Blu_Spark worked perfectly. Thanks @the Doctor

help for twrp
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder,
icant install rom and wipe data and now dont have any rom to open my device
please help me

I had this problem after installing TWRP 3.2.1-1. A new version was released last night (3.2.1-2) which I flashed this morning and seems to solve the problem. You can find the new version here.

[RECOVERY][TWRP][OFFICIAL] TWRP 3.2.1.0 encrypted /data - cant mount

I searched and didn't found... searched longer than an hour....
nexus 5x, lineageos (not rooted), twrp installed, bootloader open
PROBLEM: when I reboot to recovery twrp asks for lock pattern, so I can't mount /data
Yes I can format data and so on...
But hoe can I flash ROMs (LOS-updates) without loosing the data every time?
Why can't I read the data partition?

First of all, you're posting in the wrong section.
Second, you answered your question yourself when you wrote the title - ENCRYPTED /data. Your /data partition should be decrypted. (read)
Flashing rom updates without losing your data is called dirty flashing - all you need to wipe is /cache and /dalvik(or /art), after that you simply flash the new rom build.
Keep in mind - dirty flashing could: cause new problems; not fix existing ones.
When experiencing issues, go for clean flash.

Thanks.
When Q&A is the right section, then this could be moved, I can't.
But: I did a clean flash, with "advanced data" and factory reset. And I got this encryption problem.
I already made a clean flash again and the pattern comes back.
I don't understand, where is the step I made the mistake.
Also got a g4 h815 here it works....

Again:
shhnedo said:
Your /data partition should be decrypted. (read)
Click to expand...
Click to collapse

Thanks I read it tomorrow, it's 2 aclock in the night in Germany....
By the way , I'm on 14.1 7.2.1 not on 8.1

shhnedo said:
First of all, you're posting in the wrong section.
Second, you answered your question yourself when you wrote the title - ENCRYPTED /data. Your /data partition should be decrypted.
Click to expand...
Click to collapse
Im also facing the same problem... But as you said it has to decrypted that's not correct as far as i know. I flashed many rom in my encrypted Nexus 5X. But never had any problem. Suddenly after flashing crDroid Oreo beta it keep s asking password.

Noob_Master said:
Im also facing the same problem... But as you said it has to decrypted that's not correct as far as i know. I flashed many rom in my encrypted Nexus 5X. But never had any problem. Suddenly after flashing crDroid Oreo beta it keep s asking password.
Click to expand...
Click to collapse
crDroid and many other LOS base ROMs have the "forcefdeorfbe" flag set in the boot.img. (It is the LOS standard to set this). While most don't feel there is a "speed hit" when running encrypted, I don't like the hassle between ROM flashes.

Recovery

What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?

altojd said:
What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?
Click to expand...
Click to collapse
Yes

Where did you find it ?

Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?

altojd said:
Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?
Click to expand...
Click to collapse
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works

a g bell said:
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works
Click to expand...
Click to collapse
i found this recovery in msm extended telegram chat.
the installation did not format my data since i have all my apps working and i can see the entire internal storage when i connect the phone to pc.

I have this recovery on my device for a later time in case I decide to move away from OOS so I can't speak to experience...BUT:
My understanding is due to decryption/recovery on this device the chinese recovery will work BUT the limitations are that if you are on OOS currently you cannot decrypt storage, HENCE you will not see anything in TWRP (again that is my understanding). After backing up the device and wiping the data partition at minimum (most custom roms seem to require us to fastboot wipe our partitions from instructions ive read)... then we can use this version of recovery for custom roms.
I think the major difference between this one and the official version here is of course the unofficial nature of this twrp but also the chinese twrp will let you flash (not boot) the recovery image without issue so we can still USE OOS OR flash custom roms without things going...wrong?...I plan to wait until the A11 OOS upgrade before I make a decision. After learning about how 1P botched the recovery keys + partition issues with the A10 launch I think its just better to see how development goes AFTER the new year maybe

Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.

a g bell said:
Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.
Click to expand...
Click to collapse
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.

Lossyx said:
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.
Click to expand...
Click to collapse
Ok l stand corrected just wondering why mauronofrio hasn't released an update or updated his thread. So OnePlus have to implement changes to keystore with Android 11 so they might fix it ?