Develop Bugs

No keyboard to access encrypted phone

I am running Rujelus's latest Blue Kuban ROM and after installing the most recent update, decided to encrypt my phone. I have thought about doing this for a while but did not have the time as it is a long process (1 hour +). So I went into Settings > Security, created a password and let it run through the encryption process. After about an hour the phone rebooted and a screen comes up asking for a password, which I know, but there is no keyboard on the screen! I push in the password box and all over the screen and nothing. I assume this is the accidental result of some feature of Blue Kuban, but now I have an encrypted phone and no way to access it. To restate - I KNOW the password, I just have no way to enter it on the screen.
I assume I can Odin back to stock and reset the whole phone, but I will lose EVERYTHING I was trying to protect (since all my backups are now encrypted too.) So my question is, is there any way to fix this? Perhaps something I can do in ADB? Some keypress combination that would make the keyboard appear? Anyone? Anyone?

dr_gibberish said:
I am running Rujelus's latest Blue Kuban ROM and after installing the most recent update, decided to encrypt my phone. I have thought about doing this for a while but did not have the time as it is a long process (1 hour +). So I went into Settings > Security, created a password and let it run through the encryption process. After about an hour the phone rebooted and a screen comes up asking for a password, which I know, but there is no keyboard on the screen! I push in the password box and all over the screen and nothing. I assume this is the accidental result of some feature of Blue Kuban, but now I have an encrypted phone and no way to access it. To restate - I KNOW the password, I just have no way to enter it on the screen.
I assume I can Odin back to stock and reset the whole phone, but I will lose EVERYTHING I was trying to protect (since all my backups are now encrypted too.) So my question is, is there any way to fix this? Perhaps something I can do in ADB? Some keypress combination that would make the keyboard appear? Anyone? Anyone?
Click to expand...
Click to collapse
Did you encrypt just the device or the sdcard also? Also is ADB enabled on the phone?

crawrj said:
Did you encrypt just the device or the sdcard also? Also is ADB enabled on the phone?
Click to expand...
Click to collapse
I think I just encrypted the device. (Encrypting the SD card would take a second pass, correct?). I also realized that I can access CWM, so if I could get some mod onto the SD card that can get the keyboard back, then I can flash through CWM, and I should be set.
FYI, I just plugged the phone into the USB port of the computer, and the drives appear under My Computer but when I try to access them I get "Insert a disk into removable drive E:". It does look like it is recognized under ADB. I can also take the SD card out and just stick it in my laptop if I can find a mod that will get me the keyboard back....

dr_gibberish said:
I think I just encrypted the device. (Encrypting the SD card would take a second pass, correct?). I also realized that I can access CWM so if I could get some mod to get the keyboard back onto the SD card, then I can flash through CWM, and I should be set.
FYI, I just plugged the phone into the USB port of the computer, and the drives appear under My Computer but when I try to access them I get "Insert a disk into removable drive E:". It does look like it is recognized under ADB. I can also take the SD card out and just stick it in my laptop if I can find a mod that will get me the keyboard back....
Click to expand...
Click to collapse
And you do have CWM backups right? If so they should be on the sdcard. If they are on the internal storage instead let me know and I can help you move them. I would use calkulins format all zip from cwm. After that restore your backup from CWM. You should be fixed after that.

crawrj said:
And you do have CWM backups right? If so they should be on the sdcard. If they are on the internal storage instead let me know and I can help you move them. I would use calkulins format all zip from cwm. After that restore your backup from CWM. You should be fixed after that.
Click to expand...
Click to collapse
Unfortunately, the last nandroid backup I have is pretty out of date though you're right that at least that would solve some of the problem (I wouldnt lose everything). I backed up with Titanium last night before updating the ROM, but did not nandroid.
However, I am really wondering if there is something I can flash that would make the keyboard appear on the initial screen. The Blue Kuban updater has a mod - "Restore the keyboard popup" that I think might fix this issue, however I cant figure out how to get that mod since I cant get into the phone to download it. I posted in the Blue Kuban thread and perhaps someone can download the mod and post it there.
Thanks for your help, I certainly feel more hopeful than I did when I first realized this...

