Initiall I wanted to disable waking up the phone with the home button. So I tried to edit the /system/usr/keylayout/Generil.kl
In line 192 I put the "#" symbol before "key 172 HOME WAKE" and rebooted the phone. Instead of disable waking up with the home button, it disabled the power, menu, and back buttons altogther. The power button is only active when the phone is off or in the recovery menu.
Since I put aside the original file, I copied it back, rebooted the phone, but nothing changed! I tried wipe, but it didn't work. and probably shoud not since it does not re-write /system
how can I restore the normal functioning of the keys?
thank you
SM-G900F, international version, rooted, knox 0x0, ANE2
Revert your changes (replace or revert the file that you changed)
Then boot to recovery mode and wipe the system cache.
if your issue persists, then you may have corrupted the file permissions. Check that they are set as 0644. The only other thing that could plausibly interfere is some unexpected user settings conflict. You could seek to resolve that with a scalpel by going to the applications manager in the settings menu and clearing the app cache and data for the relevant app. Or with a sledgehammer by doing a factory data reset.
.
.
How can I wipe the system cache? I tried "wipe cache partition" which wipes /cache and "wipe data/factory reset" (as well as the factory reset from android itself), but th latter does not wipe and re-writes /system
Once you get that done, if you still want to stop the home button waking the phone, install exposed framework and run the wanam exposed module.
You can stop the home button wake function as easy as putting a check in a box. Working great for me.
Sent from my Galaxy S5 running NeatRom 0X1
fffft said:
if your issue persists, then you may have corrupted the file permissions. Check that they are set as 0644.
.
Click to expand...
Click to collapse
Oh! That was the problem! I changed the permissions and rebooted the phone. It did away with the problem!
thanks!
Prof Peach said:
Once you get that done, if you still want to stop the home button waking the phone, install exposed framework and run the wanam exposed module.
You can stop the home button wake function as easy as putting a check in a box. Working great for me.
Sent from my Galaxy S5 running NeatRom 0X1
Click to expand...
Click to collapse
can I install the framework without triggering the knox? if yes, could you give a link?
is it no way to disable the home button through editting the files?
vvixx said:
How can I wipe the system cache? I tried "wipe cache partition" which wipes /cache and "wipe data/factory reset" (as well as the factory reset from android itself), but th latter does not wipe and re-writes /system
Click to expand...
Click to collapse
Wipe cache partition (from recovery mode) wipes the system cache i.e. /cache.
If you have already wiped the system cache and done a factory data reset (initializes /userdata), then the most plausible remaining error is something with your system files. You didn't say if you had checked the original file permissions or not? That is a common source of user errors. If the permissions are correct, then you could try extracting the file in question from a full stock firmware image (use winrar) and replace it on the assumption that your current keylayout file is corrupt.
If you are unable to discern where the remaining problem lies (permissions, wrong directory, inadvertently renamed file, corrupt file, et cetera), then restore your backup if you have one. Otherwise, your option of last resort is to write a full, stock firmware image to resolve all issues. Which is to say, starting over from scratch.
Your most likely error at this point is permissions.
vvixx said:
can I install the framework without triggering the knox? if yes, could you give a link?
is it no way to disable the home button through editting the files?
Click to expand...
Click to collapse
Xposed framework will not increment your Knox flag.
Or you can edit the keylayout files (properly). There are existing threads that explain how. Or search my post history as I've described how to do so in previous posts.
.
Related
OK so, I was getting ready to flash to a new rom. I performed a factory reset, wiped cache, data, dalvic, etc...twice. But not paying attention, I accidentally selected reboot system before flashing a different rom...
...it rebooted normally, except as a fresh install. So by wiping the system, I'm really only clearing user data? How do I get rid of the rom entirely? Let's say the new rom I try to flash is considerably smaller with a lot less bloat. Wouldn't simply overwriting old rom still leave behind all of that extra data?
Is it possible to completely wipe the system partition and flash a new rom with cwm and have it boot?
Sent from my Amazon Kindle Fire using xda premium
new roms usually format the system partition - so nothing is left behind
In addition to what b63 said (which is correct), I think you're just getting hung up on some of the terminology. Doing a factory reset only wipes out userdata (data, cache, .android_secure) and doesn't touch your system partition. The ROM itself is still completely intact after a factory reset.
If you want to manually wipe your system partition you can do that, but you usually don't need to. In CWM go to "Mounts and Storage" and then select "Format /system" to do it. TWRP has an equivalent that I can't remember offhand, but it's something to the same effect (might be under "Advanced" or something). If you flash a ROM after you format /system manually it will boot fine, but obviously it won't boot if you format and reboot without installing a new ROM.
You're right, I just misspoke. The rom is only contained in the system folder, correct? I just couldn't understand why it would boot if I presumably wiped everything.
Sent from my Amazon Kindle Fire using xda premium
yes - if you look into the zip file of a rom you'll see there is mainly the system folder - that is /system
some have a data folder also - that are additional preinstalled apps in /data/apps
if your question is answered please mark the subject of the topic (edit first post) with [Solved]
Yes, the ROM's applications and binaries all live on the system partition, which is why it has no trouble booting after a factory reset. The data partition is basically reserved for user settings, apps, and other files.
Hi everyone, I recently rooted my 16GB WE TPT and installed cm10 v.0.8.1 and I love the performance and everything, if only there were no reboots. After reading in this forum I wanted to try to reinstall things from scratch wiping everything. For some reason I don't seem to be able to to anything with the data that is on my TPT. Neither can I do a factory reset from settings nor can I wipe data from Recovery. It doesn't display an error but it just doesn't delete anything. Then I tried to restore my backup from my original rom but this doesn't work either: it says error while restoring data (after recovery and system).
Can anyone help me? Could I have accidentally locked the data or anything?
Btw, Google Play has stopped working after my last try to restore stock and then install cm10 again.
In cwm you find under advanced a setting called "fix permissions". Try that
emuandco said:
In cwm you find under advanced a setting called "fix permissions". Try that
Click to expand...
Click to collapse
Doesn't do anything.
idewis said:
Doesn't do anything.
Click to expand...
Click to collapse
Hi, i had big problems with my Data-Partition. The Partition was read-only. No wipe with CWM was possible. Is that the same problem what you have? Do you have an logcat? Any error-messages?
Wiping was only possible with adb...
Here is my post: http://forum.xda-developers.com/showthread.php?t=1944759
When it is the same problem, it exist an solution...
Greetings
tpauli said:
Hi, i had big problems with my Data-Partition. The Partition was read-only. No wipe with CWM was possible. Is that the same problem what you have? Do you have an logcat? Any error-messages?
Wiping was only possible with adb...
Here is my post: http://forum.xda-developers.com/showthread.php?t=1944759
When it is the same problem, it exist an solution...
Greetings
Click to expand...
Click to collapse
I don't have the same error messages you have/had, but I could image that my data partition is also read only since I can neither delete or install anything. What did you do to get rid of that problem?
The solution was to completely format the data permission. This can't be done in CWM directly because CWM tries to keep the folder /data/media, which is your internal sd-card and only deletes the other files (That's obviously not formating). In the link you can find a zip files that you can "flash" in CWM, it will format the data partition and does nothing else. After using it you should also manually wipe the cache using CWM.
Like i said, this will include your internal sdcard! Make backups first if you have important data stored on it!
http://ubuntuone.com/4zKT1jqeqhR8qdGh2y4TaM
I need to clear it - if I do "wipe data/factory reset" in stock ICS recovery menu - will it cause deleting ROM (and reboot will make brick) OR just will get it back to clean factory ROM?
I found few threads here about "wipe data"-thing, but it seems to me, that every version of Android / custom ROM / recovery type could behave different.
I want to have a clean install on my Nexus, and I was wondering what it meant to "WIPE". Is it Factory reset, cache, dalvik cache, and system? Or is it also system too?
I have TWRP
Thank you!
factory reset. when you wipe data, you factory reset. that automatically wipes your cache and dalvik too.
simms22 said:
factory reset. when you wipe data, you factory reset. that automatically wipes your cache and dalvik too.
Click to expand...
Click to collapse
It's not system too?
iamjerry123 said:
It's not system too?
Click to expand...
Click to collapse
no.
simms22 said:
no.
Click to expand...
Click to collapse
Thank you so much for answering all my stupid questions. So If I wanted a new clean start for my phone (while it still being rooted and not losing all my SD card files) I would just have to do a factory reset, then flash?
Unfortunately, the terminology seems to vary from device to device and even from recovery to recovery.
It can mean either (a) "destroy the filesystem and rebuild a new blank one" or it can mean (b) "don't destroy the filesystem but delete all the files in it". In both of these cases, access to all files are lost, but there are subtle differences for the flash memory with regards to whether the blocks are marked as erased or not.
As regards to recent versions of TWRP, the "factory reset" button underneath the Wipe menu does not behave exactly like either of the above cases (although it is more similar to case (b)), nor does it behave the same way as the stock recovery's version of "factory reset", which deletes EVERYTHING in /data.
TWRP's version of "factory reset" erases everything in /cache, but when it comes time to deal with the /data partition, it avoids erasing all the files in /data/media. This is where the "internal SD card" files are stored INCLUDING ANY BACKUP FILES you might have made (if you didn't use an external storage for the backup)
Here's what I would recommend when using the Wipe menu in TWRP:
1) Put the tablet down on a table before you enter the Wipe menu - don't hold it in your hands. The reason for this is that none of the touch buttons require confirmation, so an accidental touch could lead to an immediate disaster involving loss of your backups.
2) If you are installing a new ROM from scratch, the only button you need to use is the "factory reset" button - nothing else. (Performing Dalvik wipe or Cache wipe are superfluous as the "factory wipe" button takes care of this) *1
3) If you are installing a ROM which is a small revision from a prior version - and the ROM dev has explicitly indicated it is OK to do a "no wipe" install, use only the "cache wipe" and "dalvik wipe" bttons. *2
In short, you should really only use the top four buttons in TWRP under normal circumstances. Especially you should avoid the "wipe data" button unless you are:
- selling the device or returning it
- some disaster happened where the /data partition fails to mount any longer.
*1 It is somewhat unusual that ROM devs fail to add a wipe of /system in their scripting prior to
installation; so typically using the "wipe sytem" button is not needed for new ROM installs, and it is cerainly not desired if you want to do a complete reset of whatever ROM is already installed.
*2 Doing this kind of thing is just asking for trouble - understanding and using the Titanium Backup along with full-wipe installs is a better idea.
cheers
Hi, today i wanted to do a factory reset and clean install my phone
im using TWRP 2.3.3.3
after factory reset in the wipe menu, at the end i see a line E:/error opening '/data/lost+found'
basically i know what does lost+found folder does in linux, but i forgot whether i have seen such error line before when i do factory resets.
in the file manager of TWRP i then see /media and /lost+found in the /data partition. when pressing into /lost+found, TWRP cannot open it
after this, wiping /system will also give me the same message at the end even it is "Done", as well as cache and dalvik, etc
then i go on flash rom, gapps, kernel, after 1 or 2 boots i go back to recovery and wipe cache, there are no such line anymore
however there is now TWO /lost+found folder in my /data partition
is this a normal behaviour? i didnt pay attention but are there 2 lost+found folders in /data partition for everyone else too?
i have backed up my sdcard and is ready for a /data wipe, any advice is appreciated. thanks in advance!
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Miasmic said:
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Click to expand...
Click to collapse
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
just had this issue and was solved by dropping back to twrp 2.4.x.x and doing data format.
misspost
mitchallica said:
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
Click to expand...
Click to collapse
No his error and mine are different. We have two lost+found dir and no file. If i delete them and make new lost+found folder. It automatically makes 2.
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Full Format data worked for me
NVijapura said:
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Click to expand...
Click to collapse
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
szurheal said:
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
Click to expand...
Click to collapse
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
That worked perfectly. Thanks!!!
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
leijonasisu said:
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
Click to expand...
Click to collapse
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
I'd appreciate any advice.
Florad77 said:
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
I'd appreciate any advice.
Click to expand...
Click to collapse
start phone go to settings/dev settings an enable oem unlock
ever find a fix??? im having the same issue !
Koleboy9 said:
ever find a fix??? im having the same issue !
Click to expand...
Click to collapse
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
I could kiss you right now, thanks!
just wipe cache partition to get to normal system again
Florad77 said:
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
I'd appreciate any advice.
Click to expand...
Click to collapse
if you experience like this(verification failed) and you dont want to lose your date. just hold and press power+up+home, this will jump to recovery mode, and if you see installing update and got error, just press again power+up+home till you reach the recovery option. after that just wipe cache partition. the verification failed will disappear and youll have the normal system again. i experienced the same issue but i manage to fixed it after doing the rooting twice. i didnt reset my device. you dont need the emergency firmware repair. just wipe the cache partition.
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
I won't kiss you but I will say THANK YOU, THANK YOU, THANK YOU. I was starting to give up on flasing my S7 with TWRP and another ROM.
ah thanks man
could kiss everyone in this thread thanks for all the help u saved my ass
Some things you can try...
Florad77 said:
Every time I try to root my phone weather through cf auto root or the method here I get the screen "Verification failed. Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." Even after I press reset it still comes back to that screen. Resetting through TWRP always fails as it says can't mount /data. The only way I can fix this is by doing an emergency firmware recovery through smart switch pc. I had my phone previously rooted with cf auto root then I flashed back to stock. Now I'm trying to root again and it just doesn't seem to work. I'm using all the right files for my device and following the steps correctly.
Click to expand...
Click to collapse
Are you sure you're following the steps correctly? Try some of these tips:
After flashing TWRP, instead of switching volume buttons on the fly (requires dexterity and timing! ), hold the VOLUME DOWN and POWER buttons until the phone turns off. You can then proceed to recovery by holding VOLUME UP + HOME + POWER.
Are you using the latest TWRP for your S7 Edge? Some older versions of TWRP have problems mounting folders and flashing ZIPs.
Did you update to the latest firmware before attempting root? Later Android versions become very finicky about device security, essentially locking you out of your phone.
Note that once your device detects that it has been tampered with, you won't be able to update. Download your stock firmware from some place like SamMobile and flash all the required tar.md5 archives through Odin (keep in mind: HOME_CSC keeps your personal data, while CSC erases it). If that doesn't fix it, backup whatever you can through TWRP and factory reset.
Did you enable OEM Unlock? Once you can access your settings again, if it is on, you may want to tap it off, then back on again. Sometimes it gets buggy.
You did remember to flash something that disables dm-verity, right? You may want to try flashing the dm-verity and force encryption disabler ZIP first before truly rooting.
i am having the exact same issue but i tried wiping cache that didnt work so i dont know what to do
Please Help
suljo94 said:
start phone go to settings/dev settings an enable oem unlock
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data
what do i do?
i am having the same problem on my S8+, it says verification fail, and i click on reset and as phone loads it goes back to the same screen that says Verification fail!
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
I don't mean to necropost, but this is an important detail for anyone out there having trouble with these "verify failed" messages. I knew I was missing something b/c there is an advanced option with formatting options that is not the same as the format button on the main wipe page. This did the trick for me trying to get my SM-G9600 (Chinese Samsung Galaxy S9) up and running with TWRP + Stock Oreo 8.1.
Big ups, @Florad77!
When to format data in rooting process?
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
When do you format data? Before installing supersu or after?
tarocco said:
I don't mean to necropost, but this is an important detail for anyone out there having trouble with these "verify failed" messages. I knew I was missing something b/c there is an advanced option with formatting options that is not the same as the format button on the main wipe page. This did the trick for me trying to get my SM-G9600 (Chinese Samsung Galaxy S9) up and running with TWRP + Stock Oreo 8.1.
Big ups, @Florad77!
Click to expand...
Click to collapse
the "advanced" tab in Odin is primarily used for the PIT file in the firmware zip package. It is not advised to flash the PIT unless necessary. Often times, the "verify failed" message means that your bootloader is still locked or youre flashing the wrong file. Just fwiw.
Florad77 said:
Yeah, in twrp remember to format data. Not the regular wipe data but the option that says format, you will need to type yes when you select it.
Click to expand...
Click to collapse
Yeah, and now my Galaxy Tab Active 2 (Android 9.0) , can't boot. Only the Welcome logo appears, and resetting it indefinitely.