Related
Hi guys, i'm in desperate need of your help. i think my precious o3d might have been screwed.
first let me tell you what i did. as you know the internal sd card of o3d is 5gb or so and it fills up very quickly. this internal sd card is mounted as /sdcard. i have a class 10 16gb micro sd card and when i insert it, its automatically mounted as /sdcard/_ExternalSD. The applications or games, especially the ones that have external data folders which are like 1gb in size insists to be installed on /sdcard. You can't move those data folders to _ExternalSD, because then the apps doesn't work.
Then i came across this topic:
http://forum.xda-developers.com/showthread.php?t=1189701
As you can see that was exactly what i needed. I had CWM 5.0.2.0 installed so i downloaded the first .zip then copied all of the files and folders excluding the _ExternalSD folder to the external sd card then rebooted into recovery. From there i flashed the zip and rebooted again. phone booted up and all was ok and it worked. now the phone sees the external sd card as the internal one and the internal sd card was mounted as /sdcard/_ExternalSD. I then formatted the internal sd card from the settings menu because i already copied all of the stuff there to the external card. It worked fine and the internal card is formatted. After that i decided to get a nandroid backup so i opened the rom toolbox program. From the menus i selected the backup option, gave it a name, clicked ok. the phone rebooted into cwm recovery screen but nothing happened. then i noticed something was not right because there was some error lines under the cwm menus saying "E:can't mount CACHE:recovery/command" etc. Then i selected the reboot phone option but the phone rebooted right back into the CWM recovery again!! At that point i knew that i was @#?^ed.
Anyways i researched a lot and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1156549
i did exactly what he said and it worked, i mean it flashed nicely. then i rebooted the phone but it booted into the recovery again!!! But this time the CWM recovery was gone and i believe this is the stock recovery screen. I can browse the menu of it and make selections but the phone boots into the recovery every time it reboots.
The recovery screen looks like this:
http://farm8.staticflickr.com/7010/6654644033_b616bc0635_z.jpg
Then i flashed the phone to the latest official firmware V21A_00, it flashed nicely but it still boots right into the recovery everytime.
Then i installed the Android SDK and tried to push the original vold.fstab file to the system using the adb command line tool but it doesn't see the phone. I think adb works only when the system boots up normally, not in the recovery mode.
I don't know if there's a way to install the CWM from the stock recovery somehow. If you know how, please tell. The CWM has more options.
I don't know what else i can do. It started to look ridiculous. If there are any experts cool enough to help please do so. I'll be waiting. Thank you...
Edit:
I also tried this:
http://forum.xda-developers.com/show....php?t=1244490
I starts just fine but get's stuck on the "RESET" command, after a while it gives "DOWNLOAD FAIL!" error. I think the phone is supposed to restart automatically but it doesn't. Manually resetting the phone doesn't work either.
I'm about to pull my hair out...
Edit 2:
I also posted on the official LG Mobile forum here:
http://www.lgforum.com/forum/boards...d-goes-into-recovery-mode-every-time-it-boots
Fingers crossed
Quite a post!
From all your post there is no mention that you formated and did a factory reset after 21a flash.
Can you please try that if you haven't?
Sent from my LG-P920 using xda premium
thank you for the reply!
i tried all 4 wipe options on the recovery screen then rebooted. it's the same, i'm back at the good old recovery again
Did you try with the external sd card out?
This is strange, usually a kdz flash coupled with a format fixes the problem.
Some how it still can't find the internal SD card.
I don't have further recommendations. Sorry
Sent from my LG-P920 using xda premium
yes i tried with the external sd card out. it didn't work..
vpamir said:
yes i tried with the external sd card out. it didn't work..
Click to expand...
Click to collapse
Hopefully someone else on this forum can suggest a way for you to unbrick.
your problem is although you have reset your phone, somehow it can't find a partition to boot from.
or
somehow the KDZ flashing is not totally successful.
good luck
If only there could be a way to be able to use the adb command from the Android SDK then i might be able to restore the vold.fstab file to its original, if the problem is that at all. Maybe then it'll work. To be able to flash the CWM Recovery again somehow might be a good thing too because it has more options like flashing .zip format roms but i have no idea how. Does anyone know if the stock recovery can flash some specifically named file to the system, does it have that kind of functionality? I'm desperate, please share your thoughts.
.............anyone?
I am sorry to say that but there is no solution for this problem yet. I have done the exact thing that you do and tried every single solution with no luck. The only way is to send it to lg repair service. My solution was to replace the mainboard.
Dostum gecmis olsun malesef tek cozum yolu anakarti degistirmek. Uzaman sayilirim android konusunda bosuna ugrasmayasin diye soyluyorum. LG servisi bile anca anakarti degistirerek cozum sunabildi. Temel problem internal karti formatlamis olman. Partititon table'i bozuyor bu islem malesef ve bu yuzden hicbir yontem ise yaramiyor.
Gecmis olsun tekrar...
so you say that the main problem was to format the internal sd card? well if formatting the internal sd card bricks the phone then why the hell is there an option to format it in the settings menu?
well if you didn't apply the swap fix, it wouldn't be a problem to format. When you swap the sd cards and format, it is the problem.
crime_of_heart said:
well if you didn't apply the swap fix, it wouldn't be a problem to format. When you swap the sd cards and format, it is the problem.
Click to expand...
Click to collapse
so you did exactly the same thing as me right? i mean you applied the swap fix then formatted the internal sd?
replacing the motherboard to fix this seems to be a bit nonsense to me to be honest. what does the partition table have anything to do with the motherboard?
if only there would be a .kdz format custom rom which factory resets the internal sd card during the flash process and maybe fixes the bootloader somehow, that might be the solution.
yes i did the same and the only solution was to replace the motherboard. we need a sowftware that can reach to the emmc in low-level. like omap flasher. but we also need the correct drivers which doesn't exist yet.
crime_of_heart said:
yes i did the same and the only solution was to replace the motherboard. we need a software that can reach to the emmc in low-level. like omap flasher. but we also need the correct drivers which doesn't exist yet.
Click to expand...
Click to collapse
i don't know what the emmc is, i need to do research on that. but i still think that replacing the motherboard won't solve this issue because it seems non relevant to me. i messed up with the vold.fstab file. but after that it worked fine. i mean the internal and external cards swapped just fine. only after i decided to make a nandroid backup using rom toolbox all hell broke loose. i plan to wait a couple of days before turning the phone to LG service. i believe someone will come up with an idea.
yardım etmeye çalıştığın için teşekkür ederim bu arada
Well, there´s a new recovery for the O3D, v5.0.2.7 (I got it with ROM Manager).
It fixes 2 bugs of the previous (5.0.2.0) version: now the USB mass storage option in the mounts menu works (mount external SDCARD), and we can use ADB while in recovery. That way we can fix stuff in the phone filesystem while in recovery: we can now use ADB shell, or ADB push to replace files.
The problem is that I don´t know how to flash it to the phone while in the stock recovery. If someone can guide me on creating a signed ZIP containing this new recovery, flashable in the stock recovery, I would be glad to do that and post it here. I think these phones of you guys can be fixed using this method!
Marcovecchio said:
Well, there´s a new recovery for the O3D, v5.0.2.7 (I got it with ROM Manager).
It fixes 2 bugs of the previous (5.0.2.0) version: now the USB mass storage option in the mounts menu works (mount external SDCARD), and we can use ADB while in recovery. That way we can fix stuff in the phone filesystem while in recovery: we can now use ADB shell, or ADB push to replace files.
The problem is that I don´t know how to flash it to the phone while in the stock recovery. If someone can guide me on creating a signed ZIP containing this new recovery, flashable in the stock recovery, I would be glad to do that and post it here. I think these phones of you guys can be fixed using this method!
Click to expand...
Click to collapse
Great news! But now i need to find a way to install the new CWM. Just as you said i believe what i need is to find or make a .kdz update which includes this new CWM.
What do you think?
I know this is possible, at least for the Galaxy Ace: I have a ZIP file for this device with a custom recovery image, flashable in stock recovery!
To make one for the Optimus 3D, I need to know the following:
- How can I obtain the .IMG of the new recovery? I have found some temp files in clockworkmod folder in my sdcard. The creation date of one of them matches the exact moment I upgraded my recovery, and the file size also matches a recovery image: 5.54MB. Is it the recovery image? Can I just rename it to recovery.img? How can I extract it to ensure it´s ok?
- After I get the recovery image, I can use the Galaxy Ace ZIP as the base to build the O3D zip file. Any help on what do I have to change to make it work correctly?
I also tried this:
http://forum.xda-developers.com/showthread.php?t=1244490
I starts just fine but get's stuck on the "RESET" command, after a while it gives "DOWNLOAD FAIL!" error. I think the phone is supposed to restart automatically but it doesn't. Manually resetting the phone doesn't work either.
I'm about to pull my hair out...
Edit: I'm 99% sure that this isn't a hardware related problem. And LG's software not being able to turn the phone to stock is totally [email protected]#$%!
On some "unbrick your optimus 3d" threads i came across this image:
http://attachments.xda-developers.com/attachment.php?attachmentid=667470&d=1311752328
i tried all methods around here but not once i came across a screen like it. weird...
well i give up guys. so much technical [email protected] going on and no one seems to understand this device enough. i'll turn it to the LG Repair Service today. Thank you everyone for your help...
So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]
Did you ever find a fix? I'm having a similar problem.
Try to use fastboot restore everything.
I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device
Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.
If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.
I upgraded to the latest Q4 beta. When doing this following instructions when flashing in TWRP it said to flash the file from USB otg since you couldn't flash from internal storage.
my question is, once you have Q installed as I do can you never flash files from internal storage? i assume this must be the case, or i have something very wrong with what i'm doing. I can't mount my internal storage at all in TWRP or see any of the files.
knives of ice said:
I upgraded to the latest Q4 beta. When doing this following instructions when flashing in TWRP it said to flash the file from USB otg since you couldn't flash from internal storage.
my question is, once you have Q installed as I do can you never flash files from internal storage? i assume this must be the case, or i have something very wrong with what i'm doing. I can't mount my internal storage at all in TWRP or see any of the files.
Click to expand...
Click to collapse
Everything works but decryption.
We may have to wait until official q comes before decryption works.
You may find ways to run unencrypted using search function. I know it has been talked about in the forum.
twinnfamous said:
Everything works but decryption.
We may have to wait until official q comes before decryption works.
You may find ways to run unencrypted using search function. I know it has been talked about in the forum.
Click to expand...
Click to collapse
Do you have any idea what could be wrong with my install or setup? I can't mount system. It can't even see my internal sd card it lists it as 0. Never had anything like this happen
knives of ice said:
Do you have any idea what could be wrong with my install or setup? I can't mount system. It can't even see my internal sd card it lists it as 0. Never had anything like this happen
Click to expand...
Click to collapse
U can't see anything in SD card if decryption doesn't work.
What twrp and what where your steps to get where you are now?
twinnfamous said:
U can't see anything in SD card if decryption doesn't work.
What twrp and what where your steps to get where you are now?
Click to expand...
Click to collapse
yes, i know what you are saying with encryption when you can't decrypt it still shows everything with crazy decrypted numbers like 8784322qzzwerei, etc. Even if i turn off my security and boot into twrp (i'm running the latest version i believe 3.3.1-50 according to the twrp menu) it can't see anything on internal storage. when you go to select storage it shows 0mb under internal storage. if i plug in a usb otg it immediately shows and reads that.
if i want to select a file it says select file from internal storage (0 mb)
I have things installed to slot A. these slots i'm not used to using but maybe someone when it boots to twrp its not on the right slot or something? any ideas?
knives of ice said:
yes, i know what you are saying with encryption when you can't decrypt it still shows everything with crazy decrypted numbers like 8784322qzzwerei, etc. Even if i turn off my security and boot into twrp (i'm running the latest version i believe 3.3.1-50 according to the twrp menu) it can't see anything on internal storage. when you go to select storage it shows 0mb under internal storage. if i plug in a usb otg it immediately shows and reads that.
if i want to select a file it says select file from internal storage (0 mb)
I have things installed to slot A. these slots i'm not used to using but maybe someone when it boots to twrp its not on the right slot or something? any ideas?
Click to expand...
Click to collapse
Has the rom booted yet? Did u wipe? Nevermind forgot on q it just shows 0mb
U can try switching slots but it might put u back to rom u had before.
As was previously stated, TWRP cannot decrypt data on q. TWRP will have to be updated to address this. It will be the same for everyone.
Once you boot into rom, all your data will be accessible.
Maybe try fastboot boot twrp.img as that may allow decryption
miffymiffy said:
As was previously stated, TWRP cannot decrypt data on q. TWRP will have to be updated to address this. It will be the same for everyone.
Once you boot into rom, all your data will be accessible.
Maybe try fastboot boot twrp.img as that may allow decryption
Click to expand...
Click to collapse
even if i remove all encryption from my device the system still shows at 0mb. which means you can't flash anything in twrp from the sd card.
i'm trying to figure out why i can't get magisk vanced to work and i assume it is because the flashing in magisk isn't occurring correctly.
so does everyone show a system in twrp for q at 0mb? if what i have is normal and the norm, fine but that was the reason for this thread to list the differences/limitations of twrp in q.
I believe TWRP can't access the internal sdcard due to the change in Q called Scoped Storage:
https://developer.android.com/preview/privacy/scoped-storage
This is also why Magisk vanced isn't installing properly
docnok63 said:
I believe TWRP can't access the internal sdcard due to the change in Q called Scoped Storage:
https://developer.android.com/preview/privacy/scoped-storage
This is also why Magisk vanced isn't installing properly
Click to expand...
Click to collapse
i agree.
the problem is, some are reporting no problems with youtube vanced through magisk. others are claiming that they can see the data on their sd card. i have no idea, maybe some of these people don't even have the q beta installed.
knives of ice said:
i agree.
the problem is, some are reporting no problems with youtube vanced through magisk. others are claiming that they can see the data on their sd card. i have no idea, maybe some of these people don't even have the q beta installed.
Click to expand...
Click to collapse
I've been on DP2, 3, and now 4 and never been able to see internal in TWRP. All flashes have had to be done via OTG after the initial Q install.
docnok63 said:
I've been on DP2, 3, and now 4 and never been able to see internal in TWRP. All flashes have had to be done via OTG after the initial Q install.
Click to expand...
Click to collapse
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
knives of ice said:
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
Click to expand...
Click to collapse
I have YouTube Premium so I don't mess with vanced. Sorry...
knives of ice said:
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
Click to expand...
Click to collapse
Because if your run your device unecrypted you can access the data partitions in TWRP while running Q.
Namolas said:
Because if your run your device unecrypted you can access the data partitions in TWRP while running Q.
Click to expand...
Click to collapse
i remove all fingerprints/pins and have no security. i should be able to boot into TWRP and see data then correct?
it still shows 0mb for me and won't mount.
knives of ice said:
i remove all fingerprints/pins and have no security. i should be able to boot into TWRP and see data then correct?
it still shows 0mb for me and won't mount.
Click to expand...
Click to collapse
Currently decrypted state, and running the device unencrypted aren't the same. Even with your fingerprints pins removed if you look in Settings/Security you'll see your device still shows as encrypted.
OnePlus 7 forces encryption by default. To run your device unencrypted you have to format the internal storage (wipes everything pictures media etc) and make sure you flash a special disable force encrypt zip every time you flash anything system related in TWRP.
Its a lengthy process to get it running unencrypted and if you forget to flash the special script even one time OP7P will force encrypt on boot and you have to start over. Its not for everybody but I know a lot of people running this way, myself included.
This should all be fixed with and update to TWRP but who knows how long that will take.
Not sure if this is worth anything or not, but it's decryption related: https://gist.github.com/mauronofrio/af29bad34ad87a1a957d193794f0bf5f
Namolas said:
Currently decrypted state, and running the device unencrypted aren't the same. Even with your fingerprints pins removed if you look in Settings/Security you'll see your device still shows as encrypted.
OnePlus 7 forces encryption by default. To run your device unencrypted you have to format the internal storage (wipes everything pictures media etc) and make sure you flash a special disable force encrypt zip every time you flash anything system related in TWRP.
Its a lengthy process to get it running unencrypted and if you forget to flash the special script even one time OP7P will force encrypt on boot and you have to start over. Its not for everybody but I know a lot of people running this way, myself included.
This should all be fixed with and update to TWRP but who knows how long that will take.
Click to expand...
Click to collapse
Thanks for your post.
So if I want to "dirty flash" a rom on android q, is it still possible with data encrypted or should I format internal storage anyway ? (and clean flash...)
Gabrech said:
Thanks for your post.
So if I want to "dirty flash" a rom on android q, is it still possible with data encrypted or should I format internal storage anyway ? (and clean flash...)
Click to expand...
Click to collapse
On my Pixel (original) with TWRP 3.3.0-0 and Q, I am able to do everything normally, including decrypting, dirty flash, cutstom ROMs, factory, nandroids, etc .... However, /system and /vendor won't mount. But, it works anyway!
The scoped storage is still a pain in the butt.
Hey guys,
my first Thread/post here. cause I have a slight problem (I do hope that I'm in
Today, I wanted to make an update of LineageOS 18.1 for my Samsung S7 herolte mobile. Therefore I use the custom ROM from Ivan Meler. Since some time, a bug accures, that an update needs a complete wipe of everything, cause elseways, Lineage wouldn't boot - I don't know why. This is something I completely forgot, so I never did a backup - something I usually do.
First Idea to solve it was simply do a backup with TWRP. This fails right away, because I used my external SD Card as a expansion for the internal storage. Thats a function of android as far as I can tell you can use at first use of the sdcard. Anyways, I can't mount the sdcard so that method fails.
Second try is using adb. The Partition is encrypted, so I use
twrp decrypt "PASSWORD" as described here. But TWRP gives me Failed to decrypt data. with no further details why. I am very certain I enter the correct password. I don't understand why it fails and never found a way to find further details to it. The only and easiest way to see it would be, that the data is corrupted but I doubt it. Starting up lineage fails (restart) after the submission of the passphrase.
My third Idea is using USB OTG but I lack the hardware to do so. Well, I could use my computer to do that, but TWRP seems to not recognise the computer as a storage device.
Does anyone have an Idea how to solve that mess? I don't want to loose 6 Months of data...
Edit: As I continue to learn: maybe the recovery.log from twrp helps - I couldn't find sth useful in there.