dr_gibberish said:
Unfortunately, the last nandroid backup I have is pretty out of date though you're right that at least that would solve some of the problem (I wouldnt lose everything). I backed up with Titanium last night before updating the ROM, but did not nandroid.
However, I am really wondering if there is something I can flash that would make the keyboard appear on the initial screen. The Blue Kuban updater has a mod - "Restore the keyboard popup" that I think might fix this issue, however I cant figure out how to get that mod since I cant get into the phone to download it. I posted in the Blue Kuban thread and perhaps someone can download the mod and post it there.
Thanks for your help, I certainly feel more hopeful than I did when I first realized this...
Click to expand...
Click to collapse
I have never messed the the encryption so I don't know if this is possible, but if that doesn't work you might try to install a stock rom from CWM and see if that gives you the keyboard back.

crawrj said:
Since your sdcard isn't encrypted you should be able to copy the mod there and install it from CWM. Just put it in the computer and copy the Mod to it.
Edit: Nevermind I see is isn't a zip file now.
Click to expand...
Click to collapse
I think it IS a zip, I just don't know how to get to it other than through the updater which is built into the ROM. Typically, all the files in the updater download to your SD card as zip files and then the phone will reboot and install them in CWM automatically. I just need someone to download the mod on their phone running Blue Kuban and then post it here so I can copy it to my SD card and install it. (That's assuming it really does fix this issue.) I posted over in the Blue Kuban thread so hopefully someone takes pity on me and puts it up there...

dr_gibberish said:
I think it IS a zip, I just don't know how to get to it other than through the updater which is built into the ROM. Typically, all the files in the updater download to your SD card as zip files and then the phone will reboot and install them in CWM automatically. I just need someone to download the mod on their phone running Blue Kuban and then post it here so I can copy it to my SD card and install it. (That's assuming it really does fix this issue.) I posted over in the Blue Kuban thread so hopefully someone takes pity on me and puts it up there...
Click to expand...
Click to collapse
I changed my previous post with another possible option if that doesn't work.

Installed Kuban and pulled the zip for you. Attached

crawrj said:
Installed Kuban and pulled the zip for you. Attached
Click to expand...
Click to collapse
Totally appreciated your doing this and, unfortunately, total fail. Installed fine, booted back up, still no keyboard on the initial screen. Now I am wondering, even if I restore a nandroid, am I going to face the same thing at boot up?
I just tried to nandroid backup my current setup so I can at least get back to it, and, as I should have guessed, it fails ("Can't mount /data") because it is encrypted. What's more, my old CWM backups are on the internal SD card and so I cant access those either. I think I am screwed. I just hope I can Odin back to stock without a problem. Thanks again for your help, that was above and beyond....
EDIT: For anyone else who might run into this situation, I WAS able to Odin back to a full stock FF18, but everything else I tried failed. (e.g. flashing a "no data" rom through Odin, flashing anything through CWM) I lost all my data on the internal SD card and cant even remember everything I lost. Only bright point is that I have a recent Titanium backup on my external SD card which is solid, so I should be able to get some of my app data, texts, etc back.

dr_gibberish said:
Totally appreciated your doing this and, unfortunately, total fail. Installed fine, booted back up, still no keyboard on the initial screen. Now I am wondering, even if I restore a nandroid, am I going to face the same thing at boot up?
I just tried to nandroid backup my current setup so I can at least get back to it, and, as I should have guessed, it fails ("Can't mount /data") because it is encrypted. What's more, my old CWM backups are on the internal SD card and so I cant access those either. I think I am screwed. I just hope I can Odin back to stock without a problem. Thanks again for your help, that was above and beyond....
Click to expand...
Click to collapse
For your backups. Once the phone is up connect to it from adb. once in adb shell do cp -r /sdcard/clockworkmod /sdcard/external_sd/ This will probably take a while so just be patient until it completes.
What I would try first is to install a stock rom via zip. See if it installs and fixes the keyboard issue.
If that doesn't work, Odin an image that doesn't wipe data and see what happens.
If that fails, do a full Odin restore.

I just ran into this problem myself. I Odin'd the FH13 rooted stock rom, installed CWM and FI25, everything seemed to be fine and then I ran the encryption. After the reboot my keyboard was inaccessible and I can't seem to make it come up.
Even if this was working, Android with encryption seems unusable. I can't imagine having to enter a password EVERY TIME I unlock my phone. I guess I won't be checking work email after all! :laugh:

Grrrrrrreat! So because I could not get a keyboard to show up after encryption I decided to flash to another ICS build, and now I'm getting a "blank USB Storage" notification. I didn't encrypt my SD card; just the phone! I even installed the ROM from the external SD card, and when I reboot to CWM I can access it.
Anybody have any ideas?

