Related
Ok. So I bricked my Kindle Fire. Could not access it through ADB. Nothing. So, I followed the unbricking method with fastboot. Got me access to ADB into the kindle again.
So now, one click will not root the device to allow me to put the other images onto the device. Nor will windows 7 mount it.
One click shows that no files or folders exist for the kindle and asks me if I am sure I am running 2.0 or higher.
I can adb into it, but without root I cannot copy files into the needed directories to get it back to stock, or put CM7 on it.
When I boot, i get the kindle fire words, then a black screen. It just stays black. Its better now because at least I can ADB into it, but without root I am hosed, and one click is not working.
I turn myself over to the mercy of the Kindle gods. Any help would be greatly appreciated.
added info:
To be clear. Windows recognizes it, and ADB can connect to it and I can navigate the file structure, but it will not let me root to copy things to the file system.
When I try to use the command prompt to get to e:, a window pops up and tells me there is no disk in the drive. Please insert a disk into drive \device\Harddisk1\DR52. Then the command prompt says, The device is not ready.
With all the knowledge and information going through this forum, not even a suggestion. Pretty please......
I'm no expert sadly but do you need to root to copy over a system file? If not you could push the stockrecovery.img that you can find here (http://forum.xda-developers.com/showthread.php?t=1390773), that may be why your device isnt booting.
Where do I push that to? What location on the device? I have downloaded the image, just not sure where to put it to get it going again.
just google it how to put android etc....
I would not say I am a noob. My question is this. It will not let me mount my sdcard. So when I push update.zip to the sdcard and then try to run it from the sdcard with twrp, I get an error message saying that it cannot mount /sdcard/update.zip, so can I put update.zip somewhere else, lets say in the system folder, and run the update from there?
Not to mention, its kind of messed up that you call me a noob and point me to a video basically telling me to search the forums. Here is the problem with that. I cannot start a thread in the dev forums for the kindle fire until I post 10 times. So while you are calling me a noob and pretty much insulting me and my intelligence, I am far from a noob, I simply could not post my question in the dev forums.
lonelliott said:
Not to mention, its kind of messed up that you call me a noob and point me to a video basically telling me to search the forums. Here is the problem with that. I cannot start a thread in the dev forums for the kindle fire until I post 10 times. So while you are calling me a noob and pretty much insulting me and my intelligence, I am far from a noob, I simply could not post my question in the dev forums.
Click to expand...
Click to collapse
When you do get 10 posts and post in the Dev forum they will just tell you that you posted in the wrong forum.
Your problem has been covered many times on here if you just browse around or search you will find it.
My problem is that the sdcard will not mount, nor will it hold information. I can copy a file to it, and as soon as I reboot, it will erase that file. I have searched for ways to format the sdcard, or format everything and partition but have found no answers yet.
Just for safe measure, I did another search just now in all the kindle fire forums for "mount sdcard" and "format sdcard" and I could find no answers.
Again, when I put a file onto the sdcard, like update.zip, as soon as I run it from twrp, or even fastboot, it tells me that it cannot mount the /sdcard/update.zip file.
On top of that, when I reboot it will not keep the file, it erases it, except the twrp folder, it stays after a reboot.
I can access the system through adb, fastboot and now twrp, but cannot get it to take an update.zip file to restore it. Even though I can access it through adb and fastboot, it does not show up in my explorer window and I cannot browse the device from either a windows 7 machine or a ubuntu 11.10 machine. When I plug it in, the machine recognizes it and charges it, but wont mount it to view files.
It also returned an error saying there is no listing for the sdcard in /etc/fstab.
Not sure what to try next. Any help would be greatly appreciated.
Then you must not have read and write privlage
Sent from my Kindle Fire using Tapatalk
I dont know if it will work but it fixed mine
download this http://forum.xda-developers.com/showthread.php?t=1348782
and flash it with fastboot
fastboot flash system path\to\system.img
and you may also have to get and flash boot.img from an amazon update
asb, I do have read write, tried and verified. It is failing to mount the sdcard. Thanks Kaw. I will give that a try with fastboot.
I have twrp as the boot image. If I reflash from an update will it remove the twrp? I think it would write over it, which, if it worked, would be ok with me. I am going to try both.
When I try to flash the system.img, it tells me the remote image is to large and exits.
Trying to restore a NAND in CWM but it says "couldn't find directory, no files found" when I click "restore"
So i did a backup, and it shows up when I then hit "restore" in sdcard/clockworkmod/backup (listed at top of recovery screen) but when I boot and look on my sdcard, it shows the old backups I made in the folder listed, not the one I just made. I can't find the one I just made, even though if I reboot into recovery, it still shows it (the latest) and only it.
Any idea where the newest one is, and why I cant restore the older ones?
Are you running CWM 6.0.1.9?
Also, take a look at http://forum.xda-developers.com/showthread.php?t=1991657.
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
TheAtheistReverend said:
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
Click to expand...
Click to collapse
I don't see why you couldn't move the files with rootexplorer. Give it a try!
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
TheAtheistReverend said:
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
Click to expand...
Click to collapse
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
If you are worried about losing the backups, copy them to your pc or onto OTG storage. I use cwm and my backups are now in /data/media/clockwork. If you activate multi-user, I think they go to /data/media/0/clockwork, but I can't test. Not sure about the TW recovery.
scott_doyland said:
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
Click to expand...
Click to collapse
Confusing But the info is there. I don't like how complicated it ahs gotten to wipe, restore, recover, and flash. It used to be so simple...:silly:
I've been flashing N7 with no issues as recently as over the weekend. Today I tried to flash a new ROM and it failed. Tried a second, different ROM, same result. Do not know what I did. Any thoughts?
Error log would help greatly.
How do I get/generate the log? Haven't had to do it before.
Thanks,
Paul
The logs= errors displayed on the screen provided by the interface you use to flash the rom (recovery, computer...)
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
do I need to create a partition? Never get more details despite the tease.
Thanks,
First -
Try and download a different (NEWER) TWRP. Re-flash TWRP. Try again
or
Have you tried completely wiping the device? And pushing a ROM from ADB or using a USB OTG and Memory stick?
I had issues with my nexus becoming VERY unstable. Leading to issues.
I completely, and I mean completely, wiped. To the point that all that device basically had was a recovery, and a bootloader.
I proceeded to flash again, BOOM all fixed up.
Is there a new TWRP?
I did a factory restore after wiping everything thing, if that is what you mean?
It was working as expected last week, don't know what I did to screw it up
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
ibsk8 said:
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this, and it said it copied but I am unable to locate it. It says 0\media\data But that folder structure doesn't exist, at least according to file expert
Will a complete wipe/restore create a partition?
pmgreen said:
Will a complete wipe/restore create a partition?
Click to expand...
Click to collapse
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
pmgreen said:
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
Click to expand...
Click to collapse
Focus your efforts here; it certainly looks like a first-order problem.
bftb0 said:
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
Focus your efforts here; it certainly looks like a first-order problem.
Click to expand...
Click to collapse
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
pmgreen said:
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
Click to expand...
Click to collapse
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
bftb0 said:
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
Click to expand...
Click to collapse
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
pmgreen said:
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
Click to expand...
Click to collapse
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ su
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
bftb0 said:
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ such
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
Click to expand...
Click to collapse
Thanks bftb, you are correct it's a can't open zip. No error than fail and it can't open the zip. It says updating partition but nothing changes
The file names are from the developers, once of which I recently successfully flashed. Tried coping the log to the SD card, but unable to find /data/media/0. Do I need to recreate a partition?
(FYI there was an auto-correct typo in my prior post - "su" not "such". Derp)
pmgreen said:
Do I need to recreate a partition?
Click to expand...
Click to collapse
No. (There is no way to do that with the tools we have anyway)
Unless what you mean by "recreate" is rebuild/reinitialize a filesystem in a partition - that's a possibility.
You need to try and figure out why you can't read files.
As a workaround, you can put files on a USB key (FAT formatted, not NTFS) and using TWRP access them by putting the USB key on the other end of a OTG cable.
Your posts are a bit vague - I can't even tell if you have tried other ROM files, whether you checked them to see if they are the correct size/checksum, etc.
pmgreen said:
Tried coping the log to the SD card, but ...
Click to expand...
Click to collapse
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
bftb0 said:
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
Click to expand...
Click to collapse
I am not familiar using ADB pull. Tried using a root file manager to access the log but don't see.
Greatly appreciate your help, let me know what other info I should paste.
Thanks,
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
The Phone is Dead now !! anyone can help please
habab said:
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
Read this thread.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i didn't understand this
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i have tried that thread still have same problem .
Any help !?!?
..
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
Hi , i Downloaded a efs backup app and i just pressed on restore before i press on backup , after that the /efs file is empty . i tried to make ( /efs/FactoryApp/factorymode ) with this app : root browser but that didn't work...
i have tried to Flash with many stock room from sammobile but the /efs file still empty .
after reboot i have to connect to Wifi every time i reboot the phone and some time i have Network and some time nott .
..
yes i have backup of the efs ,
the app that i am using just named Root browser with black android pirate icon
.
i maked the directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp , after reboot i find the file emptey again !
and i used this app ( http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 ) for backup
..
1. i am sorry, my English is so bad !!
2. day 1 , i Downloaded the app Samsung tool and then maked a backup of EFS on External SD-Card ,
3. I maked restore and i had removed the SD-card
4. after that i didn't know that the efs file was damaged , i just installed an room from sammobile ( G900FXXU1ANG9_G900FNEE1ANG5_NEE ) , after the installation was done the phone started but i got an warning massage that says , FactoryMode is on and the wifi was off and only emergency call , i rebooted the phone the wifi was till of but i got back my Network after that i tried many firmware from sammobile
5. o searched on xda and find that it can be the efs but when opened the /efs it was empty.
6. i have the efs-backup on my sd i tried to restore it but nothing happened .
7. i tested that ( Opened this app : https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree ) maked /efs/FactoryApp/ and then file factorymode , ON ) but it can't be moved to FactoryApp when i move or copy it to the folder it is nott there , After rebooting the phone even the FactoryApp directory is deleted .
in my sdcard i found only this ( samsung tool/efs.img )
i tried to make this again
directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp
Click to expand...
Click to collapse
After reastart phone screen is just black !! but the pc is finding it !!! now the phone is dead
..
No i can't boot to anything !! it is just black screen .
No i can't boot to anything !! it is just black screen .
please help me with that.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
fffft said:
No problem and your patience is appreciated.
Nothing anomalous is showing up in those details so I think we can safely assume that accidentally pressing the restore button rather than backup button simply corrupted your efs partition. All of those questions were aimed at confirming that with certainty, but I understand that this is a lot of work and frustrating for you too. So we'll proceed on that basis.
An efs.img file is an uncompressed efs backup. So try restoring that with your efs program. I have no idea if it is a valid (working) backup, but you aren't going to cause any further harm by trying to restore it. If that works, great and you're done. If not, then we'll go on to rebuild your efs instead.
To rebuild your efs partition we need a custom recovery. So a few last questions.
You are rooted, correct?
Did you use Towel root or CF-autoroot? (I am trying to discern if you have super su /busybox installed)
Are you able to boot to recovery mode (home + power up + power)?
Do you have a custom recovery installed e.g. TWRP or CWM?
If you can answer yes to all four questions, then go ahead and run the following efs repair script. If not, then you'll need to install a custom recovery first. If you're already rooted but don't have TWRP, then it's just a matter of flashing TWRP with Odin from download mode.
In any event, once you have a custom recovery in place you can run this recovery script.
Download the script here. Copy it to your external SD card. Then boot to recovery mode and install the flashable zip file "Brick_Loop_FIX_afterRestoringBackup.zip" that you copied to your Ext SD card.
Then reboot. If you still have any issues, reboot a second time, then let us know if your phone is working properly again.
Credit to Backachu, I believe for saving me the work of having to write a script for you or describe how to enter the commands manually.
The script comes from this thread. http://forum.xda-developers.com/showthread.php?p=47014662
As an aside, there is a minor mystery there. This comes from a Note 3 thread so when I went to modify it to work with your S5, I found that it was already set up for the S5 rather than the Note 3.. so why it is that way in a Note 3 thread is a mystery. Go figure. But I did check and you can use it the way it is.
.
---------- Post added at 07:43 AM ---------- Previous post was at 07:36 AM ----------
I'm not sure what you mean by "dead". If you can boot to recovery & download mode, don't worry about it for now. Otherwise please elaborate.
.
Click to expand...
Click to collapse
..
fffft said:
Don't panic. I'm sure that we can address the new issue, whatever it is.
I need a little information to determine how to fix it.
I understood that your screen is black after you rebooted. What do you mean by the PC can find it. What message do you see on the PC.. the normal USB message when you connect your phone or something else? If something else, what is the exact message from the PC?
Also please do the following
Disconnect the USB cable and remove your battery from your phone for ten seconds. Then replace the battery.
Now press and keep holding the home button. Then press and hold the volume down button as well, then lastly the power button. Keep holding all three until the phone starts (about ten seconds).
Let me know if you do or don't get to the download mode screen when you do that.
If you don't, try it a second time, just in case you weren't continously holding all three keys to get into download mode.
If you still don't, then we want to ensure that the Kies program is not running (if you have Kies on your computer). Then try going to download mode again in the same manner as above, then plug the phone into your computer with the USB cable and start the Odin 3.09 program and tell me what you see on the Odin screen.
.
Click to expand...
Click to collapse
When i plug it in i get a news USB device named : ZUES Flash Device .
i have tried to Hold Home + Volume - + Power nothing happen.
Odin don't find it , and kies program is not running.
..
Don't ask me how, but I somehow set pattern and forgot it in one hour. I use face rec. as well but after reboot I need to unlock with pattern.
For last 10h I tried all methods how to unlock phone, but no success.
I'm using original, ROM, my G6 model is H870, running Pie, unlocked bootloader, so I can use TWRP. I spent most of my time and knowledge to unlock phone with adb/twrp. Best option I found is to delete gesture.key file which is located under /data/system.
Problem is, that /data is encrypted ...
Is there anyone who managed to remove pattern/lock without loosing data?
Thank you for your time!
akulp said:
Don't ask me how, but I somehow set pattern and forgot it in one hour. I use face rec. as well but after reboot I need to unlock with pattern.
For last 10h I tried all methods how to unlock phone, but no success.
I'm using original, ROM, my G6 model is H870, running Pie, unlocked bootloader, so I can use TWRP. I spent most of my time and knowledge to unlock phone with adb/twrp. Best option I found is to delete gesture.key file which is located under /data/system.
Problem is, that /data is encrypted ...
Is there anyone who managed to remove pattern/lock without loosing data?
Thank you for your time!
Click to expand...
Click to collapse
Maybe this will work: https://************/delete-android-security-pin/
Edit: link gets truncated... Just search 'Remove pin twrp' on Google and click the first result.
krilok said:
Maybe this will work: https://************/delete-android-security-pin/
Edit: link gets truncated... Just search 'Remove pin twrp' on Google and click the first result.
Click to expand...
Click to collapse
Non of this solutions work.
This is pretty the same as I said. My problem is that /data is encrypted and I can't find/see any .key files.
Also I can't do "su" command inside adb shell because of "insuff. privileges" ...
I tried all this solutions:
https://forum.xda-developers.com/showthread.php?p=49666433#post49666433
For method 1 -5 there is a problem with .key files which are not seen to my TWRP/Aroma browser. I don't know If I'm doing anything wrong in method 7, but also after mount I can't access /data/system (/data is empty).
In method 6 I'm stucked on
"Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone." step.
I get "insuff. privileges" error.
akulp said:
Non of this solutions work.
This is pretty the same as I said. My problem is that /data is encrypted and I can't find/see any .key files.
Also I can't do "su" command inside adb shell because of "insuff. privileges" ...
I tried all this solutions:
https://forum.xda-developers.com/showthread.php?p=49666433#post49666433
For method 1 -5 there is a problem with .key files which are not seen to my TWRP/Aroma browser. I don't know If I'm doing anything wrong in method 7, but also after mount I can't access /data/system (/data is empty).
In method 6 I'm stucked on
"Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone." step.
I get "insuff. privileges" error.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Basically, the files you have to delete in the /data/system folder in TWRP are:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
It happened to me a while ago and I didn't have any '.key' files either; I just deleted the rest and when I booted up, I had no lock screen security PIN nor registered fingerprints but could re-set them again through security settings. I didn't need to flash any files nor fiddle around with adb commands, and all my data remained untouched...
If you can't find all those five files or the '.key' files, just delete the ones you can find and it should work. Otherwise, you'll probably have to do a full reset and reinstall...
krilok said:
Have you tried this?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Basically, the files you have to delete in the /data/system folder in TWRP are:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
It happened to me a while ago and I didn't have any '.key' files either; I just deleted the rest and when I booted up, I had no lock screen security PIN nor registered fingerprints but could re-set them again through security settings. I didn't need to flash any files nor fiddle around with adb commands, and all my data remained untouched...
If you can't find all those five files or the '.key' files, just delete the ones you can find and it should work. Otherwise, you'll probably have to do a full reset and reinstall...
Click to expand...
Click to collapse
Problem is, that I don't have any files/folders at all in my /data. I even don't see system folder inside data.
akulp said:
Problem is, that I don't have any files/folders at all in my /data. I even don't see system folder inside data.
Click to expand...
Click to collapse
Sounds like your data folder is not mounted when you boot to TWRP... Have you checked? Reboot to TWRP, select the Mount option; data should be ticked by default. It it isn't, select it, go back to TWRP file manager, and see if you can now browse folders and files...
krilok said:
Sounds like your data folder is not mounted when you boot to TWRP... Have you checked? Reboot to TWRP, select the Mount option; data should be ticked by default. It it isn't, select it, go back to TWRP file manager, and see if you can now browse folders and files...
Click to expand...
Click to collapse
Unfortunately it's checked ... It's seems from this post:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008/page12
nobody managed to get to (encrypted) /data on Pie.
akulp said:
Unfortunately it's checked ... It's seems from this post:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008/page12
nobody managed to get to (encrypted) /data on Pie.
Click to expand...
Click to collapse
Last comment on that thread says the solution also works on Havoc Os 2.9, which is based on Pie... Maybe that person wasn't encrypted to begin with, but, if it doesn't work for you, I guess then the only way to go is a full reset... Good luck!
krilok said:
Last comment on that thread says the solution also works on Havoc Os 2.9, which is based on Pie... Maybe that person wasn't encrypted to begin with, but, if it doesn't work for you, I guess then the only way to go is a full reset... Good luck!
Click to expand...
Click to collapse
Yep, I saw that post ... I relly don't have any more ideas. Should be inside "mount modul" in TWRP /data listed?
I only have System, Cache and SD ... and i can check System only if i check bottom "mount system partition read-only" option.
But that's nothing to do with /data.
akulp said:
Yep, I saw that post ... I relly don't have any more ideas. Should be inside "mount modul" in TWRP /data listed?
I only have System, Cache and SD ... and i can check System only if i check bottom "mount system partition read-only" option.
But that's nothing to do with /data.
Click to expand...
Click to collapse
Data option should show. At least it does on mine... You can maybe try updating Twrp version?
I'm on last TWRP.... Meantime I already made full reset ....
If you have encrypted data partition, you're pretty much banned from messing with it, unless you manage to exploit your way through the adb, which requires you to have it enabled and in trust relation with your PC to begin with.
The way I'd go around this is to place an "always yes su" binary and perform pattern removal process through init.d or similar solution. In case if su commands are restricted, kernel with permissive SELinux needs to be flashed.
On a side note, isn't this Q&A?
I also had a problem with data folder not being mounted when booting to TWRP. I tried a full reset and immediately i have access to the Data folder (but theres nothing left inside so this is kinda useless). Then later when i did a reboot into the TWRP it happened again, couldnt access to anything even when the "mount Data" option is ticked, only until i did the full reset again that it could finally work.
It turned out the problem is with the TWRP itself, i flashed another custom recovery (OrangeFox-R10-Stable-h870, which is btw a better recovery than TWRP in my opinion) and the problem never occurred again.
So either try out that new Recovery or a different version of TWRP and see if it solves the problem. And always, ALWAYS, make a full backup of all your data before messing with anything (i had to learn that the hard way so trust me).
Do this,
- you should know that I am using "orange fox recovery" not "twrp",and stock "pie"
- reboot to recovery and go to system/data
- delete this files:
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
-reboot the phone and that's it.