I thought USB storage was the internal SD?
sent from my BAD A$$ Epic touch

Did I brick my SGS3 ? ^_^

All right, first thing first. Thanks to everybody for this amazing forum and all support.
Well. Here's my story:
1) Planned on installing CM10 nightly
2) Went to recovery (TWRP v2.2.0) and by mistake wiped everything :/ (Cache, Dalvik Cache, Factory Reset, System Internal Storage)
3) In effect i wiped everything including system.
4) Still have access to TWRP and download mode.
Does anybody have a clue how to fix that and install CM10 again?
PS.
1) internal storage does not mount under system (WIN7)
2) TWRP does not recognize microSDXC (32gbz) formated to either exFat or NTFS. (Tried 4 (four) of them)
Should i buy another micro sd like 2gb, format it to Fat32 and drop CM.zip there ? Or need i do something else?
Very respectfully.

That happened to me I just downloaded the rom to a sd card from my old phone put it in my s3 and installed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Hey thank you for quick answer. Do you know if there is any limitation for TWRP? It does not read my 32gb MicroSDXC.

Go into download mode and re flash then stock rooted rom.
Then install your twrp and try cm again.
Sent from my SGH-I747M using xda app-developers app

Personally, I would (try to?) use adb with the phone booted into TWRP to transfer the ROM you want to flash over to the phone's internal storage, and go from there.
If that's not a possibility for whatever reason, you'd be best off starting by reflashing a stock rooted image with Odin and going from there.

Well. First of all thank you all for all your help in support. Got it back to stock with root (Odin flash). However there is another small problem that i can't figure out. TWRP itself seem not to have access to anything. I mean it sees all / but after openning /sdcard or anything else all it sees is empty folders. It doesn't have an access to external sd either (when you check log it sees that it couldn't mount ext sd correctly [even if after boot to stock system it recognizes it witout any issues).
Any idea how to solve this problem? What has been tried:
1) Reflash recovery (TWRP 2.2 using ODIN)
2) moving all files to /
3) RootExplorer see files (cm.zip) after reboot TWRP doesn't
4) Installing GooManager (it crashes after granting supersu permissions)
Very Respectfully.

With all those problems, flash to stock rooted and start over. You will be better off in the long run. You may want to also format your external sd.
Don't flash twrp with Odin.
Rooted stock
Dl and use goo manager to get twrp

What about a stock kernel? Just my chime in
Sent from my SAMSUNG-SGH-I317 using xda premium

Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.

widofmaker said:
Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.
Click to expand...
Click to collapse
GJ take it sure and slow. Other than flashing stock/rooting form Odin I wouldn't flash anything form Odin. Once you have super user on your phone, leave Odin out and do everything from phone
That's the safest route and it gets easier from here. The countless hours you spent are much easier the more you do it. Shouldn't take more than 20 minute to backup and flash roms and new apps from now on

Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.

widofmaker said:
Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.
Click to expand...
Click to collapse
1. you are flashing a version of gapps that is out of touch with your rom or you did not flash it correctly/cleanly. I remember no matter how many times I flashed gapps I wouldn't get it to sync. Backed all user apps to Titanium backup. Did a clean install from scratch, and wallah it worked. Last sort.
Without doing that though there is usually one that is compatible that is listed on your rom page. Flash that one. For me that is 10/22 but I remember it giving that same error for a while so I ended up flashing the previously compatible version before that which was 7/26. Goo.im might help here, I haven't used it myself. Once you find a working gapps version etc. Store your 'safe' builds in one folder
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable

zetsui said:
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable
Click to expand...
Click to collapse
1) Ended up reflashing gapps with goomanger (script to TWRP)
2) What i mean is that under phone it recognizes them perfectly. Just when I connect phone through USB to PC, my PC tends to mix them up. Just shows ExSD as Internal and Internal as ExSD. No biggy, just tried to fix as many tiny issues as possible before I hit deployment.
Very respectfully.

That is a known, and stated, issue with cm 10.1

Interesting Experience with CWM Recover 6.0.2.3

I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?

solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.

milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!

solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much

The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.

Default camera app can't save photos or videos

I have a D855K (Telstra Australia). I recently upgrading to 10i, using the firmware: LG-D855 A6KG D85510i 00_6 16GB Hong Kong http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW436606432109876543213/D85510I_00.kdz
Before the upgrade, I backed up in LG PC Suite, then imaged with a full wipe, and then restored the backup via LG PC Suite again.
I now can't take photos or videos with the native camera app (haven't tried any third party apps yet). Photos just fail silently, and videos say "Failure to write". I've done some googling, and people having complained about 4.4.x breaking the ability to write to SD cards, but I don't have an SD card in my device. It's just internal storage. Also note that I haven't rooted the phone since the firmware update.
Has anyone else had this issue, or can provide any advice at all? I'm going to get a third-party camera app to see if that can at least let me take some pics if I need to in the meantime, but I would like a fix not a workaround.
Cheers.

I just installed Camera360 and it has the same issue. With photos, both apps save a thumbnail with nothing in it, then warn that the album has changed and you need to refresh the folder. When I do, the folder is empty.
Initially I was running 10d, then then 10b because of a boot loop issue. So it could be a range of things causing this

The Camera360 app works fine (ie can save pictures) if I change the folder to DCIM, instead of DCIM/Camera.
I have used Purpledrake to root my device, and installed a Terminal app. I can navigate into DCIM, but can not do anything at all with the Camera folder. I can't navigate into it, delete it, chmod or chown it. It appears to have all the same permissions as every other folder under the emulated sdcard, but refuses to do anything. I haven't tried it via adb but I doubt it would make any difference.
Any thoughts would be greatly appreciated.

I managed to run e2fsck, and it appears that my data partition has some corruption. But e2fsck can't fix it unless the partition is unmounted. I set up adb but couldn't get to a point where the partition (/dev/block/platform/msm_sdcc.1/by-name/userdata) was not in use. I booted into recovery (adb reboot --bnr_recovery) and it still mounts the /data partition, and on top of that I don't seem to be able to elevate to root. I am only new to the Android ecosystem, so please forgive any ignorance. My google-fu doesn't appear be very helpful either. Any suggestions welcome.

Have you got the nandroid backup?? If so, How about restoring it back?... Have you tried it?? Hope it works...

mustang2012 said:
Have you got the nandroid backup?? If so, How about restoring it back?... Have you tried it?? Hope it works...
Click to expand...
Click to collapse
I was under the impression I couldn't do a nandroid backup until I had a recovery rom installed, which isn't available for the D855 yet... since the partition appears to be corrupted, I suspect formatting the data partition would solve the problem. But I don't really want to lose the customisations I've done. I wouldn't be surprised if the LG PC Suite backup is like an image of the partition, which means it might restore the corruption if I used it.

aussiewan said:
I was under the impression I couldn't do a nandroid backup until I had a recovery rom installed, which isn't available for the D855 yet... since the partition appears to be corrupted, I suspect formatting the data partition would solve the problem. But I don't really want to lose the customisations I've done. I wouldn't be surprised if the LG PC Suite backup is like an image of the partition, which means it might restore the corruption if I used it.
Click to expand...
Click to collapse
Tethered twrp recovery could have you saved your nandroid backup which then you be go back to fully functional status of your phone... Sorry I am new to LG G3 myself coming from galaxy s4.

I looked into those recovery boots but it seemed a bit more complicated than I could be bothered with at the time. The thing is, my phone is still fully operational. The only thing is that the Camera folder appears to be corrupt. Even just changing the path that the default camera app saves to would fix the visible issue, however the corrupt filesystem means I could be in for a lot more pain if I can't sort that out. I'm hoping that someone can point me in the right direction to be able to use e2fsck on the data partition (I think all I need to be able to do is unmount the partition so it's not in use). Otherwise, formatting the data partition will likely be the solution, which I'm trying to avoid.

aussiewan said:
I looked into those recovery boots but it seemed a bit more complicated than I could be bothered with at the time. The thing is, my phone is still fully operational. The only thing is that the Camera folder appears to be corrupt. Even just changing the path that the default camera app saves to would fix the visible issue, however the corrupt filesystem means I could be in for a lot more pain if I can't sort that out. I'm hoping that someone can point me in the right direction to be able to use e2fsck on the data partition (I think all I need to be able to do is unmount the partition so it's not in use). Otherwise, formatting the data partition will likely be the solution, which I'm trying to avoid.
Click to expand...
Click to collapse
No expert here but have you tried restore upgrade errors with pc suite. Hopefully will fix your problems and it doesn't wipe your phone. So you will just have to reroot afterwards.

p70shooter said:
No expert here but have you tried restore upgrade errors with pc suite. Hopefully will fix your problems and it doesn't wipe your phone. So you will just have to reroot afterwards.
Click to expand...
Click to collapse
A good suggestion! I tried to use that feature a week or so ago when I have my phone in a reboot loop. Unfortunately it only said "You have the latest version of the software, go away". It was a little politer than that, of course, but my response was not polite at all. I will give it a go again tomorrow when I have access to the same computer I was doing it with before, and see how I go. I'm not hopeful that it will help, but worth a shot.

aussiewan said:
A good suggestion! I tried to use that feature a week or so ago when I have my phone in a reboot loop. Unfortunately it only said "You have the latest version of the software, go away". It was a little politer than that, of course, but my response was not polite at all. I will give it a go again tomorrow when I have access to the same computer I was doing it with before, and see how I go. I'm not hopeful that it will help, but worth a shot.
Click to expand...
Click to collapse
Was that using restore upgrade errors tho or software update? It worked for me when I was having continuous f/cs when I bootlooped I had to use the flashtool. Can't wait for a custom recovery

It was the Restore Upgrade Errors option. Part of the problem is that there have been no OTA updates for my phone. Checking that XML file at LG shows no firmware at all. I think that cripples the repair functionality a bit.

aussiewan said:
It was the Restore Upgrade Errors option. Part of the problem is that there have been no OTA updates for my phone. Checking that XML file at LG shows no firmware at all. I think that cripples the repair functionality a bit.
Click to expand...
Click to collapse
Ah ok, bummer. How about flashing the kdz again or a different one without wiping, that might do it, its sort of the same process.

p70shooter said:
Ah ok, bummer. How about flashing the kdz again or a different one without wiping, that might do it, its sort of the same process.
Click to expand...
Click to collapse
Unfortunately I don't think the OS partition is the problem. I don't have force quits or the like happening. It's the data partition that has some corruption. I can run e2fsck in no-change mode and it tells about a range of issues. But I can't fix them unless the partition is not in use. Doing anything that keeps the data partition intact, eg flashing the firmware, is not likely to resolve the problem.

Well, I'm flashing the firmware again. I changed the runtime from Davlik to ART after some reading, and the phone stuck at the LG boot logo. I will not restore the backup I did last week, in the hopes that it doesn't screw up the data partition again. At least I get to have some fun tweaking the OS again I guess...

And I can successfully take photos again!
I am still interested to hear if anyone knows of a non-destructive way to fix this kind of issue. e2fsck is on the device, but I can't seem to run it. I'm using Linux knowledge here, but is there a way to set a dirty flag on the partition so that the OS automatically runs e2fsck on next boot?

aussiewan said:
And I can successfully take photos again!
I am still interested to hear if anyone knows of a non-destructive way to fix this kind of issue. e2fsck is on the device, but I can't seem to run it. I'm using Linux knowledge here, but is there a way to set a dirty flag on the partition so that the OS automatically runs e2fsck on next boot?
Click to expand...
Click to collapse
May you tell us how did you fixed it?

As per my post directly before the one you quoted, I had to re-flash my phone to recover from changing the runtime from Davlik to ART (it got stuck at the boot logo). I chose not to restore my backup, which may have re-introduced the problem. A full wipe of a phone will fix a lot of problems... but as I said, it would be nice to know of a less destructive way to do it.

Fix!
Probably a bit late but adding this in case anyone else has the issue.
To fix it on a rooted device, enter TWRP recovery, go to Wipe > Advanced Wipe
Select Internal Storage. and swipe to wipe. (this will delete everything on the Internal "sdcard". That is not apps or settings, but it is saved files and some game files etc.

[Q] Get Pictures off phone from TWRP

My phone is currently totally F'd up and I'm planning to do an RUU but I want to get the pictures off of it first, is there any method of getting them off via TWRP or something? They are all on Internal storage so i can't just take them out and plug them into a computer. I've tried MTP transfer from it but it only allows me to do my SD card, is there some sort of ADB command or something to extract all of my internal storage or a certain folder to my computer? Anything at all? Even besides that?
Yes the internal storage is accessible, not messed up or encrypted or anything. Just don't know how to get the files off it without having a ROM (can't flash any until i RUU).

Don't use an RUU (yet)?
If you can get any ROM to boot, use that ROM to get your pictures. THEN run the RUU. If you can get to a working recovery, this should be doable.

jshamlet said:
Don't use an RUU (yet)?
If you can get any ROM to boot, use that ROM to get your pictures. THEN run the RUU. If you can get to a working recovery, this should be doable.
Click to expand...
Click to collapse
No ROM will boot, or install, adb will not function properly, TWRP reboots randomly, half of the functions in TWRP are causing it to reboot, MultiROM has a couple partitons I think never got removed, it's quite bad. At the moment I am totally stumped at what to do to even consider 'fixing' this besides an RUU. I'm not stupid when it comes to fixing my phone either, I normally have minimal issues when fixing things but this one is just above my level in actually fixing it rather than just doing the simple way out (RUU). Oh and I can't flash anything via TWRP.
Soo in short I just want to get the pictures...then RUU. I have backups on my SD card to restore and if I can get the pictures then I'll already have a full internal storage backup & sd backup to restore if needed. The pics are the only things not fully backed up, i.e why I need/want them. Probably best I do an RUU anyways, I can't uninstall MultiROM to get rid of the partitions so the RUU seems to be my best bet.

S1L3nTShaDoWz said:
No ROM will boot, or install, adb will not function properly, TWRP reboots randomly, half of the functions in TWRP are causing it to reboot, MultiROM has a couple partitons I think never got removed, it's quite bad. At the moment I am totally stumped at what to do to even consider 'fixing' this besides an RUU. I'm not stupid when it comes to fixing my phone either, I normally have minimal issues when fixing things but this one is just above my level in actually fixing it rather than just doing the simple way out (RUU). Oh and I can't flash anything via TWRP.
Soo in short I just want to get the pictures...then RUU. I have backups on my SD card to restore and if I can get the pictures then I'll already have a full internal storage backup & sd backup to restore if needed. The pics are the only things not fully backed up, i.e why I need/want them. Probably best I do an RUU anyways, I can't uninstall MultiROM to get rid of the partitions so the RUU seems to be my best bet.
Click to expand...
Click to collapse
Ouch. Unfortunately, a screwed up partition map is probably only recoverable by fully wiping the internal storage. I inadvertently did something similar to my daughter's Nexus 7, and the only resolution was reloading a factory image from fast boot. (since Google doesn't seem to do RUUs)
Maybe one of the Multi-ROM devs has a better solution?

jshamlet said:
Ouch. Unfortunately, a screwed up partition map is probably only recoverable by fully wiping the internal storage. I inadvertently did something similar to my daughter's Nexus 7, and the only resolution was reloading a factory image from fast boot. (since Google doesn't seem to do RUUs)
Maybe one of the Multi-ROM devs has a better solution?
Click to expand...
Click to collapse
It's more like I have 4 little partitions for the other ROM's that won't get removed unless I do the RUU anyways or at least get the phone functional enough to where I can remove them with MultiROM but as I said I just want the pictures and to rid of it. Once I get them or if I can/can't then i'll fully wipe it and probably do the RUU too. Just want to at least TRY to get them, if not it's whatever but worth a shot.
Oh and the 4 little partitions thing, thats only from what I know of how MultiROM works, I don't actually know 100% for sure if it really creates partitions. Quite sure it does though

Try
adb pull /data/media/0/
it should pull all files from internal storage
make sure you mount data in TWRP first before you run the command
or
you can try to flash TWRP as linked in my sig, it can mount your internal storage as MTP
or
search for qtADB ... it's a pc-android explorer... then browse to data/media/0/
you can copy whatever that you need with its copy function
(you need to mount data in TWRP first)

ckpv5 said:
Try
adb pull /data/media/0/
it should pull all files from internal storage
make sure you mount data in TWRP first before you run the command
or
you can try to flash TWRP as linked in my sig, it can mount your internal storage as MTP
or
search for qtADB ... it's a pc-android explorer... then browse to data/media/0/
you can copy whatever that you need with its copy function
(you need to mount data in TWRP first)
Click to expand...
Click to collapse
Okay thank the spaghetti monster of doom that last one worked, got the pictures extracted safely. I tried getting my entire internal storage just in hopes I could 100% clone my old setup but it just keeps glitching and won't do it. Either way got what I wanted, attempting an RUU now . Thanks for the help!
Oh and just for informational purposes, I was already using his TWRP and that ADB command just did what every other thing I normally do in TWRP does, rebooted my phone after 2 seconds of it. It did manage to get 2 files but they weren't even what I wanted. Maybe if I did it more specifically it would've worked but oh well.
Updaaaate!: Got everything back as it should be via RUU, Nandroid Backup, & backed up Internal Storage from 8/11/14 along with the Pictures you helped me get!